Fix (APAR):  JR30260

Status:  Fix

Release:  6.1.2.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  18148

Date: 2008-12-22

Abstract:  Business Object framework can not handl e attribute "nil" with none "xsi" name space prefix in xml element. The following exception can be found: org.eclipse.emf.ecore.resource.Res

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

ERROR DESCRIPTION:?                                             
When Microsoft .net web service returns nullable values, the nil
attribute has different from xsi prefix, which causes a failed  
invocation.                                                     
A exception is thrown as below:                                 
Stack Dump =                                                    
org.eclipse.emf.ecore.resource.Resource$IOWrappedException:     
Feature 'nil' not found. (file:///C:/WID61/pf/wps/, 1, 437)...  
                                                                
For instance:                                                   
Web service invocation fails on that response message:          
                                                                
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:                                                          
u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-                                                          
utility-1.0.xsd">                                               
   <s:Body>                                                     
      <GetResponse                                              
xmlns="http://XX                                                
/v2_0">                                                         
         <GetResult i:nil="true"                                
xmlns:a="http:                                                  
//XX/v2_0/service/data"                                         
xmlns:i="http://www.w3.                                         
org/2001/XMLSchema-instance"/>                                  
      </GetResponse>                                            
   </s:Body>                                                    
</s:Envelope>                                                   
                                                                
After changing prefix to 'xsi' the response is processed        
correctly:                                                      
                                                                
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:                                                          
u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-                                                          
utility-1.0.xsd">                                               
   <s:Body>                                                     
      <GetResponse                                              
xmlns="http://XX                                                
/v2_0">                                                         
         <GetResult xsi:nil="true"                              
xmlns:a="http:                                                  
//XX/v2_0/service/data"                                         
xmlns:xsi="http://www.w3.                                       
org/2001/XMLSchema-instance"/>                                  
      </GetResponse>                                            
   </s:Body>                                                    
</s:Envelope>                                                   

LOCAL FIX:?                                                     
N/A                                                             

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server 6.1.2 users

PROBLEM DESCRIPTION:
Business Object framework can not handl
e attribute "nil" with none "xsi" name
space prefix in xml element.
The following exception can be found:
org.eclipse.emf.ecore.resource.Resource
$IOWrappedException: Feature 'nil' not
found. (file:///C:/WID61/pf/wps/, 1, 43
7)
at org.eclipse.emf.ecore.xmi.impl.XMLL
oadImpl.handleErrors(XMLLoadImpl.java:8
0)
at org.eclipse.emf.ecore.xmi.impl.XMLL
oadImpl.load(XMLLoadImpl.java:189)
at org.eclipse.emf.ecore.xmi.impl.XMLR
esourceImpl.doLoad(XMLResourceImpl.java
:179)
at org.eclipse.emf.ecore.resource.impl
.ResourceImpl.load(ResourceImpl.java:10
94)
at com.ibm.ws.bo.bomodel.util.Serializ
erUtil$2.run(SerializerUtil.java:170)

RECOMMENDATION:
None

If xml element has attribute "nil" and the name space prefix
of "nil" attribute is not "xsi", Business Object framework can
not deserialize such a xml document.
For example:
<elementSample i:nil="true"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance"/>

PROBLEM CONCLUSION:?                                            
After applying the dependent WebSphere Application interim fix  
PK70456 and this interim fix, the issue will be resolved.       


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: