Mastering Grails, Grails and legacy databases

Can convention over configuration survive unconventional databases schemas?

From the developerWorks archives

Scott Davis

Date archived: April 19, 2017 | First published: July 15, 2008

In this Mastering Grails installment, Scott Davis explores the various ways that Grails can use database tables that don't conform to the Grails naming standard. If you have Java™ classes that already map to your legacy databases, Grails allows you to use them unchanged. You'll see examples that use Hibernate HBM files and Enterprise JavaBeans 3 annotations with legacy Java classes.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Java development, Web development, Open source
ArticleID=320496
ArticleTitle=Mastering Grails: Grails and legacy databases
publish-date=07152008