[hibernate-dev] Make JpaCompliance available earlier
andrea at hibernate.org
Mon Feb 12 08:01:21 EST 2018
I think it is fine, may be you can only get just the value of the specific
setting instead of creating the entire JpaCompliance object.
On 11 February 2018 at 17:01, Steve Ebersole <steve at hibernate.org> wrote:
> I am working on HHH-12282. I was thinking that the best solution would be
> to check this setting at the time when Join#setOptional is called. The
> reason being to centralize the place that this check needs to be done. I
> can do it inside the persister as it consumes the Join, but that leads to
> duplicated code.
> But in order to fix in the way I just described, we would have to make
> JpaCompliance available earlier in the boot process (currently it is built
> as part of SessionFactoryOptions/Builder).
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
More information about the hibernate-dev