IBM Support

PM22364: A MarshalException may occur if a JAX-WS @RequestWrapper or @ResponseWrapper references a bean that lacks @XmlRootElement

Fixes are available

7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A MarshalException may occur if all of the conditions are
    met:
    1) The @RequestWrapper (or @ResponseWrapper) on
    the Web method references a JAXB bean.
    2) The bean does not have an @XmlRootElement annotation.
    3) The ObjectFactory in the same package does not reference
    the wrapper bean.
    
    This is an uncommon scenario.
    
    Here is an example MarshalExeption from the system log:
    
    javax.xml.bind.MarshalException
    - with linked exception:
    [javax.xml.bind.JAXBException:
    sample.myMethod is not known to this context]
    at
    org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
    .createSystemException(MethodMarshallerUtils.java:1326)
    at
    org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
    .demarshalFaultResponse(MethodMarshallerUtils.java:1052)
    at
    org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMa
    rshaller.demarshalFaultResponse(DocLitWrappedMethodMarshaller.ja
    va:560)
    at
    ...
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V7.0       *
    *                  developers or administrators of JAX-WS      *
    *                  Web services                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: A MarshalException may occur if the     *
    *                      JAX-WS @RequestWrapper or               *
    *                      @ResponseWrapper references a bean      *
    *                      that lacks @XmlRootElement.             *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR.    *
    ****************************************************************
    A MarshalException may occur if all of the conditions are
    met:
       1) The @RequestWrapper (or @ResponseWrapper) on
    the Web method references a JAXB bean.
       2) The bean does not have an @XmlRootElement annotation.
       3) The ObjectFactory in the same package does not reference
    the wrapper bean.
    
    Here is an example MarshalExeption from the system log:
    
    javax.xml.bind.MarshalException
     - with linked exception:
     [javax.xml.bind.JAXBException:
    sample.myMethod is not known to this context]
     at
    org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
    .createSystemException(MethodMarshallerUtils.java:1326)
    at
    org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
    .demarshalFaultResponse(MethodMarshallerUtils.java:1052)
     at
    org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMa
    rshaller.demarshalFaultResponse(DocLitWrappedMethodMarshaller.ja
    va:560)
     at
    ...
    
    This is an uncommon scenario.  In most cases, the JAXB beans
    referenced by the @RequestWrapper or @ResponseWrapper
    annotations are actual schema root elements; thus the beans
    will have @XmlRootElement annotations.   In the cases where
    the JAXB beans represent types (and not root elements), the
    corresponding ObjectFactory will contain a creation method to
    construct the wrapper bean.
    
    The failing scenario will only occur if the @RequestWrapper or
    @ResponseWrapper is included in a different schema with the
    same namespace, and the classes are then packaged with the
    original schema classes.  This is an unusual scenario.
    

Problem conclusion

  • The JAX-WS runtime is changed to inspect the JAXBContext to
    ensure that it contains all of the referenced classes.  If
    classes are missing, the JAXBContext is initialized using an
    alternative algorithm that guarantees that the classes are
    found.
    
    This additional check and fall back algorithm may correct other
    similar MarshalException and UnmarshalException errors
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  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

    PM22364

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-09-13

  • Closed date

    2010-09-16

  • Last modified date

    2010-09-16

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM22364

Modified date: 16 September 2010