We just published Hibernate Search 6.0.0.Beta2.
This release mainly introduces search analyzers, improves background
failure handling and upgrades to Elasticsearch 7.4 and Hibernate ORM
For more information, see our blog:
I seem to remember this topic came when we were working on the
Basically, EnhancementAsProxyLazinessInterceptor#session does not get
nullified when the PersistenceContext gets cleared.
As a result, such an entity can still get initialized if
the SharedSessionContractImplementor is still open.
I also noticed that narrowed proxies are never added to the
PersistenceContext, but they still have a reference to
the SharedSessionContractImplementor from which the narrowed proxy
originated. These references never get nullified either.
I believe these are both bugs, and I would like to address them.
Please let me know if I'm missing something here.
the activity was very interesting, so I would like to thank Sanne who had
the idea and led the scope of the activity and thanks to Andrea who gave me
some nice ideas to improve the work.
With [this pull request](
https://github.com/hibernate/hibernate-orm/pull/3040) we have now rules to
Other Java reflection APIs
As a follow up (and probably it won’t be the only one) I created the issue:
So far I’ve been involved in Hibernate OGM and Hibernate Search, so I don't
have a very deep knowledge of Hibernate ORM. So I would like to ask you:
what are the next steps?
And… is there something I can do to help?
Meanwhile I’ll be back to work on Hibernate Search. The integration with
Infinispan is still waiting…
Have a great weekend