class load issue

Hi we are Ts7.2 migrating existing code

we are facing following error in our code it says there is class load conflict error b/w jboss and rt.jar javax.xml.xpath pagkage. We are not able to resolve till now
Thanks

java.lang.LinkageError: loader constraint violation: when resolving field "NODE" the class loader (instance of org/jboss/mx/loading/UnifiedClassLoader3) of the referring class, javax/xml/xpath/XPathConstants, and the class loader (instance of ) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type
at com.amfam.interwoven.teamsite.common.XMLMailer.appendToXML(Unknown Source)
at com.amfam.interwoven.teamsite.deploy.WFDeploy.execute(Unknown Source)

Find more posts tagged with

Comments

Rick Poulin

Ran into the same problem a while back. My fix was to help the JBoss ClassLoader "pick one" at runtime, by doing an import like:
import javax.xml.xpath.*;
instead of specifically importing XPathConstants and other classes in that package.

rohitsoi1

Ran into the same problem a while back. My fix was to help the JBoss ClassLoader "pick one" at runtime, by doing an import like:
import javax.xml.xpath.*;
instead of specifically importing XPathConstants and other classes in that package.

Hi,

I treid it but same error could you please elobrate it how exactly you included and it would be nice if you could put some code snippt

Rick Poulin

To be honest, I was surprised when that had worked for me. It was at the long end of trying all sorts of things including pulling my hair out, but the code also worked on another server afterwards so I thought that had been it.

I'm not doing anything special really..

import javax.xml.xpath.*;

// ...
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
org.w3c.Document doc = dbf.newDocumentBuilder().parse(inputstream);
XPath xp = XPathFactory.newInstance().newXPath();
XPathExpression exp = xp.compile("/my/xpath/query");
(NodeList) res = (NodeList) exp.evaluate(doc, XPathConstants.NODESET);
// ...

rohitsoi1

To be honest, I was surprised when that had worked for me. It was at the long end of trying all sorts of things including pulling my hair out, but the code also worked on another server afterwards so I thought that had been it.

I'm not doing anything special really..
import javax.xml.xpath.*;

// ...
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
org.w3c.Document doc = dbf.newDocumentBuilder().parse(inputstream);
XPath xp = XPathFactory.newInstance().newXPath();
XPathExpression exp = xp.compile("/my/xpath/query");
(NodeList) res = (NodeList) exp.evaluate(doc, XPathConstants.NODESET);
// ...

I do not think this import all the classes is solving problem.. It might be possible that on new enviroment you different jars that worked out.. please check what jars you have removed ...

jsankara

I had the same issue. I replaced XPATH parsing with DOM / SAX parsing .. It worked for me.

Not sure how to fix the original issue [importing XPathConstants]...

Rick Poulin

I didn't remove any JARs. Messing with the application container is the last thing I want to do, since I hope/expect that Autonomy will be upgrading to a less ancient of JBoss soon.