IBM Support

PM10452: While running a JAX-WS application an IllegalAnnotationsException may occur

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While running a JAX-WS application an
    IllegalAnnotationsException may occur.
    
    Here is an example error:
    
    org.apache.axis2.AxisFault:
    com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2
    counts of IllegalAnnotationExceptions
    com.sample.BeanInterface
    is an interface, and JAXB can't handle interfaces.
    this problem is related to the following location:
    at
    com.sample.BeanInterface
    ...
    Two classes have the same XML type name
    "{http://com.sample". Use @XmlType.name and @XmlType.namespace
    to assign different names to them.
    this problem is related to the following location:
    at
    com.sample.MyService
    ..
    this problem is related to the following location:
    at
    com.sample2.MyService
    ...
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Feature    *
    *                  Pack for Web Services users of JAX-WS       *
    ****************************************************************
    * PROBLEM DESCRIPTION: While running a JAX-WS application an   *
    *                      IllegalAnnotationsException may occur   *
    *                      indicating a problem with @XmlType      *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack containing this APAR      *
    ****************************************************************
    While running a JAX-WS application an
    IllegalAnnotationsException may occur.
    
    Here is an example error:
    
    org.apache.axis2.AxisFault:
    com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2
    counts of IllegalAnnotationExceptions
    com.sample.BeanInterface
    is an interface, and JAXB can't handle interfaces.
     this problem is related to the following location:
      at
    com.sample.BeanInterface
    ...
    Two classes have the same XML type name
    "{http://com.sample". Use @XmlType.name and @XmlType.namespace
    to assign different names to them.
     this problem is related to the following location:
      at
    com.sample.MyService
    ..
     this problem is related to the following location:
      at
    com.sample2.MyService
    ...
    
    
    These errors indicate that the JAX-WS runtime did not find and
    load the application's JAXB classes.
    

Problem conclusion

  • The JAX-WS runtime examines the applications wsdl file and web
    service code to find all of the JAXB classes.
    
    The "<class> is an interface" error occurs because the JAX-WS
    runtime incorrectly loaded an interface that was in the same
    package as other JAXB classes.   The JAX-WS runtime is changed
    to avoid loading such classes.
    
    The "Two classes have the same XML type" error occurs because
    the JAX-WS runtime's search algorithm incorrectly loaded a
    class from a shared jar that had the same XML type as a class
    that was directly referenced by the application.  The search
    algorithm is changed to load the referenced class and avoid
    loading the second class.
    
    The changes correct the problem, and the exception will no
    longer occur.
    
    This same problem is fixed in the V7 WebSphere Application
    Server by APAR PM10783.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.33.  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

    PM10452

  • Reported component name

    WEBSERVIC FEATU

  • Reported component ID

    5724J0850

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-21

  • Closed date

    2010-03-26

  • Last modified date

    2010-03-26

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

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

    PM10783

Fix information

  • Fixed component name

    WEBSERVIC FEATU

  • Fixed component ID

    5724J0850

Applicable component levels

  • R610 PSY

       UP

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

Document Information

Modified date:
24 October 2021