souravm wrote:
Will you consider Struts to be a better choice today compared to JSF ?

In *most* cases, for me, yes I would, but that's just my opinion, and I'm about to invalidate it at the end of this :)

> Especially, given the fact that JSF has better controller flexibility, event handling capability and ease of development using a RAD tool ?

I don't think any of those "facts" are "givens" in any way, shape or form. You could convince me event handling is better, maybe, but not the other two.

Controller flexibility is AT BEST a wash in my opinion (which is what you asked for), especially when your talking about S2. The interceptor stacks and result types, I believe, gives you just about all the flexibility you could ask for, and it's far from rocket science. Even with S1 you now have a chain-based request processor, and that gives you a ton of flexibility it you choose to use it.

As for ease of development with a RAD tool, you may well be right there, but to me, a big part of development is maintenance over time, and any time you have to rely on tooling to create an application, even in part, your asking for trouble down the road. Besides, I've heard stories of people who have used those RAD tools you speak of, only to find that they spend just as much time mucking around with the code they generate to get it to do exactly what they want/need as they would have spent just hand-coding is all in Struts. In the end, they saved little or no time, and possibly even wound up costing themselves some in the worst cases.

At the end of the day though, my belief still stands: look at your requirements and choose the right tool for the job. I used to be pretty strongly anti-JSF, but I've calmed down considerably... at this point I'm simply indifferent to it. I've had a couple of instances where JSF was seriously considered as a platform for a project, and I would have had little trouble going with it and working with it, there just wound up being some factors that made other choices be judged as better for the given situation. You should always do that, it's not just a matter of this or that is better than this or that in absolute terms, you can't make a general statement like that in my opinion. Don't use JSF because it's the "standard", don't use Struts because it's the most popular still after all this time, use one or the other (or something else entirely!) because it suits your needs better than the other for a given project, simple as that.

Regards,
Sourav

Frank

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
 (2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
 (2007, Apress, ISBN 1-59059-816-4)
Java Web Parts - http://javawebparts.sourceforge.net
 Supplying the wheel, so you don't have to reinvent it!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to