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

Fixes are available

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?