Quoting Nadeem Bitar <[EMAIL PROTECTED]>: > > Where and how do Managed Beans and JSF's navigation rules fit in a > struts/jsf application? >
It depends on whether you want all (or part) of your application to migrate to a JSF for the "controller" type features or not. In a pure-Struts app that is being modified to use JSF components, you probably won't use the JSF navigation rules very much -- your decision to stay with the Struts controller and Action architecture implies that you still want to use Struts facilities for managing the navigation (forwards and such), so they won't do you much good. The managed bean facilities are useful (even here) to load "backing beans" -- event handlers for UI events, such as the "RegistrationBacking" class in the example program that's included in the current nightly builds: http://cvs.apache.org/builds/jakarta-struts/nightly/struts-faces/ and managed beans are useful generally if you start using ValueBinding and MethodBinding APIs programmatically in your own code (very easy to do). You don't need to worry about the form bean itself, though ... that gets created on demand for you in the same way that standard Struts does it. With the newest beta, it is also possible to have an intermixed application that uses the Struts controller architecture for part of the app, and use JSF faclities for the remainder. In that scenario, you would of course be using managed beans and the JSF navigation rules for the JSF-based portion of the app. In general, though, I'd recommend sticking with one controller architecture for any partcular application, and think of this as primariy a transition assistance facility. 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]
