I want to provide a Java-based web service, but I do not need the facilities of a fully developed J2EE application . I want to start it as soon as possible, although this is not necessarily a hard way the web service will handle many connections and access to an Oracle database will require access to at least one thread pool and database connection pool. I would like to provide a JSP interface later to provide an internal maintenance interface.
I have seen the Jetty with Apache CXF stack, but it seems that I have to do a proper amount of configuration before coding web service - would it be worth it? Will this also work? Should I forget about complexity and just go with jabos / weblog / etc and should stay with bloat and extra start-up time? I had to go with JADS-WS RI at JetTeal, Tomcat or Glassfish v3 (I
Comments
Post a Comment