Comments on: Out of the Box Grails + JEE Integration http://jasonrudolph.com/blog/2006/12/18/out-of-the-box-grails-jee-integration/ puts Blog.new("nonsense") Thu, 04 Dec 2008 18:27:02 +0000 http://wordpress.org/?v=2.6.3 By: Jason Rudolph http://jasonrudolph.com/blog/2006/12/18/out-of-the-box-grails-jee-integration/#comment-2815 Jason Rudolph Sat, 24 Feb 2007 16:16:00 +0000 http://jasonrudolph.com/blog/2006/12/18/out-of-the-box-grails-jee-integration/#comment-2815 <p>Hi Achim, Yes indeed. That's a legitimate gripe. Luckily Grails should support environment-specific resources.xml files likely before the 1.0 release. </p> <p>It looks like <a href="http://www.nabble.com/Re%3A-Deployment-to-different-environments-and-JNDI-data-sources-p9099960.html" rel="nofollow">Graeme clarified this on the mailing list</a> as well. </p> <p>Cheers, Jason</p> Hi Achim, Yes indeed. That’s a legitimate gripe. Luckily Grails should support environment-specific resources.xml files likely before the 1.0 release.

It looks like Graeme clarified this on the mailing list as well.

Cheers, Jason

]]> By: Achim http://jasonrudolph.com/blog/2006/12/18/out-of-the-box-grails-jee-integration/#comment-2764 Achim Thu, 22 Feb 2007 12:30:17 +0000 http://jasonrudolph.com/blog/2006/12/18/out-of-the-box-grails-jee-integration/#comment-2764 <p>Well, that is certainly a nice feature. However once you put a dataSource bean in your resources.xml, the Grails data sources in grails-app/conf will no longer be used even if you do not deploy to a J2EE server. This means you can no longer use the jetty container that ships with Grails and all developers will have to have a J2EE container installed for deploying the application.</p> <p>Or alternatively, you have to replace the resources.xml file manually when you create a production deployment. It would have been nice to be able to, e.g., say "for environment dev, use DevelopmentDataSource, for test, use the datasource jdbc/GrailsTest from your app server, and for prod, use jdbc/GrailsProd" - or other constellations depending on your environment.</p> <p>Achim</p> Well, that is certainly a nice feature. However once you put a dataSource bean in your resources.xml, the Grails data sources in grails-app/conf will no longer be used even if you do not deploy to a J2EE server. This means you can no longer use the jetty container that ships with Grails and all developers will have to have a J2EE container installed for deploying the application.

Or alternatively, you have to replace the resources.xml file manually when you create a production deployment. It would have been nice to be able to, e.g., say “for environment dev, use DevelopmentDataSource, for test, use the datasource jdbc/GrailsTest from your app server, and for prod, use jdbc/GrailsProd” - or other constellations depending on your environment.

Achim

]]>