geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Jacques Parent (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3894) java.lang.NoClassDefFoundError: org/jdom/Parent using JDOM 1.0
Date Mon, 10 Mar 2008 07:39:46 GMT


Jean-Jacques Parent commented on GERONIMO-3894:

First of all, thank you for your quick reply.
We have applied your solution and it works now. We encoutered some similar problems, which
were also due to jar conflicts. So we had to add another hidden class as follow :


If I understand well, by default the jar are always loaded from the parent classloader and
not from the WEB-INF/lib directory of our web application (such as weblogic does for example).
I find this quite dangerous because when I will migrate to Geronimo 2.0.2 which may contains
new versions of jar, I will have to check that my application still work with those versions.
The solution will be to hide (as above) all the jar of our web application and which are shipped
with Geronimo. This may be quite forcing to do.
Another solution may be to use the inverseClassloading flag of the 'Resource Adapter Geronimo
Deployment Plan' if this is its purpose.
What is the best practise?

> java.lang.NoClassDefFoundError: org/jdom/Parent using JDOM 1.0
> --------------------------------------------------------------
>                 Key: GERONIMO-3894
>                 URL:
>             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.(
>         at org.jdom.xpath.JaxenXPath.setXPath(
>         at org.jdom.xpath.JaxenXPath.(
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance(
>         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
>         at java.lang.reflect.Constructor.newInstance(
>         at org.jdom.xpath.XPath.newInstance(
> 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.

View raw message