[jboss-dev-forums] [JBoss AS 7 Development] - Re: Spring-WS 1.5.9 on JBoss AS 7

[Alessio Soldano]

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,
> Melloware Inc wrote:
> 
> Alessio,
> 
> Thanks for responding.  To answer your question:
> 
> 1. I have turned on TRACE level logging but Jboss is eating the exception.  They are just throwing...
> 
> throw new SoapException("Unable to create message factory for SOAP:" + ex.getMessage);
> 
> ...and no stack trace, so I can see the root error.
Did you also add a logger category for org.jboss.modules package?


> 2. I thought someone might suggest installing CXF and Spring as a Jboss7 module.  However that defeats the purpose of a portable WAR file.  If I have Jetty 8, Tomcat 7 and Jboss 7AS in my organization now I need to build custom WAR files and deployments for each platform.  I would prefer not to have to know that Jboss 7 AS is the destination platform when I build my WAR file.  Plus it will require the Unix Admins here (I am not allowed to touch Production Servers) to have to tweak Jboss 7AS to put CXF and Spring as modules in the environment etc.  I want to keep configuration of the actual container to a minimum.
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&containerType=14&container=2225]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20111212/ea52d78f/attachment.html