Fix (APAR):  JR31645

Status:  Fix

Release:  6.1.2.2

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  21998

Date: 2009-04-28

Abstract:  When WSDL/XSD constructs use soap encoding data types, WebServices binding generates incorrect SOAP request.

Description/symptom of problem:  
JR31645 resolves the following problem:

ERROR DESCRIPTION:                                              
A particular WSDL/XSD schema causes incorrect SOAP              
messages when used with WebService Import and Export            
components.                                                     
                                                                
                                                                
The schema definition has a a complexType that contains a       
messagetype with type from the "soapenc" namespace (            
"http://schemas.xmlsoap.org/soap/encoding/").                   
                                                                
                                                                
SAMPLE WSDL SNIPPET:                                            
<wsdl:message name="retrieveByIDRequest1">                      
       <wsdl:part name="contactID" type="soapenc:long"/>        
   </wsdl:message>                                              
                                                                
                                                                
SAMPLE SOAP OUTPUT:                                             
        <?xml version="1.0" encoding="UTF-8"?>                  
<soapenv:Envelope                                               
 xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"      
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/    
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"                
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">      
  <soapenv:Header                                               
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/
"/>                                                             
  <soapenv:Body                                                 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/
">                                                              
    <p660:retrieveByID xmlns:p660="urn:AxisContactHandler">     
      <contactID href="#id0"/>                                  
    </p660:retrieveByID>                                        
   <multiRef                                                    
       id="id0"                                                 
       soapenc:root="0"                                         
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/
"xsi:type="soapenc:long"                                        
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">      
      12345                                                     
      <href xsi:type="xsd:anyURI"/>                             
      <id xsi:type="xsd:ID"/>                                   
    </multiRef>                                                 
  </soapenv:Body>                                               
</soapenv:Envelope>                                             
                                                                
                                                                
                                                                
Even when the href/id attributes are not set, the additional    
href and id are generated in the SOAP message as elements.      
                                                                
This APAR will resolve this issue so that correct messages are  
generated.                                                      

LOCAL FIX:                                                      
avoid using this construct if possible.                         

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server v6.1.2.x and
v6.2.0 users.

PROBLEM DESCRIPTION:
When WSDL/XSD constructs use soap
encoding data types, WebServices
binding generates incorrect SOAP
request.

RECOMMENDATION:
None

HREF and ID attributes that are part of the business object
are generated as elements in the multi-ref element serialized
by the SOAP binding. For a WSDL definition containing:

The schema definition has a a complexType that contains a
messagetype with type from the "soapenc" namespace (
"http://schemas.xmlsoap.org/soap/encoding/").


SAMPLE WSDL SNIPPET:
<wsdl:message name="retrieveByIDRequest1">
<wsdl:part name="contactID" type="soapenc:long"/>
</wsdl:message>

The binding generated SOAP request looks like:
SAMPLE SOAP OUTPUT:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/
"/>
<soapenv:Body
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/
">
<p660:retrieveByID xmlns:p660="urn:AxisContactHandler">
<contactID href="#id0"/>
</p660:retrieveByID>
<multiRef
id="id0"
soapenc:root="0"
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/
"xsi:type="soapenc:long"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
12345
<href xsi:type="xsd:anyURI"/>
<id xsi:type="xsd:ID"/>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>

The href and id elements generated in the multi-ref element
are incorrect.

PROBLEM CONCLUSION:                                             
Applying this interim fix will resolve the issue.               


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: