Fix (APAR): JR32757 Status: Fix Release: 6.2.0.1 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 55698 Date: 2009-04-24 Abstract: Schemas imported using a null namespace are not correctly resolved in EIS binding deployment generation code. Description/symptom of problem: JR32757 resolves the following problem: ERROR DESCRIPTION: null namespace not being passed in LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server and WebSphere Enterprise Service Bus v6.2.0.1 users. PROBLEM DESCRIPTION: Schemas imported using a null namespace are not correctly resolved in EIS binding deployment generation code. RECOMMENDATION: None During service deploy of an SCA module containing EIS bindings the resolution of complex type schemas references that are imported from WSDL interface descriptions that are using the null (empty) namespace cause the generation of application artifacts to fail because they are not correctly resolved to their typing in the null namespace. As a result, deployment or installation of these SCA modules will fail. PROBLEM CONCLUSION: The application of this iFix will resolve the problem of resolving null namespace import references in SCA modules that contain EIS bindings. The application of this iFix will resolve these types of problems on WebSphere Process Server and WebSphere Enterprise Service Bus products version 6.2.0.1. 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: