Model Component
If webwork was replaced by some other framework chances of the Action class will be replaced by some thing else therefore it isn't a part of the model domain but tightly coupled to the WebWork controller, Another reason to consider the webwork Action class part of the controller is that it has access to the ServletDispatcher and therefore all of the controller resources which the model domain should not know about, so Action class is part of the controller.
My Explanation about WebWork Model is: Depending of the type of architecture ur application uses, the model portion can take many different forms. In a two tier application,where the web tier interacts diectly with a data store,the model classes may be a set of java classes. Where as in the case of complex enterprise application(Where web tier communicates with Ejb Server),the model portion will be a enterprise java bean.Joseph Ottinger wrote:
On Fri, 28 Mar 2003, Snehal K.Gandhi wrote:thnx, that's a clean explanation of the MVC on webwork, but i would like to share the model part of it as i read it in a boook.I don't understand what your response means. You would like to share.... the model part of it? I can't see any difficulty in that; it's a set of Actions, the valuestack introspects the set until it finds a value that matches a given name (actually, an expression that can go down attribute chains to find a value) to get values out of the model. But what does "as I read it in a book" mean?Joseph Ottinger wrote:On Fri, 28 Mar 2003, Hariharan wrote:Hi I would like to know in-depth about the Framework of Webwork.Pls explain about the Webwork Model Components.As I understand it, WebWork "model" components are actually composites, build through a stack, called the "ValueStack." Models are implementations of "Action," often extensions of "ActionSupport," and follow ordinary JavaBean semantics.if webwork was replaced by some other framework chances of the Action class will be replaced by some thing else therefore it isn't a part of the model domain but tightly coupled to the WebWork controller, Another reason to consider the webwork Action class part of the controller is that it has access to the ServletDispatcher and therefore all of the controller resources which the model domain should not know about, so Action class is part of the controller.Webwork View Components.One of WebWork's strengths is that view components are entirely up to the user. If you'd like to use JSP, that's fine. If you'd like to use Velocity, that's all right as well. If you'd like to use GUI components, that's easily accomplished. If you'd like to use a servlet (why?), I imagine that'd not be difficult either.Webwork Controller Components.WebWork uses a dispatcher as a Controller. I haven't done much with this, as it's a fairly workable black box; servlets are provided to give you easy access and use of a controller (for JSP and Velocity - the Velocity servlet doing a touch more work to store the valuestack components into the velocity context), and non-web dispatchers are easy to work with as well, I'd imagine.with regards Hariharan.P -- P.Hariharan Sip Technologies & Exports Ltd., G4 Elnet Software City, Taramani Chennai -113 e-mail [EMAIL PROTECTED] Phone 22541473/74 Ext 314 ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork--------------------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.com IT Consultant ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
-- Snehal K. Gandhi SIP Technologies & Exports Ltd., Software Engineer G4 Elnet SoftwareCity, Chennai Core Technology Group URL:http://www.siptech.com/ [EMAIL PROTECTED] Ph: +91-44-22541473/4 x313 --
