> Give me the spec paragraph that says that field has priority over getter.
Where is the spec that says getter has priority over field ? :) In a separate discussion with the Dali (eclipse jpa tooling) team it seems like for orm.xml it is not at all specified and thus left up to interpretation of the vendor and it seems the ref implementation (eclipselink) takes the opposite approach to this than Hibernate and we get stuck in the middle. The "fix" seems to be that the validation in eclipse will be customizable to which default it should validate against. /max > > On 1 juil. 2010, at 11:06, Andersen Max <max.ander...@redhat.com> wrote: > >>> The spec dedicates a whole paragraph about the default access type using >>> using annotations, but I could >>> not find anything regarding the default access type using orm.xml only. It >>> seems it is up to >>> the implementor to decide on the the default. Why would you consider >>> 'property' access to be the wrong default? >> >> The problem is that eclipse tooling tries and validate if the orm.xml >> actually maps to something >> "legal". >> >> Currently the default for orm.xml seem to be field access first thus it >> fails validation if there is no >> matching field. >> >> The Eclipse tooling claims to be following the JPA spec thus why we are >> asking what Hibernate >> is basing its choice on. >> >> /max >> >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
