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

Subscribe

You can track all active APARs for this component.

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 number

    PM28389

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-07

  • Closed date

    2010-12-27

  • Last modified date

    2013-03-22

  • 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



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server
General

Software version:

7.0

Reference #:

PM28389

Modified date:

2013-03-22

Translate my page

Machine Translation

Content navigation