Name: PK41705
=============
 
Summary:
   Incorrect wire triggered if multiple action outputs with same type are wired.
 
Problem Description:
   If a source portlet defines multiple action outputs of which the declaration in the .wsdl file references the same type in the wsdl message declaration, it may happen that wrong wires get fires. 
   This is the case if multiple action outputs are wired up. No matter which action output is published, always the same wire gets fired and thus the wrong information published to the target portlet. 
   The targets these multiple action outputs are wired to do not necessarily have to be defined in one portlet but could be for different ones. 
   
 
Problem Solution:
   Fixed the selection of wires when publishing an output property. 
   The problem was that the first wire with the matching type was taken whereas there are various in the scenario described.
   Now the output property name of the action that publishes information is taken into account as well.
   
   .
 
Failing Module(s):
   Property Broker/C2A/Wires
 
Affected Users:
   All users
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): 
      Co-Requisite(s): ---
 
Platform Specific:
   This fix applies to all platforms.
 
Installation:
   NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
          The Portal Update Installer can be downloaded from the following link:
          http://www.ibm.com/software/genservers/portal/support
 
   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   4. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install the fix.
   5. Restart WebSphere Portal.
   6. The temporary directory may be removed.
 
Un-Installation:
   NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE
          A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
          YOU MAY REAPPLY ANY REMOVED FIX.
 
   1. Shutdown WebSphere Portal.
   2. Follow the instructions that are packaged with the
      Portal Update Installer on how to uninstall the fix.
   3. Restart WebSphere Portal.