Out the box Grails provides two ways to display messages to the user.
Here are some ‘real life’ database connection examples for the MySQL (~5.0) and MSSQL (Microsoft SQL Server 2005 JDBC Driver which can be used on 2003).
Logging is a better way to debug and provide messages than slapping println statements around. Here is an example of a grails config for log4j. This will also place the log file in with the Tomcat logs when you deploy.
It is well advised to place application and business logic in service classes when doing any programming and indeed the Grails user guide does advise this. However the default templates do not do this so there is no example or dare I say it best practice example that I could find on the web. So exactly how do we get the controller and service to interact and retain all the functionality provided by the templates and generate-all?
If you would like to do anything more than idEq when using criteria with id’s you may run into some trouble.