Sorry, I couldn't resist. On 7/26/07, souravm <[EMAIL PROTECTED]> wrote: > > Regarding going for JSF due to componentization, I'm again not sure what > additional componentizations JSF does compared to struts. Apart from the fact > that JSF does not need a layer like Action Classes, all other components > (validator, managed bean, html tag libs etc.) are already there in Struts.
I don't know where you got the idea that JSF does not need a layer like Action Classes. This layer is where your UI logic will go - it's the layer that converts the incoming request parameters into an object that your backend/business layer can understand. It's true that you won't be required to extend a base action class, but make no mistake, you'll still have these objects. The only way you can avoid this layer is if you use a framework that allowed web requests to directly call your business logic object and pass fully populated business domain objects. I've experimented with one just for fun but if I were to ever use it in an actual app, I'd still have an "action" object layer for web-specific logic (redirection, view preparation, etc). One way to find out what JSF won't provide, or needs improvement on, in a bullet-list format, would be to take a look at what they've listed for the next major version. Read Section 2 of JSF 314 [1]. Hubert [1] http://www.jcp.org/en/jsr/detail?id=314 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
