I'm not an expert on this, but I think it's a configuration option to automatically enable this behavior for Jetty 5 due to the performance hit. It may be that in Jetty 6 that it's turned on by default.
My point was that Mahbub might be able to download and install this filter into his 2.3 environment and be able to use Shale, although he might have to configure his app differently. On 8/3/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 8/2/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > > On 7/21/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > principally to allow us to use a ServletRequestListener and a > > ServletRequestAttributesListener to deal with the per-request lifecycle > event callbacks, > > plus the ability to impose filters on a RequestDispatcher.forward() call > if you want them. > > > >> Any suggestion on making latest nightly workable with servlet 2.3 / > JSP > > > 1.2 platforms? > > > > It *might* be technically feasible to mimic some of the functionality > using > > a filter in a 2.3 environment, but it is not technically possible to > support > > everything. Therefore, this combination (Shale and Servlet 2.3) is not > > going to be supported. > > For what it's worth, Greg Wilson of jetty considered > ServletRequestListener and ServletRequestAttributesListener "too > objectionable to include in the core of Jetty" and wrote a filter to > support them. > > http://www.mortbay.org/javadoc/org/mortbay/jetty/servlet/JSR154Filter.html > > Not sure about the "impose filters on a RequestDispatcher.forward() > call" part, though. > That is too bad ... I'll need to put Jetty on the "not supported" list if it does not support Servlet 2.4. Providing non-standard ways to achieve standard functionality seems to me like a road to irrelevance ... but I guess that's Greg's call for Jetty. I'm certainly not going to waste my time on a container that isn't going to stay up with at least the mainstream standards. On the other hand, I see that Jetty is an optional choice for the servlet container in Geronimo (a J2EE 1.4 container that therefore requires support for Servlet 2.4). Maybe he's had a change of heart since the javadocs referenced above were written :-). Craig Craig
