I'm pretty sure that making FilterDispatcher a Filter was a design decision so converting it to a servletdispatcher may not be as easy or as straightforward as one might think.
If memory serves ( and these days, that's not guaranteed ), it actually used to be a filter/servlet combination before it got rolled up in to a filter. For example, it wraps the servletrequest so that the EL can have access to the value stack. Also, it allows for the static dispatch of the templating themes. Coder emptor, is all. hth + gl, -a Shepherd, Darren S -2 wrote: > > All, > > > > This is regarding Struts 2.0. > > > > I've just ran into what I believe is a bug in WebSphere 6.0 and 6.1 where > the filter chain does not get hit on certain RequestDispatcher includes. > So I have two options here: > > > > 1. Get IBM to fix the bug > 2. Rewrite the Filter Dispatcher as a Servlet > > > > My experience is that if I engage IBM my bug will be fixed some time in > 2008 (seriously). I'm supposed to be in production before that. So let > me know if this is a terrible idea. I'm going to take the filter > dispatcher and turn it into a servlet. We do not serve static files from > struts. If we do wish to server static files, I will write a filter > specifically for that. > > > > Darren > > > -- View this message in context: http://www.nabble.com/Whats-the-harm-in-creating-a-Servlet-Dispatcher--tf4444401.html#a12737527 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
