Yes that looks fishy. The only explanation I can see is if that approach is supposed to
use the byte code enhancement lazy as opposed to proxy but AFAIR we have different
annotations to express that.
On 15 Mar 2014, at 18:48, Steve Ebersole <steve(a)hibernate.org> wrote:
There is a test currently failing with the new metamodel code. The
mapping
that causes the problem has the following annotations:
@Id
@ManyToOne(...)
@JoinColumns(...)
@Basic(fetch=FetchType.LAZY)
Is it really legal to combine @ManyToOne and @Basic? Those seem "at odds".
My guess is that the legacy binding code simply did not validate for this.
Wdyt?
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev