> What is in Grails that would make Wicket "better" for web-app development? > Is it just the integration of Groovy or is there something more for a Wicket > user?
My uneducated take on this (correct me if I'm wrong, I'm just thinking out loud): something like Grails should work very well for when you have to develop/ deliver quickly. Wicket works very well for when you want to build projects that are maintainable, take advantage of reuse, easily scale to larger teams etc. This plugin for Grails sounds like the best of both worlds to me, at least if it is possible to have a mixed development model. If it is possible to reuse custom components in Grails (or Gricket) and if you can later switch pages (and components?) that were build in Grails to 'normal' Wicket when you want to, that would mean that you can work very rapidly at the start of projects, and achieve a sort time-to-market, and later when it is more important to work on robusteness, or e.g. digest custom components to avoid code duplication etc, switch (parts) to a Wicket model. Or use Cricket for one project and old-skool Wicket for the other and still be able to reuse parts/ knowledge between the projects. Graeme, Julian, great you've been working on this! Cheers, Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
