David Graham wrote:
Why should we duplicate the effort of the container inside Struts?

We often duplicate the effort of the container. Actions duplicate servlets. Modules duplicate multiple applications.


In each of these cases, the effect of the container feature is the same, but the justification has always been "it more lightweight".

In this case it's more heavyweight. We would have to alter the DTD, transform the new DTD elements to objects, code up the chaining mechanism, write unit tests, and deal with the bugs.


Adding a RequestHandler interface is *much* simpler and acheives the desired results (if not in the xml configuration manner some would prefer). It doesn't make sense to me, to disregard all the work that containers have put into Filters and write our own.

Even after implementing our own approach we would have to spend time supporting and modifying it. This especially seems like a waste of time given there's already a standard solution out there.

This reminds me of modules where they sounded like a great idea and then there's nobody to support the bugs.

David


*If someone wanted to write it*, I don't see that a composable request processor would have to be a 2.x change. The major changes could all take place within the process method, and the original RequestProcessor could remain available.


Things like the DTD may have to be expanded, but it would not be anything more radical than what we did between 1.0 and 1.1. [As if that's a good justification for anything =:0)]

-Ted.


-- Ted Husted, Struts in Action <http://husted.com/struts/book.html>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to