Hi,
Why you want to deploy one servlet per one "resource class" when you
can deploy one servlet with many resource classes using @Path?
You will not get the same level of support utilizing a Servlet as you
will utilizing a JAX-RS resource class. So depending on your
application you may be making things harder for yourself rather than
easier.
The plan for integration in EE 6 is:
1) for a JAX-RS application to annotation the implementation of the
javax.ws.rs.Application class so that one does not
have to create and/or edit the web.xml; and
2) for a root resource class to support the injection of EE artifacts.
We are waiting for the relevant specs to settle down a bit, then we
can update the APIs and implement.
Paul.
On Aug 9, 2009, at 7:04 PM, Felipe Gaścho wrote:
> I am thinking about a new pet project, and I did a POC here:
> http://kenai.com/projects/puj/lists/arena-dev/archive/2009-08/message/20
>
> The mini-project is for a competition project we are promoting in
> Brazil: http://kenai.com/projects/puj/pages/Home
>
> The code of my POC is Java EE 5 style, EJB 3.0 and using Jersey to
> expose business through a RESTful interface.... my plain old 2008
> code...
>
> Then I started to think about migrate this code to Java EE 6 using
> @WebServlet to do the REST part,..
>
> Is it already feasible to use Java EE 6 and @WebServlet ? (low to mid
> risk of be forced to rollback I mean....)
>
> and: @WebServlet means 1 servlet by resource ?
>
> I like Jersey, and my prime option is to keep with it.. but eventually
> JavaEE 6 bring me some even more easy way to do that... just
> thoughts...
>
>
> --
> Looking for a client application for this service:
> http://fgaucho.dyndns.org:8080/footprint-service/wadl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>