Fixes are available
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
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
APAR status
Closed as program error.
Error description
During a JAX-WS Webservice reply the following exception may be encountered if the @ResponseWrapper is not an @XmlRootElement [10.6.20 20.17.25:781 CEST] 0000001c ExceptionFact 1 org.apache.axis2.jaxws.ExceptionFactory logRootCause stack:javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:"http://com.xxxxx/xxxx/xx /", local:"sendTestSubscriptionDataResponse"). Expected elements are (none)] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.handle StreamEx ception(UnmarshallerImpl.java:417) at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Load er.java: 199) at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Load er.java: 194)
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * of JAX-WS * **************************************************************** * PROBLEM DESCRIPTION: An UnmarshalException error may occur * * if an @ResponseWrapper is not an * * @XmlRootElement * **************************************************************** * RECOMMENDATION: Install a fix pack containing this APAR. * **************************************************************** A JAX-WS Web service that has the "document/literal wrapped" style uses JAXB "wrapper" classes to marshal and unmarshal the XML data. These wrapper classes are identified by the @RequestWrapper and @ResponseWrapper on the Service Endpoint Interface (SEI). Here is an example usage: @WebMethod @WebResult(name = "entry", targetNamespace = "http://sample") @RequestWrapper(localName = "findEntryByName", targetNamespace = "http://sample", className = "my.FindEntryByName" ) @RespoonseWrapper(localName = "findEntryByNameResponse", targetNamespace = "http://sample", className = "my.FindEntryByNameResponse" ) public AddressBookEntry findEntryByName( @WebParam(name = "firstname", targetNamespace = "http://sample") String firstname, @WebParam(name = "lastname", targetNamespace = "http://sample") String lastname); In almost all cases, the JAXB wrapper classes have an @XmlRootElement annotation. This annotation indicates that the JAXB class represents a root element in the schema. In the failing scenario, the JAXB wrapper class has an @XmlType annotation but does not have an @XmlRootElement annotation. In such cases, the wrapper class represents a root type but not a root element.
Problem conclusion
The JAX-WS runtime uses the JAXB framework to unmarshal XML messages. The JAXB framework provides an alternative unmarshaling algorithm if the target JAXB is not a root element. The JAX-WS runtime is changed to identify wrapper beans that are not root elements and use the alternative JAXB unmarshaling algorithm. This change avoids the UnmarshalException. 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
PM17067
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-06-23
Closed date
2010-07-01
Last modified date
2010-07-01
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
Modified date:
24 October 2021