Do not package JAXP libraries within applications that use JAXB APIs

Packaging JAXP libraries within applications that have dependencies on JAXB APIs can cause linkage errors. In the event the application uses the JAXB implementation provided by WebSphere traditional, and JAXB then links to the JAXP implementation provided by the application, the application server can leak memory and the application will receive a ClassCastException .

This rule flags the first reference to the javax.xml.bind package when the application provides a javax.xml.datatype implementation and does not package a JAXB implementation.

To prevent this from happening one of the following must be done:

• Remove any JAXB or JAXP libraries provided by the application and use those provided by traditional WebSphere
• Provide both JAXB and JAXP from the application and use the PARENT_LAST classloader delegation when using traditional WebSphere.
• Remove JAXB and JAXP from the application and configure them as an isolated shared library associated with the application