[ http://issues.apache.org/jira/browse/AXIS-1297?page=comments#action_12360360 ]
Tom Jordahl commented on AXIS-1297: ----------------------------------- Just remove the classes from the Axis 1.1 jaxrpc.jar. > Axis's jaxrpc.jar includes some interfaces from JAXP, causing class cast > exceptions in JBoss, possibly Tomcat > ------------------------------------------------------------------------------------------------------------- > > Key: AXIS-1297 > URL: http://issues.apache.org/jira/browse/AXIS-1297 > Project: Apache Axis > Type: Bug > Versions: 1.1 > Environment: Axis 1.1; JBoss 3.2.3, possibly Tomcat 4.x. Have seen on > Windows XP and Linux. > Reporter: John G. Norman > > The jaxrpc.jar shipped with Axis 1.1 includes interfaces that belong to JAXP. > They are: > javax/xml/transform/dom/DOMSource.class > javax/xml/transform/sax/SAXSource.class > javax/xml/transform/Source.class > javax/xml/transform/stream/StreamSource.class > Because on some servers, namely JBoss, JAXP is loaded by a different > classloader, class cast exceptions are produced when other Axis classes > expect these classes to be loaded by the same classloader. > (Note that it can be tricky on JBoss to alter the classloading mechanism for > a particular .ear or .war, and impossible in some cases without access to the > server setup.) > This is a blocker for many applications on JBoss, especially ones that need > to use a particular version of XML and also Axis. The presence of these JAXP > interfaces in Axis's jaxrpc.jar creates a conflict. > It seems very weird that the Axis jaxrpc.jar would include these interfaces, > anyway: They don't belong there. A developer should be able to put in place > his favored XML parser implementation. > For what it's worth, I made my own version of Axis's jaxrpc.jar that simply > omits these items, so that Axis just uses the JAXP items that are available > as part of normal JBoss startup. It seems to eliminate the typical class cast > exceptions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
