Hi I was myself looking for a web framework and I've looked at both Tapestry and Wicket, so I'll quickly give my feeling : - Tapestry development team switch from major version to major version without providing a clear migration path for the user. As such, on Tapestry forums, you got questions of "old" Tapestry 3, then of current Tap 4 and even some on Tap 5, each version being quite different. That was a major hurdle for me, because I want my web framework to last more than the time of a version and to have a clear migration path. - In tapestry, components inheritance isn't possible. In wicket, it's just awesome, especially considering an enterprise developed website. Indeed, you define "basePage", "baseForm" and so on, so the basic developer is guided and helped a lot. For example, I use an "ajaxBasedForm" for my forms, and thus the ajax stuff is written only once and I don't have to deal with it anymore, even if all my forms are ajax enabled. Great isn't it ? On an enterprise, I really see the benefits : the "normal" forms' developers will just have to deal with the forms' elements, and not with the form validation and submitting logic. - last but not least, the developers behind Wicket are just really user friendly. They listen to developers inputs as well as respond really fast and efficiently to questions. It's just amazing.
For GWT, I can't tell. I mainly skipped it because it was way too much "full ajax" and, at the time, not free (quite annoying at the time for the unfixed bugs). Best regards ZedroS ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
