In order to meet the spec requirements for handling server side events related to the view tier components, JSF also provides a front controller responsible for handling the server side request processing lifecycle, with event listeners and other plug-in points for either application code or controller-level frameworks (like something that would manage a wizard dialog). Without such functionality, JSF would have been useless without an application framework to provide the lifecycle services ... and, if everyone invents their own lifecycle, you'd end up with JSF components that were specific to a particular controller even though they conform to a common component API. That would have been fairly useless.
Shale proposes to leverage the extension points of this front controller instead of reinventing it yet again -- the world doesn't need YAWAF (yet another web application framework) that doesn't do anything new. It needs something that makes developing web applications in Java easier for non-rocket scientists. Craig On Wed, 3 Nov 2004 09:05:54 -0600, Michael Rasmussen <[EMAIL PROTECTED]> wrote: > > statement above clearly indicates that JSF goes well beyond that > > charter, and clearly suggests that there are facets of JSF that should > > not be a part of that JSR. > > > From the original design goals of JSR 127 (JSF) > "Provide a JavaBeans model for dispatching events from client-side > GUI controls to server-side application behavior." > > I read this as "Actions" in struts. > > > > Shale purports to depend on the parts of JSF that are unrelated to > > visual components, while visual components are the "raison d'etre" for > > JSF. So what, exactly, is the connection between JSF and Shale? > > > I could be totally wrong but I think the idea is to depend on these > classes to create the backbone for things like actions in struts > shale, using the ViewController as a JSF Managed Bean for event > handling in the controller. Craig? > > > > > And why does Shale need to be linked to JSF? > > > > -- > > Martin Cooper > > > > > > > > > > > Craig > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
