Fix (APAR):  JR31297

Status:  Fix

Release:  6.2.0,6.1.2.1,6.1.2,6.1.0.3,6.1.0.2,6.1.0.1,6.1

Operating System:  Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  23672

Date: 2009-02-06

Abstract:  WebService Import generates SOAP request using incorrect type attribute (xsd:long instead of soapenc:long).

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

ERROR DESCRIPTION:?                                             
A particular wsdl from Axis 1.4 has an input with type          
soapenc:long.                                                   
                                                                
However, Web Service import component creates SOAP message      
which has this as type xsd:long.                                
                                                                
This is isolated to the Web Service componet.  Other code such  
as the BOXMLSerializer produce the correct types in xml format. 
                                                                
Example message snipped:                                        
                                                                
Expected output message:                                        
                                                                
    <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/">      
      11181                                                     
    </multiRef>                                                 
                                                                
                                                                
Actual output message:                                          
                                                                
    <multiRef                                                   
        id="id0"                                                
        soapenc:root="0"                                        
                                                                
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/
"                                                               
-->        xsi:type="xsd:long"                                  
                                                                
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">      
      11181                                                     
    </multiRef>                                                 

LOCAL FIX:?                                                     
None.                                                           

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server V6.1.0.x, V6.1.2.x,
and V6.2.0.x customers using RPC/lit
encoded Webservices Definition Language
(WSDL).

PROBLEM DESCRIPTION:
WebService Import generates SOAP
request using incorrect type
attribute (xsd:long instead of
soapenc:long).

RECOMMENDATION:
None

When serializing message to SOAP, RPCEncodedMediator creates
type attributes for all elements in the Webservices Definition
Language(WSDL). However, it defaults these types to the xsd
schema, which overwrites the explicit soapenc type already
serialized due to its presence in the WSDL.

PROBLEM CONCLUSION:?                                            
Apply the interim fix to resolve this 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: