I have no idea why Craig would say that the RequestProcessor is somehow related to the Template Method pattern. It just isn't.
Are you talking about org.apache.struts.action.RequestProcessor? Even if its not a shining textbook example of "Template", it most certainly is related to that pattern. The "process(...)" method defines a sequence of operations as a number of method calls, and the indicated mechanism for extending the request process is to selectively implement changes to only those methods which you need to change, leaving "process()" as the "template" for normal operations.
The implementation of ComposableRequestProcessor leaves this pattern behind, as it reimplements the template method itself using almost none of the methods which were originally intended to define the request process. Maybe that's what you mean when you say that "it just isn't"?
As Ted said and whch makes sense to me, in another thread that is currently winding down:
Yes, once again, Ted eloquently summarized how we work. Thanks, Ted. It lets me just say "what he said."
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
