I don't think we ever came back to you on that one.
No we have no plan on backporting this feature nor other features in
general.
Steve wrote a nice piece of why we take a relatively hard stance on
older releases
https://github.com/hibernate/hibernate-orm/wiki/Huge-Project,-Small-Team
It's a bit
I am not sure if that is still relevant but in the past, either HSEARCH
or HV were keeping the ReflectionManager around to use it at runtime
(either because metadata was loaded lazily or because of a reboot of the
factories due to a configuration change.
So we need to check that losing access to R
On 30 August 2016 at 10:09, Emmanuel Bernard wrote:
> I am not sure if that is still relevant but in the past, either HSEARCH
> or HV were keeping the ReflectionManager around to use it at runtime
> (either because metadata was loaded lazily or because of a reboot of the
> factories due to a confi
> So we need to check that losing access to ReflectionManager after SF is
created won't be problematic for these projects.
In HV there is no reference to ReflectionManager whatsoever (same for OGM).
2016-08-30 11:09 GMT+02:00 Emmanuel Bernard :
> I am not sure if that is still relevant but in
On Tue, Aug 30, 2016 at 6:27 AM Sanne Grinovero wrote:
> On 30 August 2016 at 10:09, Emmanuel Bernard
> wrote:
> > I am not sure if that is still relevant but in the past, either HSEARCH
> > or HV were keeping the ReflectionManager around to use it at runtime
> > (either because metadata was loa
Any thoughts on the JpaIntegrator parts of the discussion? Specifically
there are 2 main considerations:
1. To change the Integrator#integrate contract - ideally, in retrospect,
#integrate probably should have taken a "parameter object" to help insulate
from these types of changes. But
Hi Steve,
I can start integrating this code into your wip/6.0 branch. Are there any
fundamental changes you would like to see before I integrate, or should I
integrate as is?
Thanks,
Gail
On Fri, Apr 1, 2016 at 12:14 PM, Steve Ebersole wrote:
> I do like the proposal. Awesome job on the gist.
I do wonder if OperationContextType should not be integrated into
EventType. I hate repeatng this set of enumerations. Something like
https://gist.github.com/sebersole/2a4af882d0a61696dce39d242023add0
Not specific to this PoC but one thing I would also like to see is the
ability to know the Even
