On 11/12/05, Ted Husted <[EMAIL PROTECTED]> wrote: > Now about the whole "what to call it" thing :) > > We've called everything else "Action", why not call the framework that too? :)
+1 Better that previous attempts. > Struts Action in a Nutshell > > The framework's controller class, also called "Action", acts as a > bridge between the application's Model and the web View. When a > request is received, the Request Processor invokes an Action class. According to http://java.sun.com/blueprints/corej2eepatterns/Patterns/FrontController.html it seems to me that Action is a Dispatcher: * ActionServlet, RequestProcessor: Controller (J2EE); Handler (.NET) * Action: Dispatcher (J2EE); part of Command (.NET) * ActionForm: part of Command (.NET) * JSP page: view On 11/12/05, Martin Cooper <[EMAIL PROTECTED]> wrote: > Also, I prefer "action-oriented" and "component-oriented" over "action/page" > and "event/component". Right, because it is possible (and easy) to use event-based approach in Struts (DispatchAction et al). Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
