Hi currently we have a mapped super class of the following:


These validations of length 32 reflect that required in the database.

We have however a extended class of this:



Where we want the validation length to be of length 15 rather than of 32.

This validation for PersonFraudCheck appears to be unpredictable, sometimes it validates to the requirement of 32 sometimes it requires 15.

What steps must be taken to ensure all validation for PersonFraudCheck is to 15?

Thanks so much for your time and appreciate any guidance.

Hi,

first of all, constraints don't override each other. @Length(max = 15) is not overriding the @Length(max = 32) constraints. It is just adding an additional constraint. If you validate an instance of PersonFraudCheck you are validating once against max=32 and once against max=15. Order is also not guaranteed. as per spec the constraint can be evaluated in any order. Only via a group sequence definition can one enforce an order.

One possible solution for your problem could be to work w/ groups and have the two different @Size constraints in different groups. Depending on your concrete circumstances this might or might not work.

--Hardy

Hi Hardy!

Thanks that was extremely informative, helpful and straight to the point!

Sorry I am not familiar with the group validation that you are talking about could you kindly point me to some documentation in which you are referring to?

On another stream of thought...

If I have NO validation on PersonBase but rather have it on the extended classes would this be a suitable fix to the problem?

I.e.
PersonBase.java


ShortNamePerson.java extends PersonBase



LongNamePerson.java extends PersonBase

Check the Hibernate Validator documentation - http://docs.jboss.org/hibernate/stable/ ... tml_single or if you prefer you
can have a look at the Bean Validation specification itself - http://www.jcp.org/en/jsr/detail?id=303


Sure. This will work. If it fits your use case.

--Hardy

Thanks Hardy! Extremely helpful and fast!