Hi Farukh,
Are you going to utilize Jersey's Spring integration module
(contribs/jersey-spring)?
If yes, then all you need is a Servlet container (any low level http
servers are out of the game then).
You just stick with Servlet dependency there is no need to introduce a
direct dependency
to Grizzly or any other container.
If you are going to utilize a lower level HTTP container, then you
probably end up
writing an integration for that and Jersey. Would you be interested in
contributing that back?
~Jakub
P.S. I am afraid we do not maintain any comparing matrix for the
supported containers.
On 11.10.2011 22:53, Farrukh Najmi wrote:
>
> The following link lists several jersey containers:
>
> http://jersey.java.net/nonav/documentation/latest/chapter_deps.html#d4e1720
>
>
> Is there any matrix comparing these container features and tradeoffs?
>
> I need to be able to deploy a jersey server that uses spring IOC
> container with beans defines in spring application context files.
> My server need not support very large transaction rates so Grizzly may
> be overkill. I am not sure what is the difference between
> Simple HTTP Web server, Light weight HTTP server and Servlet containers.
>
> Thanks for your help.
>