[jira] Commented: (GERONIMO-3894) java.lang.NoClassDefFoundError: org/jdom/Parent using JDOM 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828049#action_12828049 ] Jean-Jacques Parent commented on GERONIMO-3894: --- Can close this issue. Quite old, 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.
[jira] Commented: (GERONIMO-3894) java.lang.NoClassDefFoundError: org/jdom/Parent using JDOM 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576888#action_12576888 ] 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 : org.jaxen org.apache.axis2 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: 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.
[jira] Commented: (GERONIMO-3894) java.lang.NoClassDefFoundError: org/jdom/Parent using JDOM 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574983#action_12574983 ] Kevan Miller commented on GERONIMO-3894: Create a Geronimo deployment plan (assuming you don't already have one). Like the following http://geronimo.apache.org/xml/ns/j2ee/web-1.1"; xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1"; xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1";> org.mygroup MyApp 1.0 car org.jaxen Assumin you've called this file NoJaxen.xml, you can deploy using: ./bin/deploy.sh NoJaxen.xml > 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.
[jira] Commented: (GERONIMO-3894) java.lang.NoClassDefFoundError: org/jdom/Parent using JDOM 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574963#action_12574963 ] Manu T George commented on GERONIMO-3894: - Have you tried using hidden-classes to hide the conflicting classes in the parent classloaders? JDOM is shipped with G. So by default the JDOM jar loaded will be from the parent classloader and will not pick up the jaxen jar in your application. Try hiding org.jdom and org.jaxen as I understand you package both in your application > 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.
