[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-629?page=co... ] Sam Pullara commented on HBX-629: --------------------------------- I was able to get around this issue by changing the Hibernate Annotation code, commenting out the part where it sorts them. I don't know what effect this will have on native query support as the comment indicates that is why it is being done. Index: src/java/org/hibernate/cfg/AnnotationBinder.java =================================================================== --- src/java/org/hibernate/cfg/AnnotationBinder.java (revision 15355) +++ src/java/org/hibernate/cfg/AnnotationBinder.java (working copy) @@ -983,12 +983,12 @@ log.debug( "Processing " + propertyHolder.getEntityName() + " " + accessType + " annotation" ); List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType ); //order so that property are used int he same order when binding native query - Collections.sort( properties, new Comparator<XProperty>() { +/* Collections.sort( properties, new Comparator<XProperty>() { public int compare(XProperty property1, XProperty property2) { return property1.getName().compareTo( property2.getName() ); } } ); - for ( XProperty p : properties ) { +*/ for ( XProperty p : properties ) { if ( !p.isTypeResolved() && !discoverTypeWithoutReflection( p ) && !mustBeSkipped( p, mappings ) ) { throw new AnnotationException( "Property " + StringHelper.qualify( propertyHolder.getEntityName(), p.getName() ) + -- 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