[
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: [email protected]
For additional commands, e-mail: [email protected]
