> 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]
