How to avoid Hibernate Validator ConstraintDeclarationException?

Question

I have my WebService based on Spring 4, and I am using Hibernate Validator (beyond MethodValidationPostProcessor). My problem is that I have my ClientService interface, and its implementation. So I put Bean Validation constraints on the implementation and it forces me to put that constraints on the interface (throwing ConstraintDeclarationException) (or in both of them).

I want to know two things about this:

Why does it work like this? Why does it force me to put all constraints on the interface? What is the reason?
Is there any way to put the constraints only in the implementation?

Thanks in advance! Regards

Hardy · Accepted Answer · 2015-06-19 09:47:15Z

5

To answer your first question. The behavior is specified in the Bean Validation specification section 4.5.5. Method constraints in inheritance hierarchies. Basically the rule is that a method's preconditions (as represented by parameter constraints) must not be strengthened in sub types. This is the so called Liskov substitution principle.

To answer your second question, there is no way at the moment to place constraints on the implementation class. There is HV-872 which suggests to implement a configurable relaxation of these rules as a Hibernate Validator specific feature, but it is not implemented yet.

answered Jun 19, 2015 at 9:47

Hardy

19.2k3 gold badges52 silver badges65 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

How to avoid Hibernate Validator ConstraintDeclarationException?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related