PM12908: A javax.xml.bind.UnmarshalException "unexpected element" error may occur when a JAX-WS Web Service receives a message.

Fixes are available

APAR status

Closed as program error.

Error description

A JAX-WS Web service client or provider may receive an
UnmarshalException "unexpected element" error when it receives
an inbound message.   The error indicates that a problem has
occurred converting the incoming message into the customer's
JAXB data object.

Here is an example message:


[4/21/10 15:01:30:734 EDT] 0000002e ExceptionFact 1
org.apache.axis2.jaxws.ExceptionFactory logRootCause Root
Cause:javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.bind.UnmarshalException: unexpected element
(uri:"http://my.test/", local:"myOperation"). Expected elements
are
<{http://my.test/}myOperationResponse>]


All of the following must be true for this error to occur:
A) The JAX-WS Web service must use the document/literal
wrapped style.
B) The method being invoked must not have the
@RequestWrapper or @ResponseWrapper annotation.
C) The customer has provided a wrapper bean in the expected
package (for example, my.test.jaxws.MyOperationResponse).
D) The customer has provided another bean in
the same package as the Web service interface (for example,
my.test.MyOperationResponse).

Local fix

```
<None>
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS                                   *
****************************************************************
* PROBLEM DESCRIPTION: An UnmarshalException "unexpected       *
*                      element" error may occur when a         *
*                      JAX-WS Web service receives a message   *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
A JAX-WS Web service client or provider may receive an
UnmarshalException "unexpected element" error when it receives
an inbound message.   The error indicates that a problem has
occurred converting the incoming message into the customer's
JAXB data object.

Here is an example message:


[4/21/10 15:01:30:734 EDT] 0000002e ExceptionFact 1
org.apache.axis2.jaxws.ExceptionFactory logRootCause Root
Cause:javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.bind.UnmarshalException: unexpected element
(uri:"http://my.test/", local:"myOperation"). Expected elements
are
<{http://my.test/}myOperationResponse>]


All of the following must be true for this error to occur:
A) The JAX-WS Web service must use the document/literal
wrapped style.
B) The method being invoked must not have the
@RequestWrapper or @ResponseWrapper annotation.
C) The customer has provided a wrapper bean in the expected
package (for example, my.test.jaxws.MyOperationResponse).
D) The customer has provided another bean in
the same package as the Web service interface (for example,
my.test.MyOperationResponse).


Condition (B) is unusual.  Most JAX-WS Web service interfaces
explicitly indicate the location of the wrapper beans.
The duplicated classes (C and D) may occur as the result of
using the wsgen and wsimport tooling.

Problem conclusion

When a JAX-WS Web service method does not have the
@RequestWrapper or @ResponseWrapper annotation, the JAX-WS
runtime uses an algorithm to locate the wrapper classes.

Due to an error in the algorithm there was a collision with
the two classes.  The algorithm is changed to avoid the
collision and correctly process the web service request.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.13.  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
PM12908
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-04-23
Closed date
2010-06-04
Last modified date
2010-06-04

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

PM12908: A javax.xml.bind.UnmarshalException "unexpected element" error may occur when a JAX-WS Web Service receives a message.

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?