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
> The avoidance of reflective constructor invocation via byte code
generation should be rather simple using ByteBuddy.
Turns out that the ByteBuddy byte code provider already has an
instantiation optimizer doing exactly that [1]. Unfortunately, though, from
what I can say it's never used due to a
