PK75322: JAVAX.XML.BIND.JAXBEXCEPTION <CLASS> IS NOT KNOWN TO THIS CONTEXT.

Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• When trying to invoke a JAX-WS web service, this exception
  might occur:
  
  [9/30/08 7:57:45:468 PDT] 00000020 ExceptionFact 1
  org.apache.axis2.jaxws.ExceptionFactory logRootCause
  stack:javax.xml.bind.JAXBException:
  com.somecom.lib.business.xml.ComIdentifierXml is not known to
  this context
  at
  com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBCont
  extImpl.java:538)
  at
  com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.getBea
  nInfo(UnmarshallerImpl.java:519)
  at
  com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmars
  hal(UnmarshallerImpl.java:319)
  at
  org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl$4.
  run(JAXBBlockImpl.java:513)
  at
  ...
  

Local fix

• Place the jar file in under war/WEB-INF/lib.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of JAX-WS clients running in          *
  *                  WebSphere Application Server Feature Pack   *
  *                  for Web Services.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: The error                               *
  *                      "javax.xml.bind.JAXBException:          *
  *                      <class> is not known to this context"   *
  *                      might occur.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When trying to run a JAX-WS client in WebSphere Application
  Server for Web Services, this exception might occur:
   .
   9/30/08 7:57:45:468 PDT  00000020 ExceptionFact 1
  org.apache.axis2.jaxws.ExceptionFactory logRootCause
  stack:javax.xml.bind.JAXBException:
  com.somecom.lib.business.xml.ComIdentifierXml is not known to
  this context
  at
  com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBCont
  extImpl.java:538)
  at
  com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.getBea
  nInfo(UnmarshallerImpl.java:519)
  at
  com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmars
  hal(UnmarshallerImpl.java:319)
  at
  org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl$4.
  run(JAXBBlockImpl.java:513)
  at
  ...
  .
  When the JAX-WS web service engine receives a message, it uses
  the JAXB engine to convert the message into java beans.
  The message indicates a failure occurred while converting xml
  into an object of type
  com.somecom.lib.business.xml.ComIdentifierXml.  The failure
  indicates that the JAXB engine was not initialized with
  information about this user class.
  .
  In this use case, the class
  com.somecom.lib.business.xml.ComIdentifierXml is packaged in a
  JAR at the EAR level. The exception does not happen if the
  class is packaged in a JAR located in the WAR module's
  WEB-INF/lib directory.
  

Problem conclusion

• The code that populates the JAXBContext with user classes is
  improved to consider classes that are packaged in JAR files at
  the EAR level.
  .
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 6.1.0.25.  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• WEBSVCS
  

Fix information

• Fixed component name

  WEBSERVIC FEATU

• Fixed component ID

  5724J0850

Applicable component levels

• R610 PSY

     UP