I would say you're correct, but WebWork does far less than Struts to dictate how the model is created. Struts is very simple in action: you get one model. WebWork creates a model as a composite of every Action invoked in a chain, so your "model" can actually be composed from the results of many beans... and the view has access to the models (pulling them) instead of being provided the model.
On Fri, 29 Nov 2002, liwz wrote: > Gentleman: > I have spent some time on WebWork,but I am not clear about the run > principle of webwork, just like Struts?I really want to see a graph about > the architecture. > From the document,I know webwork is a kind of "Pull HMVC" web > application framework.what is the different between "Pull HMVC" and normal > MVC. > I think MVC model in webwork means this: > Model is JavaBean created by user; > Controller is Servlet created in webwork lib and actions mapping > file; > View is all kind of view such as JSP/XSLT,etc. > Is it right? > > > > > --------------------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.com IT Consultant ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
