Have Geek Brain

Local Java Web Services container?

I want to provide a Java based web service, but I do not need the full blown J2EE Application Server features. I would like it to start as quickly as possible, although this was not a hard requirement. The web service will handle multiple connections and requires access to the Oracle database so that it at least requires a thread pool and a database connection pool. I might want to add a JSP interface to it later to provide an internal support interface.

I looked at Jetty with Apache CXF stack, but it looks like I will need to do a little configuration before even coding the webservice - would it be worth it? Will this work? Should I forget the complexity and just go with JBoss / Weblogic / etc. And to please the bloat and extra startup time?

+2


a source to share


3 answers


I would go from JAX-WS RI to Jetty, Tomcat or GlassFish v3 (I disagree with others with other opinions expressed here, and according to my practical experience with GFv3, GFv3 offers a high performance development environment).



And please don't go Axis 2 (I won't even talk about its architecture and the terrible deployment and packaging model of hell, just take a look at JAX-WS RI 2.1) .

+4


a source


Setting up Tomcat 6 + Axis 2 is pretty straightforward . I would not recommend using JBoss / Glassfish / etc for your scenario - the overhead is far outweighed by the only benefit - no additional configuration was required.



+1


a source


I am using the inline jetty to display a range of jax-ws web services. Works really well and the configuration just involves taking things that I don't need from the dock.

+1


a source






More articles:


All Articles