I don't think there is only one "preferred" scenario, because the starting points will vary widely. Option (a) is certainly going to be popular if you have an existing application that you are migrating, because you can do it one page at a time. Option (b) is really useful if you like the "setter injection" variation of IoC containers, because that's exactly what you get from the managed beans configuration capability. But both of these needs are quite legitimate, and can be used either together or separately in a single application.
JSF is designed to satisfy requirements in the view tier, and be able to plug in to larger application scale frameworks that provide controller and/or model capabilities. For simple applications, it is likely to be sufficient by itself. However, I think more complicated applications are going to want more, and I certainly believe that a future Struts should be a way to satisfy those needs. Craig On Wed, 22 Sep 2004 11:32:49 +0530, babloosony <[EMAIL PROTECTED]> wrote: > Hi All, > > what is preferred and in what scenarios out the below two when > integrating jsf and struts: > > a. accessing a struts form bean(used for populating jsf+jsp page) from > a struts action class > b. accessing a jsf managed bean(used for populating jsf+jsp page) from > a struts action class > > in jsf and struts integration, should we use jsf just for view tier > and struts for all client and server side validation+exception > handling+internationalization+tiles integration ? > > Thanks & Regards, > Kumar. > > --------------------------------------------------------------------- > 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]
