Fix (APAR):  JR31194

Status:  Fix

Release:  6.0.2.5,6.0.2.4

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR31194

Byte size of APAR:  34617

Date: 2009-02-20

Abstract:  When there is a xsd union construct in a business object definition that has both date and datetime as its members, the current BO implementation can not pick up the correct type.

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

ERROR DESCRIPTION:?                                             
The problem that APAR JR26505 fixed with the xs:union types not 
working properly is present in WPS 6.0.2.4 even though this APAR
is checked into that release.   The issue still occurs on       
6.0.2.4, and is a regression of the code.                       
                                                                
This APAR is to reissue the fix for use on WPS 6.0.2.4          

LOCAL FIX:?                                                     
none                                                            

PROBLEM SUMMARY:?

USERS AFFECTED:
 Websphere Process Server 6.0.2.4 users who
are using xsd Union for date vs DateTime
time.

PROBLEM DESCRIPTION:
When there is a xsd union construct
in a business object definition that
has both date and datetime as its
members, the current BO
implementation can not pick up the
correct type.

RECOMMENDATION:
None

When there is a xsd:union construct in a schema that has both
xsd:date and xsd:dateTime types as members, there are problems
when deserializing and deserializing BOs containing the union
construct. During deserialization, i.e. when converting from xml
to DataObject, the time component is lost and the xml value is
interpreted as a date alone and likewise during conversion from
DataObject to xml, the time component is lost again, and the
resulting xml only has the date value.

PROBLEM CONCLUSION:?                                            
This fix resolves the following issue on Websphere Process      
Server 602 Fix Pack 4, 602 Fix Pack 5.                          


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: