I'm not sure if this played into the original motivation, but it does make WebWork/Struts2 more flexible. Since you can actually use it as a filter for another Servlet. You just define what rules trigger the Struts Filter and the rest get processed by the Servlet. If Struts2 was a Servlet itself, you wouldn't have that option. (*Chris*)
On Wed, Jul 20, 2011 at 7:12 PM, Dave Newton <davelnew...@gmail.com> wrote: > You'd need to ask the original webwork devs. It's true that the servlet > spec > specifically states that filters should not be used to serve requests, but > as far as I can tell there's no compelling technical reason why that's so > stated. > > Dave > On Jul 20, 2011 9:57 PM, "Balwinder" <balwinder....@gmail.com> wrote: > > Hi All, > > > > I just want to understand why in Struts2 request is serviced by sub > > class of Filter class rather than specified and standard way of doing it > > through Servlet class? > > > > Regards, > > Balwinder Kumar > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > > For additional commands, e-mail: dev-h...@struts.apache.org > > >
