You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Aldrin E Baroi (JIRA)" <xm...@xml.apache.org> on 2008/07/09 01:10:32 UTC
[jira] Created: (XMLBEANS-376) LinkageError: loader constraint
violation ... when resolving method
org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setUserData
LinkageError: loader constraint violation ... when resolving method org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setUserData
----------------------------------------------------------------------------------------------------------------------------
Key: XMLBEANS-376
URL: https://issues.apache.org/jira/browse/XMLBEANS-376
Project: XMLBeans
Issue Type: Bug
Affects Versions: Version 2.3
Environment: OS: Windows XP SP2
Java: JDK 1.6.0_06
JBoss 5.0.1 CR1
Reporter: Aldrin E Baroi
Priority: Minor
I get linkage error in JBoss 5.0.1 CR1 with XMLBean 2.3.0.
I have fixed the problem by creating xbean.jar from 2.3.0 source by modifying the following in the ANT build.xml file:
<!-- property name="build.compiler" value="javac1.4"/ --> <--- commented it out
<property name="javac.target" value="1.5"/> <--- changed value from 1.4 to 1.5
<fileset dir="build/classes/store" excludes="javax/**,org/w3c/**"/> <--- modified to exclude javax & org/w3c in "xbean.jar" target
Here is the partial stacktrace:
15:45:54,543 INFO [STDOUT] 2008-07-08 15:45:54,543 HDScanner INFO NotificationManager : Loading notifcation configuration...
15:45:54,746 ERROR [[/...ELIDED...]] Exception sending context initialized event to listener instance of class [...ELIDED...]
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setU
serData(Ljava/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object;" the class loader (instance of org/jboss/classloader/spi/base/BaseC
lassLoader) of the current class, org/apache/xmlbeans/impl/store/Xobj$NodeXobj, and the class loader (instance of <bootloader>) for interface org/w3c/dom/Node have different Class objects for the type org/w3c/dom/UserDataHandler used in the signature
at org.apache.xmlbeans.impl.store.Cur.createDomDocumentRootXobj(Cur.java:244)
at org.apache.xmlbeans.impl.store.Cur.createDomDocumentRootXobj(Cur.java:233)
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.<init>(Cur.java:2836)
...
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-376) LinkageError: loader constraint
violation ... when resolving method
org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setUserData
Posted by "Anton Kuzmin (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894007#action_12894007 ]
Anton Kuzmin commented on XMLBEANS-376:
---------------------------------------
I got this too with WLS 10.3 and jdk 1.6, xmlbeans-2.4.0.jar
Error 500--Internal Server Error
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.xml.dtm.ref.dom2dtm.DOM2DTMdefaultNamespaceDeclarationNode.getSchemaTypeInfo()Lorg/w3c/dom/TypeInfo;" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the current class, org/apache/xml/dtm/ref/dom2dtm/DOM2DTMdefaultNamespaceDeclarationNode, and the class loader (instance of <bootloader>) for interface org/w3c/dom/Attr have different Class objects for the type org/w3c/dom/TypeInfo used in the signature
at org.apache.xml.dtm.ref.dom2dtm.DOM2DTM.nextNode(DOM2DTM.java:570)
at org.apache.xml.dtm.ref.DTMDefaultBase._exptype(DTMDefaultBase.java:486)
at org.apache.xml.dtm.ref.DTMDefaultBase._type(DTMDefaultBase.java:462)
at org.apache.xml.dtm.ref.DTMDefaultBaseTraversers$DescendantTraverser.next(DTMDefaultBaseTraversers.java:709)
at org.apache.xpath.axes.AxesWalker.getNextNode(AxesWalker.java:335)
at org.apache.xpath.axes.AxesWalker.nextNode(AxesWalker.java:363)
at org.apache.xpath.axes.WalkingIterator.nextNode(WalkingIterator.java:195)
at org.apache.xpath.axes.NodeSequence.nextNode(NodeSequence.java:335)
at org.apache.xpath.axes.NodeSequence.runTo(NodeSequence.java:494)
at org.apache.xml.dtm.ref.DTMNodeList.(DTMNodeList.java:81)
at org.apache.xpath.objects.XNodeSet.nodelist(XNodeSet.java:346)
at org.apache.xpath.jaxp.XPathExpressionImpl.getResultAsType(XPathExpressionImpl.java:357)
at org.apache.xpath.jaxp.XPathExpressionImpl.eval(XPathExpressionImpl.java:100)
at org.apache.xpath.jaxp.XPathExpressionImpl.evaluate(XPathExpressionImpl.java:184)
at org.springframework.xml.xpath.Jaxp13XPathExpressionFactory$Jaxp13XPathExpression.evaluate(Jaxp13XPathExpressionFactory.java:112)
at org.springframework.xml.xpath.Jaxp13XPathExpressionFactory$Jaxp13XPathExpression.evaluateAsNodeList(Jaxp13XPathExpressionFactory.java:104)
at org.springframework.ws.transport.http.WsdlDefinitionHandlerAdapter.transformLocations(WsdlDefinitionHandlerAdapter.java:199)
at org.springframework.ws.transport.http.WsdlDefinitionHandlerAdapter.handle(WsdlDefinitionHandlerAdapter.java:127)
at org.springframework.ws.transport.http.MessageDispatcherServlet.doService(MessageDispatcherServlet.java:222)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3590)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
> LinkageError: loader constraint violation ... when resolving method org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setUserData
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: XMLBEANS-376
> URL: https://issues.apache.org/jira/browse/XMLBEANS-376
> Project: XMLBeans
> Issue Type: Bug
> Affects Versions: Version 2.3
> Environment: OS: Windows XP SP2
> Java: JDK 1.6.0_06
> JBoss 5.0.1 CR1
> Reporter: Aldrin E Baroi
> Priority: Minor
>
> I get linkage error in JBoss 5.0.1 CR1 with XMLBean 2.3.0.
> I have fixed the problem by creating xbean.jar from 2.3.0 source by modifying the following in the ANT build.xml file:
> <!-- property name="build.compiler" value="javac1.4"/ --> <--- commented it out
> <property name="javac.target" value="1.5"/> <--- changed value from 1.4 to 1.5
> <fileset dir="build/classes/store" excludes="javax/**,org/w3c/**"/> <--- modified to exclude javax & org/w3c in "xbean.jar" target
> Here is the partial stacktrace:
> 15:45:54,543 INFO [STDOUT] 2008-07-08 15:45:54,543 HDScanner INFO NotificationManager : Loading notifcation configuration...
> 15:45:54,746 ERROR [[/...ELIDED...]] Exception sending context initialized event to listener instance of class [...ELIDED...]
> java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setU
> serData(Ljava/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object;" the class loader (instance of org/jboss/classloader/spi/base/BaseC
> lassLoader) of the current class, org/apache/xmlbeans/impl/store/Xobj$NodeXobj, and the class loader (instance of <bootloader>) for interface org/w3c/dom/Node have different Class objects for the type org/w3c/dom/UserDataHandler used in the signature
> at org.apache.xmlbeans.impl.store.Cur.createDomDocumentRootXobj(Cur.java:244)
> at org.apache.xmlbeans.impl.store.Cur.createDomDocumentRootXobj(Cur.java:233)
> at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.<init>(Cur.java:2836)
> ...
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-376) LinkageError: loader constraint
violation ... when resolving method
org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setUserData
Posted by "yanke (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852802#action_12852802 ]
yanke commented on XMLBEANS-376:
--------------------------------
We had this problem on WLS 10.3 (weblogic running on jdk1.6)
I manually removed from xmlbeans-2.3.0.jar 4 classes (org.w3c.dom.*) and published the new jar in our intranet maven repository with a different classifier:
<groupId>org.apache.xmlbeans</groupId>
<artifactId>xmlbeans</artifactId>
<version>2.3.0</version>
<classifier>java6</classifier>
with this new jar our application works in both tomcat and Weblogic (with JDK6)
What do you think of this approach?
Had you implemented a special logic inside the org.w3c.dom classes that we will miss when using specific xmlbeans functionality?
If our approach is fine, would you publish a similar jar (without org.w3c.dom classes) also in maven official repo?
thanks for your feedbacks,
Yanke
> LinkageError: loader constraint violation ... when resolving method org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setUserData
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: XMLBEANS-376
> URL: https://issues.apache.org/jira/browse/XMLBEANS-376
> Project: XMLBeans
> Issue Type: Bug
> Affects Versions: Version 2.3
> Environment: OS: Windows XP SP2
> Java: JDK 1.6.0_06
> JBoss 5.0.1 CR1
> Reporter: Aldrin E Baroi
> Priority: Minor
>
> I get linkage error in JBoss 5.0.1 CR1 with XMLBean 2.3.0.
> I have fixed the problem by creating xbean.jar from 2.3.0 source by modifying the following in the ANT build.xml file:
> <!-- property name="build.compiler" value="javac1.4"/ --> <--- commented it out
> <property name="javac.target" value="1.5"/> <--- changed value from 1.4 to 1.5
> <fileset dir="build/classes/store" excludes="javax/**,org/w3c/**"/> <--- modified to exclude javax & org/w3c in "xbean.jar" target
> Here is the partial stacktrace:
> 15:45:54,543 INFO [STDOUT] 2008-07-08 15:45:54,543 HDScanner INFO NotificationManager : Loading notifcation configuration...
> 15:45:54,746 ERROR [[/...ELIDED...]] Exception sending context initialized event to listener instance of class [...ELIDED...]
> java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.xmlbeans.impl.store.Xobj$NodeXobj.setU
> serData(Ljava/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object;" the class loader (instance of org/jboss/classloader/spi/base/BaseC
> lassLoader) of the current class, org/apache/xmlbeans/impl/store/Xobj$NodeXobj, and the class loader (instance of <bootloader>) for interface org/w3c/dom/Node have different Class objects for the type org/w3c/dom/UserDataHandler used in the signature
> at org.apache.xmlbeans.impl.store.Cur.createDomDocumentRootXobj(Cur.java:244)
> at org.apache.xmlbeans.impl.store.Cur.createDomDocumentRootXobj(Cur.java:233)
> at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.<init>(Cur.java:2836)
> ...
--
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org