No I did not get time to investigate this any futher. I've had to put this aside and I worked on the apache-servicemix-web component to be able to use the coyote and tomecat provided by jboss with servicemix, and FYI this worked great. I will get back on this issue later.
gnodet wrote: > > Did you manage to solve this issue ? > > On 1/29/07, Eric Dofonsou <[EMAIL PROTECTED]> wrote: >> >> >> >> Hello >> I've ran into another issue with regards to using servicemix inside >> jboss, >> this time around it's with the eip component. Before I investigate this >> any >> further I wanted to first share my troubles with you guys :-) >> >> Here is the content of my jbi.xml file that uses the eip components >> wiretap >> and xpath router) >> ------------ >> <eip:content-based-router >> service="cah:AppAccessDeviceServiceRouter" >> endpoint="AppAccessDeviceServiceRouterEndpoint"> >> <eip:rules> >> <eip:routing-rule> >> <eip:predicate> >> <eip:xpath-predicate >> xpath="*[local-name()='createResponse']"/> >> </eip:predicate> >> <eip:target> >> <eip:exchange-target >> service="cah:AppAccessDeviceServiceWireTap" >> endpoint="AppAccessDeviceServiceWireTapEndpoint"/> >> </eip:target> >> </eip:routing-rule> >> <eip:routing-rule> >> <!-- there is no predicate, so this is the default >> destination --> >> <eip:target> >> <eip:exchange-target >> service="cah:AppAccessDeviceWebServiceProvider" >> endpoint="AppAccessDeviceWebServiceProviderEndpoint"/> >> </eip:target> >> </eip:routing-rule> >> </eip:rules> >> </eip:content-based-router> >> ----------- >> >> However when lauch jboss with my component in the deploy folder I get the >> following error : >> Caused by: java.lang.LinkageError: loader constraints violated when >> linking >> javax/xml/namespace/QName class >> at >> org.apache.servicemix.expression.JAXPXPathExpression.<init>(JAXPXPathExpression.java:47) >> at >> org.apache.servicemix.expression.JAXPBooleanXPathExpression.<init>(JAXPBooleanXPathExpression.java:35) >> at >> org.apache.servicemix.eip.support.XPathPredicate.<init>(XPathPredicate.java:39) >> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native >> Method) >> at >> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) >> at >> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) >> at >> java.lang.reflect.Constructor.newInstance(Constructor.java:494) >> at >> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:84) >> ... 72 more >> ------------ >> >> My guess is this has to do with confilcting javax.xml.namespace.* classes >> in >> my classpath. I know that servicemix uses the stax-api-1.0.1.jar file for >> the javax.xml.namespace ? could this be the issue ? or am'I missing on >> something much more simpler here ? >> -- >> View this message in context: >> http://www.nabble.com/eip-component---jboss---linkage-error%21-tf3137741s12049.html#a8695703 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Architect, LogicBlaze (http://www.logicblaze.com/) > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/eip-component---jboss---linkage-error%21-tf3137741s12049.html#a8858801 Sent from the ServiceMix - User mailing list archive at Nabble.com.
