[
https://issues.apache.org/jira/browse/GERONIMO-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Jacques Parent closed GERONIMO-3894.
-----------------------------------------
Resolution: Fixed
Out of date
> java.lang.NoClassDefFoundError: org/jdom/Parent using JDOM 1.0
> --------------------------------------------------------------
>
> Key: GERONIMO-3894
> URL: https://issues.apache.org/jira/browse/GERONIMO-3894
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: core, webservices
> Affects Versions: 2.0.1
> Environment: OS : windows 2003
> Reporter: Jean-Jacques Parent
>
> We've got a problem using jDOM 1.0 with geronimo 2.0.1.
> Just using the following method : XPath.newInstance(String) we encounter the
> following error message.
>
> Caused by: java.lang.NoClassDefFoundError: org/jdom/Parent
> at org.jaxen.jdom.JDOMXPath.(JDOMXPath.java:91)
> at org.jdom.xpath.JaxenXPath.setXPath(JaxenXPath.java:281)
> at org.jdom.xpath.JaxenXPath.(JaxenXPath.java:99)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at org.jdom.xpath.XPath.newInstance(XPath.java:137)
>
> The class Parent is present in the jdom jar which is located in the lib
> directory of our web application. (Such as the jaxen beta 9 jar)
>
> We have seen on JIRA that there is a similar problem :
> AXIS2-3413 : Cannot use JDOM within Axis2 (java.lang.NoClassDefFoundError:
> org/jdom/Parent)
> But don't really understand which solution is to be applied.
> There is obviously a conflict with jaxen jar but what should we do exactly?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.