The first question I would ask myself is, "Am I going to take advantage of the features inherent in a heavier weight application server, such as JBoss, etc.?" If not, then there is no need to implement the extra overhead. That would greatly narrow down my selection to simpler containers, such as Tomcat. I don't believe WS-Security and WS-Trust require anything more than this. So, unless you're using a protocol not supported by Tomcat, or plan to use JVM clustering, I would go with the simple solution.
Just as an FYI, we've been using CXF since the days when it was a separate XFire project over at Codehaus. It's been running just fine in Tomcat all this time. Currently, we're running CXF 2.4.1 on Tomcat 6.0.32. Ron -----Original Message----- From: eaudet [mailto:[email protected]] Sent: Tuesday, October 11, 2011 1:56 PM To: [email protected] Subject: Best J2EE container with Apache CXF All, We have been enjoying Apache CXF to implement fairly complex message handling (HL7v3). We recently started to use WSS4J interceptors for content signature (inbound and outbound). It works great under jetty but we have major problems when deploying under WebSphere 7.0. This is not new to this forum. WebSphere I know! We are actually thinking implementing our ESB outside of WebSphere in an other J2EE container or even simply Tomcat. But before going down an other road then WebSphere, I would like to know what CXF users are actually using for J2EE container. Is it Geronimo? Is it Glassfish? any other that works well with all CXF features? Thanks for sharing your experiences. Before answering don't forget we are focusing on CXF WS-Security and WS-Trust features. - Erick -- View this message in context: http://cxf.547215.n5.nabble.com/Best-J2EE-container-with-Apache-CXF-tp4893036p4893036.html Sent from the cxf-user mailing list archive at Nabble.com.
