Craig, Could you briefly enumerate the advantages a filter would have over a servlet for what ActionServlet *currently* does? I can see how it would be useful for certain new features, and I can see how the context lifecycle events would be nice to monitor; but I'm not sure I see what a filter buys us for ActionServlet's current functionality.
Thanks, Donnie > -----Original Message----- > From: craigmcc@localhost [mailto:craigmcc@localhost]On Behalf Of Craig > R. McClanahan > Sent: Sunday, December 09, 2001 8:57 PM > To: Struts Developers List > Subject: Re: Struts & Filters (Servlets 2.3) > > > On Sun, 9 Dec 2001, Peter Heller wrote: > > > Date: Sun, 09 Dec 2001 20:36:34 -0500 > > From: Peter Heller <[EMAIL PROTECTED]> > > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Struts & Filters (Servlets 2.3) > > > > Will there be a subclass created in struts such as actionFilter ? > > > > Will the Struts filter be part of web.xml or struts-config.xml? > > > > I think the question being asked here is "will the Struts controller > functionality (currently implemented in ActionServlet) be implemented as a > javax.servlet.Filter from the Servlet 2.3 API?" It's a pretty interesting > question. > > Had the Servlet 2.3 API been available when Struts was originally > designed, it's a pretty sure bet that I would have implemented the > controller as a Filter instead of as a Servlet. This would have made > possible some interesting approaches to using the Struts controller in > front of (or in front of part of) existing applications that are being > migrated to Struts, as well as the "multiple controllers per webapp" > paradigm that we are currently discussing. > > However, that's not what happened. Struts is currently based on the > facilities of Servlet 2.2 and JSP 1.1, because that provides support on > the very broad range of application servers that support these APIs. I > feel that we ultimately want to migrate to Servlet 2.3 / JSP 1.2 to take > advantage of the new facilities -- the quesion is, when? > > We certainly need to continue to support the ability to run Struts based > applications on a Servlet 2.2 / JSP 1.1 platform for the forseeable > future. However, there are many compelling features of the next > generation APIs that are worth supporting. I'd like to see us explore > taking advantage of those capabilities by offering enhanced (or > alternative) implementations of the basic Struts controller functionality > based on the new APIs. > > What do the other developers think? Are there enough Servlet 2.3 / JSP > 1.2 environments available (obviously, I will be using Tomcat 4 for this, > since I'm pretty intimiate with its internals :-) to make development > *and deployment* of Servlet 2.3 / JSP 1.2 based applications useful, or is > it still a little too early? > > Even if it's too early, we can start exploring those sorts of ideas so > that we're ready when the platforms are readily available. > > Craig > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
