Hi,
I have created a new servlet that one can extend:
com.sun.ws.rest.spi.container.servlet.ServletContainer [1]
which can be used with a minimal set of jars. This servlet container
still requires the init-param "webresourceclass" to be set to configure
the WebApplication. And, it supports the injection of
HttpServletRequest, HttpServletRequest and ServletConfig.
The existing servlet:
com.sun.ws.rest.impl.container.servlet.ServletAdaptor
can still be used. It extends ServletContainer and provides additional
support for persistent units.
As a result the core runtime dependencies have been reduced, see here
[2]. When using the light weight HTTP server the minimum set is:
jersey.jar, jsr311-api.jar and http.jar (which is not required for SE 6).
Next up in this are could be to investigate how multiple deployed
servlets can share the same web application. This is useful if you want
utilize servlet filtering or authentication for some part of an
application, for example resources under "/admin" require HTTPS and
basic auth, but not split up the root resource classes into two sets.
Would anyone find this useful?
Paul.
[1]
https://jersey.dev.java.net/source/browse/jersey/trunk/jersey/src/spi/com/sun/ws/rest/spi/container/servlet/ServletContainer.java?view=markup
[2]
https://jersey.dev.java.net/source/browse/*checkout*/jersey/trunk/jersey/docs/dependencies.html
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jsr311.dev.java.net
For additional commands, e-mail: users-help_at_jsr311.dev.java.net