On May 11, 2009, at 3:15 PM, Gregory Gerard wrote:
> hi,
>
> Trying to figure out what I lose if I go the Spring route and what
> problems others have run into along the way with interegrated Spring
> and Jersey (performance, lack of functionality, unit testing, etc.)
>
AFAIK there are no limitations on using Jersey/JAX-RS features with
the Spring integration. In terms of unit testing people have used
Grizzly and Jetty for embedded containers. In terms of performance i
do not have any data but i doubt that the Jersey layer adds much,
essentially Jersey defers to Spring to instantiate a component and
Jersey gets the opportunity to inject onto that component. The
instantiation and injection is optimized at component initialization
time.
> While I do like Jersey / JAX-RS, Spring 3 looks like it's doing its
> own thing wrt binding requests via annotations. I see support on the
> slides but am looking for the more graceful, natural integration.
>
Can you present some more details on what you would like to see or
what was missing that made Jersey/JAX-RS integration less graceful or
less natural than you currently consider?
Paul.