Alessio Soldano [http://community.jboss.org/people/asoldano] created the discussion "Re: Spring-WS 1.5.9 on JBoss AS 7" To view the discussion, visit: http://community.jboss.org/message/641015#641015 -------------------------------------------------------------- Hi, Did you also add a logger category for org.jboss.modules package? Well, generally speaking when deploying on JBoss AS you should consider you're deploying against a Java EE container that comes with webservices functionalities, hence you're not supposed to provide your own ws impl. If you want to use JBoss AS 7 as a "simple" web container, an idea might be to disable the webservices subsystem in the standalone configuration you're using. I didn't try that, but I guess that might work for you in this case. There're multiple reasons for having the CXF libs included in the AS, most of them basically comes from JavaEE certification requirements. To be honest, there's even https://issues.jboss.org/browse/AS7-537 https://issues.jboss.org/browse/AS7-537 (part of https://issues.jboss.org/browse/AS7-388 https://issues.jboss.org/browse/AS7-388) which is about filtering out Apache CXF libs in user deployments to avoid clashes. Generally speaking, a portable application should be built using standards only. So write a standard jaxws application with no direct reference to Apache CXF, Spring, etc. and you won't have portability problems (you'd just have to apply minor changes to web.xml descriptor for stuff not covered by spec there, but nowadays you can even get rid of web.xml...). If you're directly leveraging specific implementation / libs / tools, unfortunately you need to deal with this kind of issues. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/641015#641015] Start a new discussion in JBoss AS 7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]