HHH-11147 changed a EntityMetamodel constructor argument from
a SessionFactoryImplementor to a PersisterCreationContext.
Would a custom EntityPersister break due to calling the constructor with
the new argument type?
>From what I can tell, the argument was changed to PersisterCreationContext
go g
HHH-11147 changed Property#isLazy as shown in [1].
The part that concerns me is:
+ // For a many-to-one, this is always false. Whether the
+ // association is EAGER, PROXY or NO-PROXY we want the fk
+ // selected
+ return false;
I don't think this is correct when enhancement-as-proxy is disable
HHH-11147 added PersistenceContext#addEnhancedProxy without a default
implementation.
Would an application implement PersistenceContext? If so, this would be a
breaking change.
Please let me know...
Thanks,
Gail
___
hibernate-dev mailing list
hibernate
