No, I still believe it would be quite trivial to write a Wicket builder that would make creating Wicket component interfaces much simpler in Groovy. Something like Groovy's current SwingBuilder system: http://www.oreillynet.com/onjava/blog/2004/10/gdgroovy_basic_swingbuilder.html
It is just about investing the time to build this. As to what you get by using Grails and Wicket together, well you essentially get an ORM system built right in that follows a convention-over-configuration approach and supports dynamic finders and is built on Hibernate (http://grails.org/GORM) You also get support for Grails' entire plug-in eco-system including things like Quartz, Compass, XFire, Spring Remoting, Acegi etc. See http://grails.org/Plugins My only concern with the current implementation is that it requires a server restart when you make any changes to the Wicket Application class or components. This goes against the "Grails Way" which promotes agile, iterative development and really ideally we would need to find a way, at least in development mode, to refresh the Wicket Application instance when the Groovy classes change so get automatic reloading PS One correction is that Grails is not part of the RoR family or in anyway related to Rails or a port of Rails. It is built from the ground up on solid Java technologies like Spring & Hibernate Cheers --- Graeme Rocher Grails Project Lead jklappenbach wrote: > > http://graemerocher.blogspot.com/2007/05/grails-wicket-wonders-of-grails-plug-in.html > (SFW) > > Graeme pinged me as soon as I got online this morning to tell me about his > work on integrating Wicket and Groovy, a Rails implementation based on the > Java scripting language, Groovy. > > As you'll read, the integration took him *20 minutes*, and the result was > the following: > > 1. Wicket classes can be utilized as-is from wicket jars inside a > Groovy environment, meaning that there's no concern of keeping a > Groovy-based mirror of Wicket synchronized. > 2. Wicket classes can take advantage of GORM, with dynamic methods > (This is very, very, cool) > 3. Developers can take advantage of closures, and all other nice > features of Groovy > > Graeme warned me that he hadn't tested much more than a "Hello World" > example. But in getting even those two simple words out, a lot had to be > going on under the hood. I'd be surprised if there were issues lurking > beyond. > > If you haven't heard of Grails, or would like to know more, I have a short > post here at: > > http://tapestryofthoughts.blogspot.com/2007/05/grails-rails-gone-groovy.html > > For more in-depth, there's the Grails site at: > > http://grails.codehaus.org/ > > -jjk > > ------------------------------------------------------------------------- > 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 > > -- View this message in context: http://www.nabble.com/Gricket%3A-The-Love-Child-of-Grails-and-Wicket-tf3772804.html#a10674823 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- 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
