orm.xml - cleanup respecting column names ----------------------------------------- Key: ANN-687 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-687 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Environment: mysql 5, MS SQL 2000, Win2000, hibernate 3.2.4 Reporter: darren hartford couple of issues with orm.xml mapping file that is not fully implemented and needs cleanup. many-to-many table mapping not respecting column names. http://forum.hibernate.org/viewtopic.php?t=982330 id-class not respecting column names (end of an old issue, repeated with different scenario). http://opensource.atlassian.com/projects/hibernate/browse/ANN-361 <id-class class="MyTestId"/> <attributes> <id name="compoundOne"> <column name="COMPOUND_ONE"/> </id> <id name="compoundTwo"> <column name="COMPOUND_TWO"/> </id> ... WARNING: Preparing the statement failed: Invalid column name 'compoundOne'. WARNING: Preparing the statement failed: Invalid column name 'compoundTwo'. ========== Use case and urgency of issue related to external technology integration. -DTO should not require hibernate-annotations to be used in client-code, but is required when using annotations. orm.xml approach removes this limitation. -GWT 1.4 does not work with java 1.5/annotated DTO. Although everyone keeps pushing it off saying 'GWT 1.5 is on the way', it is not and solutions that should have been working to work around that limitation need to be working correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira