Inspired by the title of Douglas Crockford book, "Javascript, the good parts" and having to write an introduction on grails as a course for some colleagues, I thought it would be good to just blog about grails and the first steps some one should take.
Well, when I'm prototyping and generally developing with grails I do not want to use generate-all and just edit the generated controllers and gsps. I try to find my way overwriting maybe some actions but not edit them and some or more changes to the scaffold templates.
After having static resources get served right with Jetty within an OSGI enviroment you may want to be able to use groovy and more specific some groovlets
More or less the problem is the one that has been described at a previous post. Once again all we have to do is give some more "space" to the groovy.servlet.GroovyServlet to look for our groovlets
The case is an sql table with about 30 columns that I have to query and export some (or all) data. In this case plain csv format should be just fine!