Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
1.3
-
None
Description
Axis2 is shipped with a vanilla jaxen-1.1.1.jar. If one will use JDOM inside his WebService Implementation, he will get a java.lang.NoClassDefFoundError: org/jdom/Parent Exception. Cause JDOM comes with a slightly modified version of jaxen jar. But the vanilla jar is earlier in the classpath so this version is taken.
The solution is to remove the vanilla jaxen jar and put the ones shipped with jdom into his aar
There was a question on the mailing list about this earlier
The solution was described here:
http://cvs.jdom.org/pipermail/jdom-interest/2005-May/014821.html
Why is the jaxen.jar in the axis2/lib directory? who needs it?