Hi,

I've written a custom constraint and validator to check that a date field is greater than or equal to another date field in the same class. I've implemented the inner class List on this constraint so that more than one date field can be validated.

The problem I'm having is that only one validation error will be shown at a time, even if both constraints should fail. After debugging, it appears as though only one constraint is validated, and if that fails, the other is ignored.

Is this a restriction of the bean validation spec or is there some way to ensure that both constraints are validated at class level? Multiple constraints at field level work as expected.

Hi,

Could you post the code for your custom constraint, together with an example entity you are using it on?

--Hardy

Hi,

As said Hardy, an example of code will be useful :)

I've made an example with a custom constraint and it works as expected. I've tried to reproduce your behavior and I've seen that, if the error message defined in the custom constraint is a "constant" (look at the following example), only one error is returned. But if the error message is parametrized like "{value} is invalid" all errors are returned.



--
Kevin

Just for completing my previous post :)

If only one error message is displayed when the error message is a "constant", it's because these constraint violations are considered equal (same message, propertyPath, validated value, ...).

--
Kevin

Hi,

Thanks very much for the replies - my problem was having a constant value for the message.

Thanks!!