PM28389: Unmarshalling of an XML document with the IBM JAXB runtime may result in an object with missing data.

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• An application attempts to unmarshal a document into objects
  in a Java package which contains more than one namespace;
  these objects may be missing data that was in the
  original XML document.
     This often results in the following NullPointerException.
  [07/12/11 15:10:00:393 GMT] 00000036 ServiceDescri 1
  org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl
  <init>
    sparseComposite = Cannot dump DescriptionBuilderComposite due
  to : java.lang.NullPointerException
  This problem does not occur if the JAXB implementation bundled
  within Java 6 is used and this system property is set:
  -Djavax.xml.bind.JAXBContext=com.sun.xml.internal.bind.v2.Contex
  tFactory.
  

Local fix

• Set
  -Djavax.xml.bind.JAXBContext=com.sun.xml.internal.bind.v2.Contex
  tFactory in genericJvmArguments
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server V7.0   *
  *                  users of JAXB and JAX-WS.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unmarshalling of an XML document with   *
  *                      the IBM JAXB runtime may result in an   *
  *                      object with missing data.               *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack that contains this APAR. *
  ****************************************************************
  An application attempts to unmarshal a document into objects
  in a Java package which contains more than one namespace;
  these objects may be missing data that was in the
  original XML document.
  

Problem conclusion

• When JAXB classes appear in a Java package with multiple
  namespaces, the IBM JAXB Unmarshaller was occasionally
  assigning the wrong namespace when mapping XML names to these
  classes. With the wrong mapping information, the
  Unmarshaller ignored valid elements in the XML document
  and so returned objects with missing data.
  
  The problem was resolved by fixing the namespace mapping logic
  in the IBM JAXB runtime.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.17.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP