I attached a workaround for the problem, in the file

. It requires spring, hibernate 3.6 and annotation configuration but still I think it's something worth sharing. Use the instead of the standard in the bean definition, and leave all the configuration as is, this is just an extension of the original spring class.

After the mapping parsing is complete, this class will reorder the properties pushing the

annontated elements (at the moment the xml configuration is not supported) to the end of the property list, so when queries are generated oracle will accept them. Obviously this will not solve all cases, but I think it will help in many cases without renaming properties or relying on luck. I don't know if this might be applied also for hibernate 4, I haven't tried.

If you negate the comparator in the class (swapping 1 and -1), the problem will be easier to reproduce.