You can clone with
Cannot retrieve contributors at this time
Bending GORM: 5-minute Techniques for Enterprise Integration============================================================Have you seen someone develop a Rails or Grails application in a matter ofminutes, only to later discover that their domain model and database schemafollowed conventions that are different from your existing systems? Orperhaps you're interested in using Grails, but you don't want to duplicateyour existing Java domain classes in Groovy. In this session, we'll see howGORM (Grails Object Relational Mapping) makes it easy to hook into yourpre-defined schemas or existing entity classes, while still getting all therapid application development (RAD) goodness that Grails has to offer.In an enterprise environment, you're no doubt surrounded by legacy schemasthat pre-date Grails by many years, possibly even a decade or so. You wantto develop web applications quickly with one of the next-gen frameworks, butthere's no chance that management will agree to change all the schemas justso you can code your app using the conventions employed by the next bigthing. However, we'll see that Grails offers a slew of options for quicklyand easily adapting Grails to any database schema. Whether you prefer theGORM DSL, a few annotations, or even trusty ol' Hibernate XML, we can easilywire together our Grails domain models to our existing schema and still getmost of the RAD benefits of Grails, including the super-productive dynamicfinders, highly-configurable validation rules, powerful Hibernate criteriabuilders, and more.