On 12/13/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > First, it [JSF] is component oriented so it is easier to reuse > code between applications and easier to understand.
Struts can be easily made component-oriented. > Plus, the > components are STATEFUL, they keep their state between request and > that is a big advantage of JSF. In Struts, only the forms input > controls were stateful and only if your form beans had session scope. Have JSF invented another method to keep application state? In Struts one can use action form both for input and output, which makes it a conversational input/output object, a view buffer, a managed bean if you will. > Also, JSF provides a fine-grained event model à la Swing compare to > the coarse-grained event model of Struts (receive request, do > something). DispatchAction et al? > Finally, the best part of JSF comes from method and value > binding wich allows you to use normal Java Beans for your controller > (think of it as a Dispatch Action merged with an Action Form). Combining DispatchAction with ActionForm would be a simple change for Struts, without breaking compatibility. For some reason that did not happen [yet?]. <skipped> JSF has its benefits, but the features that you quoted are not unique for JSF. The same practices can be easily used with Struts. > Alexandre Poitras > Québec, Canada Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
