Currently, I'm rewriting our GWT-based application and I picked Wicket. GWT is delicious but only on papers. GWT cons: 1. lack of roles separation, building the GUI in the code doesn't work for me. 2. Hibernate integration is a nightmare. 3. Unit testing isn't that agile thing. I like GWT but I wouldn't prefer to work with it daily.
Casper Bang-3 wrote: > > I was just wondering about the Wicket community's opinion of GWT. It seems > to share many of the positive characteristics as Wicket (focus on code, > not > markup) with the major difference/benefit as I see, that is does not > maintain any state on the server. Also, with GWT you seem to get more > readily available components (i.e. http://extjs.com/explorer/). The > bennefit > of Wicket as I can see, is that applications potentially degrade nicer and > the programming model hides the Ajax RPC better. Any thoughts? > > /Casper > > -- View this message in context: http://www.nabble.com/GWT-vs.-Wicket--tp22950178p23020555.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
