[
https://issues.apache.org/jira/browse/AXIS2-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223139#comment-13223139
]
Qiuzhuang Lian commented on AXIS2-3413:
---------------------------------------
Or in case if you still want JDOM to work in your project, you could copy this
lib into axis2/lib war to solve this error.
> Cannot use JDOM within Axis2 (java.lang.NoClassDefFoundError: org/jdom/Parent)
> ------------------------------------------------------------------------------
>
> Key: AXIS2-3413
> URL: https://issues.apache.org/jira/browse/AXIS2-3413
> Project: Axis2
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.3
> Reporter: Stefan Lischke
> Fix For: 1.4
>
>
> 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
> http://www.nabble.com/I-have-fixed-the-some-bugs-in-axis2-and-attaching-updates-to9734382.html#a9735592
> 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?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
