Sorry, I think I used the wrong terminology in the description. Consider the 'children' field in an entity, which has the @NotNull annotation.
@OneToMany(mappedBy = "parent", cascade = CascadeType.ALL, orphanRemoval = true)
@NotNull
private List<Child> children;
In the 4.2 branch a ConstraintValidationException is thrown if an Entity, containing the above field, is merged/persisted with a null value. However, in 5 this is not the case.
I posted this here because my experience was always via a Hibernate session, but maybe the Validator project is the correct place for this issue.
|