Low overhead Java Web Services container?

I want to provide a Java-based Web Service, but I don't require the features of a full-blown J2EE Application Server. I would like it to start as quickly as possible, though that's not a hard requirement. The Web Service will handle multiple connections and require access to an Oracle database so it will at least require a thread pool and database connection pool. I may want to put a JSP interface onto it later to provide an internal maintainence interface.

I have looked at Jetty with an Apache CXF stack, but it looks like I'll have to do a fair amount configuration before even c开发者_开发百科oding the web service - Will it be worth it? Will it even work? Should I forget about the complexity and simply go with JBoss/Weblogic/etc and put up with the bloat and extra start-up time?

I'd go with JAX-WS RI on Jetty, Tomcat or GlassFish v3 (I do not agree with other opinions expressed here and according to my practical experience with GFv3, GFv3 offers a highly productive environment for development).

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

Setting up Tomcat 6 + Axis 2 is fairly easy. I wouldn't recommend using JBoss/Glassfish/etc for your scenario - the overhead far outweighs the only benefit - no additional setup involved.

I am using embedded jetty for exposing a number of jax-ws webservices. Works pretty well, and configuration involved just stripping off things I didn't need from jetty.