users@jersey.java.net

Re: [Jersey] [PATCH] SpringServlet doesn't quite work with Servlet Filters

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Mon, 16 Feb 2009 12:12:02 +0100

On Feb 16, 2009, at 11:37 AM, James Strachan wrote:

> Just a heads up - I spotted this when trying to use SpringServlet as a
> Servlet Filter and have submitted a fairly minor patch to fix it...
> https://jersey.dev.java.net/issues/show_bug.cgi?id=217
>
> Its a fairly minor issue - mostly due to WebComponent having a
> different ServletContext field to ServletContainer which should maybe
> be refactored a little to avoid similar issues surfacing.
>

Thanks. Doh, that is embarrassing.

I am going to fix this a long with another issue related to Guice
integration that Gili found [1], which requires that an HTTP servlet
implementation implement HttpServlet, which IMHO is wrong because
Servlet is the contract for invocations not HttpServlet and the latter
IIUC is not MUST requirement.

Given the Guice discussion i doubt the Guice developers will change
things. So i am going to make ServletContainer re-implement
HttpServlet and encapsulate WebComponent.

Paul.

[1] https://jersey.dev.java.net/issues/show_bug.cgi?id=219