PK93265: JAVAX.XML.BIND.JAXBEXCEPTION: [LMY.BEAN; IS NOT KNOWN TO THIS CONTEXT] ERROR OCCURS WHILE INVOKING A JAX-WS WEB SERVICE

Fixes are available

7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • While invoking a JAX-WS web service, a MarshalException error
    may occur on the client or on the server.
    
    The MarshalException will have one of the following linked
    errors:
       i) "javax.xml.bind.JAXBException: [Lmy.Bean; is not
    known to this context]".
      ii) "javax.xml.bind.JAXBException: java.util.List; is not
    known to this context]".
    
    
    Here is an example message from the web service indicating
    that the error has occurred on the server:
    
    <?xml version="1.0" encoding="utf-8"?><soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
    <soapenv:Fault>
    <faultcode>soapenv:Server</faultcode>
    <faultstring>
    javax.xml.bind.MarshalException - with linked exception:
    [javax.xml.bind.JAXBException: [Lservice.data.Cliente; is not
    known to this context]
    </faultstring>
    <detail></detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>
    
    Note: the "[Lmy.Bean;" is a Java Language description of an
    array of my.Bean.  In the customer's scenario this will
    designate the name of one of the application's arrays.
    
    This error will only occur if the web service is called with a
    web method that uses the document/literal wrapped style and
    the wrapper beans are not provided.  This is an uncommon
    scenario.  See the Problem Summary for more information.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
    *                  of JAX-WS                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: A JAXBException "[LMy.Bean; is not      *
    *                      known to this context] error occurs     *
    *                      while invoking a JAX-WS web service     *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack containing this APAR      *
    ****************************************************************
    While invoking a JAX-WS web service, a MarshalException error
    may occur on the client or on the server.
    
    The MarshalException will have one of the following linked
    errors:
       i) "javax.xml.bind.JAXBException: [Lmy.Bean; is not
    known to this context]".
      ii) "javax.xml.bind.JAXBException: java.util.List; is not
    known to this context]".
    
    
    Here is an example message from the web service indicating
    that the error has occurred on the server:
    
    <?xml version="1.0" encoding="utf-8"?><soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Body>
    <soapenv:Fault>
    <faultcode>soapenv:Server</faultcode>
    <faultstring>
    javax.xml.bind.MarshalException - with linked exception:
    [javax.xml.bind.JAXBException: [Lservice.data.Cliente; is not
    known to this context]
    </faultstring>
    <detail></detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>
    
    Note: the "[Lmy.Bean;" is a Java Language description of an
    array of my.Bean.  In the customer's scenario this will
    designate the name of one of the application's arrays.
    
    This error will only occur if all of the following conditions
    are met.
      A) The web service method is defined by the wsdl as a
         document/literal operation.
    
      B) The web service method uses the wrapper style.  This means
         that the name of the wsdl operation and the name of schema
         representing the data for the method are the same.  The
         rules for JAX-WS wrapper style are defined in the JAX-WS
         specification (chapter 2.3.1.2).
    
      C) When the JAX-WS document/literal wrapper style is used,
         the web method provides wrapper annotations.  These
         annotations locate the name of the class used to hold the
         request and response data.  If the annotations are not
         present, the JAX-WS runtime uses an algorithm to locate
         these wrapper classes.  The error only occurs if these
         wrapper classes are not found.  Here is an example of a
         method with wrapper annotations:
    
         @WebResult(name = "echoReturn",
                    targetNamespace = "urn://sample")
         @RequestWrapper(className="my.Echo"
                         localName="echo"
                         targetNamespace="urn://sample")
         @ResponseWrapper(className="my.EchoResponse"
                         localName="echoResponse"
                         targetNamespace="urn://sample")
        public String echo(List<Bean> in );
    
      D) The web method has a parameter or return value that is a
         java.util.List or an array.
    
    Note that it is common for a customer to have conditions (A),
    (B) and (D).
    
    Condition (C) is uncommon. Condition (C) only occurs if the
    customer has hand-written the web service instead of using a
    tool (wsimport) to produce the web service.  The use of the
    document/literal wrapper style without wrapper beans is not a
    best practice.  The customer should provide wrapper beans when
    using the document/literal wrapper style.
    

Problem conclusion

  • The use of the document/literal wrapper style without wrapper
    beans is not a best practice.  Though supported by the JAX-WS
    specification, it is not the intention of the specification.
    Some communities refer to this scenario as document/literal
    wrapper minimal due to the absence of the wrapper beans.
    
    Due to the rare use of this scenario, the JAX-WS engine
    algorithm for marshaling and unmarshaling arrays and Lists
    was not adequate.  This APAR improves that algorithm to ensure
    that the arrays and Lists are properly marshaled and
    unmarshaled.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.9.  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

    PK93265

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-06

  • Closed date

    2009-11-04

  • Last modified date

    2009-11-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
General

Software version:

7.0

Reference #:

PK93265

Modified date:

2009-11-04

Translate my page

Machine Translation

Content navigation