Re: [undertow-dev] Jersey on Undertow, without servlets?
Thanks Stuart.
If grizzly2-http is any indication, this should be possible with
500-1000 lines of code. That's not as bad as I thought it would be.
-Michael
On Tue, Apr 7, 2015 at 11:21 PM, Stuart Douglas <sdouglas(a)redhat.com> wrote:
I think you would need to implement your own container. Looking at
https://github.com/jersey/jersey/tree/master/containers there are a few existing container
implementation that don't use servlet, you could probably just base it off one of
these.
Stuart
----- Original Message -----
> From: "Michael Hixson" <michael.hixson(a)gmail.com>
> To: undertow-dev(a)lists.jboss.org
> Sent: Wednesday, 8 April, 2015 3:12:59 PM
> Subject: [undertow-dev] Jersey on Undertow, without servlets?
>
> Hello,
>
> Has anyone run a Jersey application on Undertow, *without* using servlets?
>
> By "using servlets" I mean wrapping an
> org.glassfish.jersey.server.ResourceConfig in an
> org.glassfish.jersey.servlet.ServletContainer and deploying that with
> undertow-servlets. That's pretty easy to do; I don't have any
> complaints about it. My question comes mostly from curiosity.
>
> In my application, ServletContainer is the only connection to the
> servlet API. My naive view is that the application could be simpler
> (in terms of the number of hidden gears turning to process requests)
> and more efficient by avoiding the servlet API completely, and by only
> using undertow-core. Maybe I'm wrong, or maybe there is so much work
> involved that no one in their right mind would try it.
>
> -Michael
> _______________________________________________
> undertow-dev mailing list
> undertow-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/undertow-dev
>