Dakota Jack wrote:
The idea, I thought, was to use the Commands to supplant theI think there is on little design problem in struts that depends on the history: It would be much better, if Action is an interface. So you would have all possibilites to use POJOs, it must only implement the new Action-Interface. Secondly it were also much better, when the execute-Method must only take a context interface. So you have more flexibility and you have no servlet-things at the paramater signature:
RequestProcessor with a composable request processor. Some of the
present suggestions are so radical as to provide some question whether
Struts is going to be Struts. This is especially so of the suggestion
that we tie the ActionForm and the Action together. Might as well
just go to JSF and Shale?
public interface Action {
void execute(Context context);
}where Context is also an interface.
I have programmed this approach by myself (http://plstrutsit.sourceforge.net/architecture/index.html), but it were quite better, if this would be integrated in struts - with backwards compatibility to struts 1.1. You only need a new request-processor that can deal with such Action interfaces an can create such contexts.
Manfred
If anything, I would tie the ActionForm and the Action less together.
I don't care what you call an Action. I do care if it handles the request and returns an ActionForward. If you loose that, you loose Struts altogether in my opinion.
The whole command structure, remember, is only because you adapted the Template Method pattern for the parts of the composable request processor requiring the Command/Chain pattern to fix its difficulties. To decide for that reason that the Command/Chain structure is some pattern Valhalla is a serious error, in my opinion.
Jack
-- =========================================== Dipl.-Inf. Manfred Wolff Software Engineer ------------------------------------------- http://www.manfred-wolff.de http://www.struts-it.org -------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
