Fix (APAR):  JR25960

Status:  Fix

Release:  6.0.2.1

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

Supersedes Fixes:  JR26031

CMVC Defect:  JR25960

Byte size of APAR:  12207

Date: 2007-05-02

Abstract:  If there are "simple types with extension" used in BO schema, SCA runtime is not able to resolve its name, (gives a default of ":0"). and eventually throws org.w3c.dom.DOMException

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

ERROR DESCRIPTION:                                              
Encountering a DOMException: NAMESPACE_ERR exception when there 
is a SOAP fault in return message from WevService. There very   
well could be references to the incorrect namespace             
In the log, we see expressed the following error                
"                                                               
[25/01/07 14:38:05:365 EST] 00000082 ExceptionUtil E            
CNTR0020E: EJB threw an unexpected (non-declared) exception     
during invocation of method "onMessage" on bean                 
"BeanId(BDPublishProcessApp#BDPublishProcessEJB.jar#ServiceSIBus
MessageBean, null)". Exception data: org.w3c.dom.DOMException:  
NAMESPACE_ERR: An attempt is made to create or change an object 
in a way which is incorrect with regard to namespaces.          
   at                                                           
org.apache.xerces.dom.ElementNSImpl.setName(Unknown Source)     
   at org.apache.xerces.dom.ElementNSImpl.<init>(Unknown Source)
   at com.ibm.ws.webservices.engine.xmlsoap.SOAPElement.<init>(S
OAPElement.java(Compiled Code))                                 

LOCAL FIX:                                                      
None known                                                      

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2.x users
using Business Objects with schema
containing "simple type with extension".

PROBLEM DESCRIPTION:
If there are "simple types with
extension" used in BO schema, SCA
runtime is not able to resolve its
name, (gives a default of ":0").
and eventually throws
org.w3c.dom.DOMException: NAMESPACE_ERR

RECOMMENDATION:
None

SCA runtime throws org.w3c.dom.DOMException: NAMESPACE_ERR
when the BO schemas contain "simple types with extention".

e.g.:
<xsd:complexType name="ResponseMessageType">
<xsd:sequence>
<xsd:element name="PresentationMessage"
type="tns:PresentationMessageType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="PresentationMessageType">
<xsd:simpleContent>
<xsd:extension base="string"/>
</xsd:simpleContent>
</xsd:complexType>

In this case, an EClassifier called ":0" is created under the
PresentationMessageType.  It exists, but when setting up a
SOAP call, the data for the EClassifier ":0" should be placed
as if it were the data for "PresentationMessage".

PROBLEM CONCLUSION:                                             
When setting up a SOAP call, the data for the EClassifier ":0"  
is placed as if it were the data for parent element.            


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.2.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 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 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) 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: