Fix (APAR):  JR29294

Status:  Fix

Release:  6.1.0.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  24653

Date: 2008-05-28

Abstract:  If an EJB import returns a herited object of the parameter type, SDOJavaObjectMediator would throw a TypeNotFoundException when trying to convert the java object to a data object.

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

ERROR DESCRIPTION:                                              
A service manages two classes: ClassX1 and                      
ClassX2 which extends the first one. When the mapper tries to   
translate the ClassX1 to the SDO it is trying to map to         
ClassX2 and an error is raised.                                 
                                                                
Since the ClassX2 extends ClassX1, it is                        
called/referenced at runtime, but the tooling did not generate  
the BO definition for it.                                       

LOCAL FIX:                                                      
In the generated ClassX1.xsd, add/define the ClassX2 also, so   
runtime can recognize this BO definition.                       

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.1.0.0 users who
use EJB import which returns a herited
object of the parameter type.

PROBLEM DESCRIPTION:
If an EJB import returns a herited
object of the parameter type,
SDOJavaObjectMediator would throw
a TypeNotFoundException when trying
to convert the java object to a data
object.

RECOMMENDATION:
None

The code was not checking if the super class of a java object
could be mapped to a data object.

PROBLEM CONCLUSION:                                             
A check was added for the super type of a java object.          
Applying this interim fix resolves the problem.                 


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: