RE: JAXB (2.1) and AXIS2 (1.5.1)

...@gmail.com] Sent: Wednesday, January 13, 2010 14:35 To: axis-user@ws.apache.org Subject: Re: JAXB (2.1) and AXIS2 (1.5.1) This probably means that JAXB is trying to look up ObjectFactory and jaxb.index from the wrong class loader. This may happen if the JAXB JARs are loaded by the application class loader

Re: JAXB (2.1) and AXIS2 (1.5.1)

This probably means that JAXB is trying to look up ObjectFactory and jaxb.index from the wrong class loader. This may happen if the JAXB JARs are loaded by the application class loader, while the generated code is loaded from the service class loader. One solution would be to use the variant of the

JAXB (2.1) and AXIS2 (1.5.1)

Hi, I am deploying a WS under tomcat 5.5 and Java JDK is 1.5.0_08. I use some external jars that include code which was generated with JAXB 2.1 (using Ant XJC Task). The code is built from the xml schema without any error using the same JAXB libs as used in Axis2: jaxb-xjc-2.1.7.jar activatio