The new version of Orbeon has included a version of xml-apis.jar in the
WEB-INF/lib directory. It includes version 1.4.01.
Is this intentional? Is it really required?
We are running on an older appserver, JBoss 6.1, that has its own quirky
class loading scheme.
The issue we are seeing is that the various xml-apis classes (org.w3c.dom)
are loaded from the JDK's rt.jar when jboss starts up and then these loaded
versions are clashing with the versions loaded from the xml-apis jar
included in Orbeon when the war starts up.
Jboss uses multiple class loaders and you often get problems when the same
class is loaded by two different class loaders.
If I remove the xml-apis jar file from the orbeon war so it reverts to using
the JDK supplied version I get a java.lang.NoClassDefFoundError for
org/w3c/dom/ElementTraversal which is a class that didn't exist in version
1.3 of xml-apis (as included in the JDK). We are running JDK 1.7 but 1.8 and
1.9 are using the same 1.3 version of the xml-apis.
I would think this issue is not only going to affect us and our old
appserver but is likely to cause other problems for other users. I assume
Tomcat is OK with it since you are testing in Tomcat. What about other
appservers?
This will prevent us upgrading past 2017.1 until we update our appserver to
Wildfly 11 but even then I'm not ruling out the possibility that the
clashing version won't cause us more problems.
thanks,
brian...
--
Sent from:
http://discuss.orbeon.com/--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
To post to this group, send email to
[hidden email].
Locked
