Community
Participate
Working Groups
This is similar to the problem with orm.xml virtual attributes not being validated. But this is in a purely Java case. You only get validation on attribute overrides if you specify them. If the EMPLOYEE.ZIP column does not exist, there is no validation error appearing on Employee.address. @Entity public class Employee private Address address; } @Embeddable public class Address { private int zip; }
This problem also applies to mapped superclass: @MappedSuperclass public abstract class Foo { private String state; private String street1; } @Entity @AttributeOverride(name = "state", column = @Column(name = "PROVINCE")) public class Foo1 extends Foo { } If changing attribute "state" to something else in Foo, you would get a validation error on Foo1; however, you would NOT get a validation error on Foo1 against attribute "street1" even though no column named "STREET1" exists in the database.
This appears to be a regression and as such should be fixed in 3.0.
This is not only a bug for Java, but also for ORM.
Tried to get this fixed for RC2 but didn't have enough time. Targeting to RC3 and will evaluate whether or not it is appropriate for RC3 when the fix is complete.
Given the normal severity of this bug, and the fact that the fix is likely to be a very large change, I am deferring this to 3.0.1.
Moving JPA specific bugs to new JPA component in bugzilla.
This is fixed in head. It seems unlikely that fixing this will be feasible in 3.0.x.
Fixed in Dali 3.1. Will only look at backport upon request.
