This post originated from an RSS feed registered with Java Buzz
by Jason Carreira.
Original Post: Russell Chooses Struts
Feed Title: Jason Carreira
Feed URL: http://sedoparking.com/search/registrar.php?domain=®istrar=sedopark
Feed Description: Personal Aggrandizement
I decided I'm just using Struts. Why? Because it has been blessed by Sun and it has an incredible amount of docs and support. There's like, what, 5 books, endless numbers of websites and constant work being done to improve it. I'm not Struts biggest fan, but I got it to work like I wanted it to with some tweaking so I'm sticking with it. I looked at developing my own simplified MVC, at JPublish, Cocoon and various Python systems, but decided in the end that Struts did what I needed it to do and for the most part got out of my way, so I went that way. There's a lot to be said for standards and Struts is becoming the MVC standard. (Don't jaw at me about WebWork. I looked at it and it just had *too many abstractions*. Bad.)
WebWork has *too many abstractions*? WTF? Abstractions are what make a framework powerful. If you just wanted to code Servlets, then just code Servlets... WebWork abstracts away the useless cruft of FormBeans, passing the Request and Response, etc...
Another point: Because it has been blessed by Sun and it has an incredible amount of docs and support. Blessed by Sun? When was this? Last I knew, Sun had put Craig McClanahan on JSF and he was basically saying that you should stop using Struts in 6 months when JSF is finalized (this was over a month ago, so make that 4 1/2 months now). I don't deny that Struts has a lot of tool and documentation support, but some frameworks need more tool support because they're too complex :-)
Do whatever you like, since it's your app, after all, but these seemed like silly reasons to me.