[
https://issues.apache.org/jira/browse/AXIS2-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574574#action_12574574
]
Davanum Srinivas commented on AXIS2-3413:
-----------------------------------------
Seriously, If JDOM comes with a modified version of jaxen it's JDOM's issue,
not ours..either way, if you don't want to run XPath over axiom, you can safely
remove the jar with no repercussions. It's not used internally in Axis2 or
AXIOM.
thanks,
dims
> Cannot use JDOM within Axis2 (java.lang.NoClassDefFoundError: org/jdom/Parent)
> ------------------------------------------------------------------------------
>
> Key: AXIS2-3413
> URL: https://issues.apache.org/jira/browse/AXIS2-3413
> Project: Axis 2.0 (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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
