Details
-
Bug
-
Resolution: Fixed
-
Medium
-
2.10.2
-
None
-
3
-
Description
From JDK 1.5 this class is inluded in the JDK, so there is no need to ship that class anymore with Confluence. The real problem here is that you can configure certain app servers like WebLogic to prefer loading classes from the web application, which is a good thing, but leads to the app server loading other classes in the javax.xml.namespace package using the app server class loader and only the QName class using the web app class loader. This gives you a LinkageError because the app server class loader doesn't allow classes for that package to be loaded from a different class loader.
The class is namely in two JAR files:
- stax-api-1.0.1.jar (can be replace by stax-api-1.0-2.jar)
- axis-jaxrpc-<version>.jar (could probably be replaced with geronimo-spec-jaxrpc-1.1-rc4.jar, but it is missing javax.xml.messaging.Endpoint and javax.xml.messaging.URLEndpoint)
Attachments
Issue Links
- is related to
-
CONFSERVER-15146 Saving a page or Switching to wiki markup fails with java.lang.AbstractMethodError: getTextContent error in Weblogic
- Closed
- relates to
-
CONFSERVER-15332 Page tree view doesn't work under Weblogic 10.x
- Closed