Hi Sara As I mentioned before on these lists Muse does not use SAAJ, only DOM. There may be jboss related issues with including xerces and xalan directly in a war, but these have nothing to do with Muse or with any SOAP stack.
Even with the axis2 platform the interface used is not SAAJ but axiom. Unfortunately j2ee apps are not generally portable, extra work must go into each deployment scenario. Child/Parent first classloader issues and different JDKs can all cause problems, OSGi is pretty much the only safe option (which of course brings its own issues). If you can provide a specific example of a problem we can try to help. cheers, Chris On Fri, Mar 13, 2009 at 7:31 AM, SARA1232007 <[email protected]> wrote: > > This wsrf war is developed for tomcat and it is successfully deployed and > runned on tomact. > > Since tomcat need an additional SOAP protocol stack which included in the > wsrf war, I guess the problem is that the SOAP protocol stack provided in > wsrf war is conflicted with that on JBoss. > > My question is: > Can the web service generated by muse platform be portable to the SOAP > protocol stack on JBoss? Can I solve the problem by just removing the SOAP > stack code provided in muse platform and deploy the war file regenerated on > JBoss? Which jar file the muse SOAP protocol stack? > > Thanks. > > SARA > -- > View this message in context: > http://www.nabble.com/Problems-of-running-muse-wrsf-example-on-JBoss-tp22471238p22490985.html > Sent from the Muse - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
