Struts and Webwork
September 27, 2003 |
co.mments
I guess I'm looking forward to comparing WebWork and Struts for an application I'm building
Me too. There's something about Struts... I can't put my finger on it. A colleague put it this way - 'it has a learning curve', but I think I'm more concerned about maintaining/evolving a Struts solution than building it in the first place.
I looked at Tapestry last weekend. And after writing a simple app came to the conclusion I'm too stupid or lazy to 'get' it without (up to date) documentation and examples. It just didn't gel with me, even after digging in the code to find out how the bindings worked.
Onto webwork.
[foo fighters: low]
September 27, 2003 03:52 PM
Comments
Maybe also take a look at RIFE (http://rife.dev.java.net)? The users guide is available here : http://rifers.org/docs/usersguide/index.html and much example code is available, small applications as well as a few full-blown ones.
I work with Struts daily, and it does get tedious in terms of refactoring and the way to forces you to do things in certain ways. (you are forced to have ActionForms AND value objects, EVEN if the fields are the same, etc.)
Fortunatelly, I have great tool support for it in WebSphere Studio, so I can't complain.
Struts modules also help a lot with the complexity.
Regarding WebWork, I can't spend the time to figure it out without proper documentation, but I am excited about WW2's featureset.
A good friend recently tried WW1 and WW2 and he gave up for lack of comprehensive docs.
Also - have a look at Maverick:
I think I know what's wrong with Struts. I wrote about it here : http://www.synaesmedia.com/wiki/wiki.cgi?Struts/FirstImpression
Trackback Pings
TrackBack URL for this entry:
http://www.dehora.net/mt/mt-tb.cgi/1090