Well, what kinds of conflicts at runtime are you getting? It looks to me like you should be fine relying on the xbean.jar that Axis2 has. I also think that it should be possible to replace the jar that Axis2 has with a newer version of XmlBeans (for instance, if you need a recent bug fix), but that is the more difficult path. Radu
________________________________ From: Vinh Nguyen (vinguye2) [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 1:46 AM To: [email protected] Subject: xmlbeans and axis2 Sorry for the repost, I meant to reach the larger audience. ________________________________ From: Vinh Nguyen (vinguye2) Sent: Friday, February 09, 2007 1:41 AM To: '[EMAIL PROTECTED]' Subject: xmlbeans and axis2 Hello, I'm using XmlBeans2.2.0 to generate java classes from my xsds, and am primarily using the classes for serialization to/from xml. I am deploying the generated classes in an Axis2 application. But, I see that Axis2 already has a xbean-2.2.0.jar, which appears to be the same as the xbean.jar in the XmlBeans2.2.0 libs. If I deploy all the XmlBean jars along with the Axis2 jars, I seem to get class conflicts at runtime. Does anyone know what jars in XmlBeans I really need to deploy with my app, or can I just use the ones in Axis2? If I need to deploy jars from both, how should I prevent conflicts between jars that contain the same classes, although possibly different class versions? Any help is appreciated, thanks! -Vinh _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
