We just discovered that we're facing this issue using Hibernate 3.6.10.
Unfortunately we're stuck to Hibernate 3.6 as we're still forced to use Java 5.
Is there any possibility to get this fixed in 3.6 stream? Maybe a "private" patch?
Thanks!