I personally always use the filter. In case you will not map your
application (the jersey servlet) to a context (like /rest/*) you'll get less
troubles using the filter.
On Mon, Aug 2, 2010 at 18:24, John Lister <john.lister_at_kickstone.com> wrote:
> I was wondering if there are any benefits or disadvantages to using Jersey
> as a filter compared to running it as a servlet? It would seem to me the
> only difference is that the filter mapping code gets called before the
> servlet ones, which depending on your needs is either a good thing or not.
>
> Just wondered what people thought and used.
>
> Thanks
>
> John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>