Feb
23
2008
23
2008
G2X Day 1: Graeme’s Keynote
An article by Glen
Ok. Gotta blog up some of this stuff before it gets stale. Last night Graeme took us through what’s on the planning on the horizon for Grails 1.1.
- JPA support. Lot of people asking about this (really?). So there is likely to be a JPA plugin down the track but since JPA doesn’t support Criteria, it’s gonna be a fair bit of work for the team to implement.
- JSP Taglib in GSPs. You’ll be able to use your Java taglibs in a GSP (not just a JSP). Good stuff for reusing old custom tags.
- Portlet support. The biggest ticket JIRA item is portlet support, and the Grails team are investigating what’s involved.
- JCR support. Graeme has been tinkering with a plugin for this. Means you’ll be able to version domain classes, and do diffs and rollbacks and other goodness
- DB Migrations. You’ll be able to move your schema forward and backward.
- Security API. Provide well-known hooks into the framework for Acegi and JSecurity plugins to plug in to.
Graeme then demoed a version of grails.org running on Grails! He’d whipped up a confluence style wiki that supports basic Textile markup, versioning and rollback.
He found XmlSlurper died (OutOfMemory) on the 75Mb XML Confluence file. He had to whip up a SaxParser impl (in Groovy, of course!). The import to his Macbook (read and parse XML and import to a domain model in MySql) took around 90 seconds. Cool!
Took him a day and a half to pull together! Look for it soon!
Did you enjoy this article? Share it!
About the Author: Glen Smith
4 Comments + Add Comment
Leave a comment
Glen Smith
Archives
- April 2012
- March 2012
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- January 2011
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003
portlet support would be awesome
I think the JPA suport (legacy databases must easily be adopted when writing a new app from scratch with Grails) and the DB migrations are the most important ones at least for me.
I dont think we need a Security API. Acegi is easy to figure out even without the plugin.
Hi Glen!
Thanks for listing the Grails new feature list. I have given a presentation on Groovy and Databases, and half of it was about different approaches to use when considering DB versioning/refactorings. I’m very interested in how Graeme is seeing this plugin.
cheers,
./alex
–
.w( the_mindstorm )p.
Hi Glen, thanks for the update. A couple of things I’m looking forward to seeing;
1. Your presentation available for the unfortunate that weren’t able to attend the conference.
2. A reverse engineering tool that will read the schema from an existing database and create the model in grails. It would be wonderful just to use the current functionality. Hopefully this will also flush out missing pieces to properly describe current dbs.
Keep up the Grails work, Thanks