Fix (APAR):  JR27007

Status:  Fix

Release:  6.0.2.1

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

Supersedes Fixes:  JR25922, JR26704,JR26524,JR27058

CMVC Defect:  xxxxxx

Byte size of APAR:  62573

Date: 2007-08-05

Abstract:  Customer is migrating collaborations from WICS to BPEL in WPS. The current solution relies on serialising a BusObj to an XML string for external processing.  When this logic is mig

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

ERROR DESCRIPTION:                                              
Problem:Customer is migrating collaborations from WICS to BPEL  
in WPS.The current solution relies on serialising a BusObj to an
XML string for external processing.  When this logic is migrated
to WPS,the invocation of the Crossworlds XML Datahandler fails  
with a java.lang.IllegalArgumentException.                      

LOCAL FIX:                                                      
No                                                              

PROBLEM SUMMARY

USERS AFFECTED:
Testing BusinessObj.isBlank() method
throws illegal argument
exception in migrated code from ICS to WPS.

PROBLEM DESCRIPTION:
Customer is migrating collaborations
from WICS to BPEL in WPS.
The current solution relies on
serialising a BusObj to an XML string
for external processing.  When this
logic is migrated to WPS, the
invocation of the Crossworlds XML
Datahandler fails with a java.lang.
IllegalArgumentException.
If the attribute being tested for
isBlank() is a BusObj type and is
set, then this exception is being
thrown.  In WICS, this
would have returned false.


RECOMMENDATION:
None

Inspection of the stack traces indicates that this error is
being
created by the CxCommon.BusinessObject.isBlankValue method,
which seem
to be behaving differently to its counterpart in the WICS
environment.
If the attribute being tested for isBlank() is a BusObj type
and is
set, then this exception is being thrown.  In WICS, this
would have returned false.

PROBLEM CONCLUSION:                                             
This ifix fixes the following issue in 6021/6022 and will be    
included                                                        
the release after 6022.                                         


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system.
Also 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

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. 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

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: