Comments on: Which framework to use? http://www.fuzzylizard.com/archives/2005/04/08/523/ My thoughts on Agile, Java and Ruby on Rails (mostly) Tue, 06 Jan 2009 00:10:07 +0000 http://wordpress.org/?v=2.7 hourly 1 By: fuzzylizard http://www.fuzzylizard.com/archives/2005/04/08/523/comment-page-1/#comment-501 fuzzylizard Sat, 09 Apr 2005 02:06:09 +0000 http://www.fuzzylizard.com/archives/2005/04/08/523/#comment-501 I have used Struts in the past and never really liked it. The only reason that it made it to the list was because it seems to be the industry standard when it comes to web frameworks. I think the decision is really between Tapestry and Wicket. Currently I am leaning more towards Tapestry only because it is the more established of the two frameworks. However, I have not really researched either completely so there is lots of room for me to make up my mind. As for Echo, I have not done any investigation into it so I may add it to my list of things to check out. Thanks for the comments and sorry for spelling Wicket wrong (this has since been corrected). I have used Struts in the past and never really liked it. The only reason that it made it to the list was because it seems to be the industry standard when it comes to web frameworks. I think the decision is really between Tapestry and Wicket. Currently I am leaning more towards Tapestry only because it is the more established of the two frameworks. However, I have not really researched either completely so there is lots of room for me to make up my mind.

As for Echo, I have not done any investigation into it so I may add it to my list of things to check out.

Thanks for the comments and sorry for spelling Wicket wrong (this has since been corrected).

]]> By: Eelco http://www.fuzzylizard.com/archives/2005/04/08/523/comment-page-1/#comment-498 Eelco Fri, 08 Apr 2005 20:51:34 +0000 http://www.fuzzylizard.com/archives/2005/04/08/523/#comment-498 Well, since I am one of the developers of Wicket, I am baised. But, I would really argue that you pick a component based framework. The 'Model2' frameworks (like Spring MVC, Struts or - another I was/am active on, Maverick) work fine for sites with not-too complex interfaces. But when you start to build larget, more complex interfaces, you'll end up in a nightmare. I did tons of projects in Struts and Maverick (and some other model 2 stuff), and two in Wicket, and finally, I can add complexity to my pages, without being pulled into a swamp. So, IMHO you should go with Wicket if 1 and 4 (and 2, as you'll find the community support really good) weigh heaviest, or with Tapestry or Echo if 2, 3 and 5 weigh the heaviest. Eelco Well, since I am one of the developers of Wicket, I am baised. But, I would really argue that you pick a component based framework. The ‘Model2′ frameworks (like Spring MVC, Struts or - another I was/am active on, Maverick) work fine for sites with not-too complex interfaces. But when you start to build larget, more complex interfaces, you’ll end up in a nightmare. I did tons of projects in Struts and Maverick (and some other model 2 stuff), and two in Wicket, and finally, I can add complexity to my pages, without being pulled into a swamp.

So, IMHO you should go with Wicket if 1 and 4 (and 2, as you’ll find the community support really good) weigh heaviest, or with Tapestry or Echo if 2, 3 and 5 weigh the heaviest.

Eelco

]]>