You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2009/01/21 00:35:59 UTC
[jira] Updated: (SM-1773) xercesImpl and xml-apis conflict when
running inside Jboss
[ https://issues.apache.org/activemq/browse/SM-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Custine updated SM-1773:
------------------------------
Assignee: Chris Custine
> xercesImpl and xml-apis conflict when running inside Jboss
> ----------------------------------------------------------
>
> Key: SM-1773
> URL: https://issues.apache.org/activemq/browse/SM-1773
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-components
> Affects Versions: 3.2.3, 3.3
> Environment: All platforms
> Reporter: Dave Stanley
> Assignee: Chris Custine
>
> When using the servicemix jboss deployer with JBoss 4.2.2 there is a conflict between the xercesImpl jar in <jboss>/lib/endorsed and the xerces and xml-api's in many of the Servicemix components. When using servicemix with jboss, this results in a stack trace similar to:
> http://www.nabble.com/file/p16140526/DeploySharedException.txt
> and the problems described in this thread:
> http://cwiki.apache.org/SM/discussion-forums.html#nabble-to15306485|a15306485
> The following components are pulling in xml-apis (xml-apis-1.3.04.jar) and xercesImpl:
> + /deployables/sharedlibraries/
> servicemix-shared
> And also (via a transitive dependency from shared) its being pulled into the following components
> + /deployables/bindingcomponents/
> servicemix-file servicemix-http servicemix-truezip target
> servicemix-ftp servicemix-jms servicemix-xmpp
> + /deployables/serviceengines
> servicemix-cxf-se servicemix-lwcontainer servicemix-script
> servicemix-bean servicemix-drools servicemix-wsn2005
> servicemix-eip servicemix-quartz servicemix-jsr181 servicemix-saxon
> The fix is just to add the xerces and xml-api's exclusion to servicemix-shared/pom.xml
> [1] http://svn.apache.org/repos/asf/servicemix/smx3/tags/servicemix-3.2.3/deployables/sharedlibraries/servicemix-shared/pom.xml
> [2] http://svn.apache.org/repos/asf/servicemix/components/shared-libraries/trunk/servicemix-shared/pom.xml
> {code}
> <dependency>
> <groupId>org.apache.servicemix</groupId>
> <artifactId>servicemix-soap2</artifactId>
> <exclusions>
> <exclusion>
> <groupId>xml-apis</groupId>
> <artifactId>xml-apis</artifactId>
> </exclusion>
> <exclusion>
> <groupId>xerces</groupId>
> <artifactId>xercesImpl</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> {code}
> I've verified that as both the xml api jars are also below <servicemix>/lib this change shouldn't have any negative affects. Also, this will reduce the footprint of the distribution by about 20mb ;-)
> I think instructions above should be sufficient to make change. Let me know if you want svn diff output and I will attach.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.