+1
And my caching work is ready (in my opinion). Could that be included?
The important thing it does, is to replace those key contracts with an
interface, preparing ground for various optimisations. I didn't
implement the actual optimisations, but that won't break any SPI..
On 1 June 2015 at 18:06, Steve Ebersole <steve(a)hibernate.org> wrote:
HHH-9818[1] and HHH-9837[2] contains all the details. Essentially
there is
a very bad flaw in how hibernate-osgi is currently propagating class
loading to mapping binding. Fixing this was missed in the 5.0 work. It
only affects AnnotationBinder, but it happens to affect every single
application that uses annotations because it happens to be the code that
loads the entity Class and proxy interface Class references.
Personally I feel that this warrants a CR2. What do y'all think?
[1]
https://hibernate.atlassian.net/browse/HHH-9818
[2]
https://hibernate.atlassian.net/browse/HHH-9837
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev