Add generate-hbm-xml script to expose hibernate config

This would also be useful when another non-grails app needs to leverage a data model that was produced via GORM. Something we will run into in the near future. A similar option would be to dump the hbm files at runtime...maybe just in development.

The impact of this could be enormous. It could introduce a slew of Java/Hibernate people to the GORM.

e.g. My current team is using Java and Hibernate3 with XML mappings. We find it expensive to recall how to map complicated structures, even with our own pre-existing work. I would love to fire up Grails/GORM where I could easily express relationships and then tweak the output. Essentially, the GORM would be a DSL to prototype mappings.

This would also make it easier to use existing Hibernate tools for eclipse on a grails project. It needs to look at a configuration file in order to help you test out your criteria and queries. These tools really simplify complicated queries which findAllBy can't do... Thanks.

this feature would have saved me countless hours of troubleshooting.

in the end i gave up on hooking up GORM to a "legacy" (not really) schema and had to implement in hbm.xml. (i was trying to get a one-to-one with a shared primary key)

switching to java/hbm has presented it's own problems as there is no way to access "transient fields" (getters/setters without a hbm mapping-- GrailsDomainClass only contains what is in the mapping, and seems to ignore the rest of the java class – i'm looking for this defect in jira now).

There is no scope / time to resolve these remaining lower priority issues for 1.2 so moving to 1.3

for 1.2 final only issues considered blocking will now be fixed

Implemented by http://github.com/grails/grails-core/commit/673239d909514dc4e5bd578108f0e69cebcf07cf and docs are here: http://github.com/grails/grails-doc/commit/283b65dfc9ad69341e45070213b0330ea04f56c0

Unless I totally misread the 18/May/10 "solution", I would like to re-open this ticket and raise its priority. What was requested is a truely important feature. What was provided is more or less useless.

Moreover, I absolutely fail to see how copying a template for the hibernate.cfg.xml file is anywhere close to a material equivalent to code generating the hbm files for each of the domain classes. Copying a template is not any solution at all. Just take a look at the original request and you will clearly understand that the request was for the hbm files. and over and over again, the comments were supportive of having the hbm files.

Hmmm. I guess I joined hbm-xml and hibernate from the subject line and read it as wanting a script to generate a hibernate.cfg.xml file.

The App Info plugin supports this as one of its features, although it's not available as a script - you need to manually make the request and copy/paste the generated hbm.xml to a file. See http://grails.org/plugin/app-info

I'll reopen this and consider it for 1.4 or 2.0.