Hi Steve,
We had discussed releasing in 5.4, and possibly 5.3, with the default
for hibernate.bytecode.allow_enhancement_as_proxy=false. I am in favor of
this.
Are you suggesting that the default behavior would effectively be to set
hibernate.bytecode.allow_enhancement_as_proxy=true in 5.5?
Do you think there would be any need to be able to restore the earlier
behavior in 5.5? IOW, would we even need the property in 5.5?
Regards,
Gail
On Mon, May 13, 2019 at 10:11 AM Sanne Grinovero <sanne(a)hibernate.org>
wrote:
Hi Steve,
like Christian, I would probably target ORM 6, but it's up to you.
If you would rather recommend a 5.5 to get these improvements out
earlier, I have no objections and can help with that.
Thanks,
Sanne
On Mon, 13 May 2019 at 16:20, Christian Beikov
<christian.beikov(a)gmail.com> wrote:
>
> +1 for 6
>
> Am 13.05.2019 um 15:25 schrieb Steve Ebersole:
> > Over the last 3 weeks or so, we have put a lot of work into HHH-11147
which
> > essentially allows bytecode enhancement to behave like the more
traditional
> > proxy feature (create a reference based solely on the entity id).
> >
> > We are wrapping up development of that improvement, enhancement,
change,
> > whatever-you-want-to-call-it... One remaining question however is how
to
> > make this change available in terms of releases. It seems to big of a
deal
> > to simply drop in a new bug-fix release.
> >
> > Should we consider a 5.5 release? Push it to 6? Thoughts?
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev