If we're talking about making Struts independent of Servlets, then what part of Struts would depend on either Servlet 2.3 or Servlet 2.4?
Rather, how will we partition Struts so that we know our boundaries? Presumably in a chain-like world, you could have Servlet 2.3 pre-processing chains and Servlet 2.4 pre-processing chains, and of course we're going to have view post-processors for XSLT, Velocity... so why shouldn't there be JSP 1.2 and JSP 2.0 post-processors?
I suppose we ought to draft a glossary to make sure we all agree on these various concepts...
Joe
At 10:51 AM -0800 12/18/03, Craig R. McClanahan wrote:
For the portions of the framework that depend on Servlet 2.4, you get two modest but useful features:
* Ability to execute filters on RequestDispatcher.include and RequestDispatcher.forward calls, which is not possible in 2.3. This gives you additional degrees of freedom in how you organize the processing logic of a framework like Struts -- for example, it would now be technically feasible to implement the controller as a filter instead of a servlet.
* Ability to define request lifecycle listeners (like the older ones for session and application lifecycle) so you get a complete and consistent event handling model.
If your presentation tier is based on JSP 2.0 (instead of 1.1/1.2), you get a very large number of benefits. The most visible ones are:
* New ***much*** simpler API for building tag classes (tag instance pooling is gone, single invocation method instead of doStart/doEnd, ability to define a tag that takes an arbitrary list of attributes, ...).
* Tag files -- essentially, the ability to write a tag handler using JSP code instead of Java, complete with parameter passing.
* EL expressions evaluated everywhere (even template text), so you don't need to limit yourself to just tags that implement support for it (meaning we don't need struts-el variants).
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "We want beef in dessert if we can get it there."
-- Betty Hogan, Director of New Product Development, National Cattlemen's Beef Association
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
