jdaugherty opened a new issue, #63: URL: https://github.com/apache/grails-intellij-plugin/issues/63
Grails allows users to use traditional Hibernate mappings, or annotations mappings, by altering the dataSource.configClass property. When this is done, mapped Hibernate classes are automatically converted to Grails domain classes and behave exactly the same way as traditional domain classes with the following oddities: 1) They are usually in src/java instead of grails-app/domain 2) Constraints are defined in [className]Constraints.groovy – e.g. org.foo.Bar's constraints are in org/foo/BarConstraints.groovy More details can be found at the following two URLs: [http://grails.org/doc/1.2/guide/15.%20Grails%20and%20Hibernate.html](http://grails.org/doc/1.2/guide/15.%20Grails%20and%20Hibernate.html) [http://www.grails.org/Validation](http://www.grails.org/Validation) Note: We keep our domain classes in a Grails plugin referenced by our main applications; in a perfect world, they should be resolved in the dependent Grails applications as domain objects, also. --- *Imported from [IDEA-51851](https://youtrack.jetbrains.com/issue/IDEA-51851) · Type: Feature · Votes: 5* *Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
