JPA - Override bean validation in joined-strategy inheritance

Question

I have three JPA entities: A, B and C. B and C inherit A with joined strategy. Is it possible to override a Bean Validation constraint in the subclasses? For example, I would like B to have a @NotNull constraint in one field and C to have a @Null constraint in the same field.

I was thinking to do it by using Bean Validation groups, however I don't know how to define that B must be validated with one group and C with another group.

Code to illustrate the problem:

@Entity
@Inheritance(strategy=InheritanceType.JOINED)
...
public abstract class A {
    ...
    @Column(name="FIELD")
    private Integer field;
    ...
}

@Entity
public class B extends A {
    ...
    //@NotNull in field
    ...
}

@Entity
public class C extends A {
    ...
    //@Null in field
    ...
}

score 0 · Answer 1 · edited May 23 '17 at 12:11

0

I think I have come to a solution reading this other question about conditional bean validation: Conditional Bean Validation.

It is still not tested, but I think it could work.

Code of the solution:

@Entity
@Inheritance(strategy=InheritanceType.JOINED)
...
public abstract class A {
    ...
    @Column(name="FIELD")
    private Integer field;
    ...
}

@Entity
public class B extends A {
    ...
    @Transient
    @AssertTrue
    private boolean isValidClassA() {
        return (getField() != null); //Validates NotNull
    }
    ...
}

@Entity
public class C extends A {
    ...
    @Transient
    @AssertTrue
    private boolean isValidClassA() {
        return (getField() == null); //Validates Null
    }
    ...
}

edited May 23 '17 at 12:11

Community

1
1

answered Oct 08 '14 at 21:01

Aliuk

1,249
2
17
32

It will not be easier just to move the attribute field to B and C? – uaiHebert Oct 08 '14 at 23:30
No, because I need it when querying A entities. – Aliuk Oct 09 '14 at 17:10

score 0 · Answer 2 · answered Oct 10 '14 at 06:57

If you need this validation during persist or merge operation, why dont you define a pre prersist/update callbacks?

public class Base {

  protected String myData;
}

public class ConcreteA {

  @PrePersist
  @PreUpdate
  private void checkDataNotNull() {
    assert(mydata).isNotNull();
  }
}

public class ConcreteB {

  //myData may be null, so dont do any check
}

You are guaranteed then that the data will not be save to the database for ConcreteA if it null, and an error will be raised. You no longer need to manually check the field if it is not null manually.

JPA - Override bean validation in joined-strategy inheritance

2 Answers2