The Validator.validateValue() seems to be ignoring validation annotations on an interface. Example:

Not sure whether it’s by design (interface is technically not a bean), or accidental.

Use-case: I’m using ktorm for persistency; ktorm entities are interfaces with backing proxy (strange but that’s how ktorm rolls). I’m trying to write an UI in Vaadin performing validation of ktorm entities, but the validators do not fire.

Why I think this might be a bug: feels like there’s an inconsistency here, in a way that MyBean2 seems to be inheriting validation annotations from the interface. In my opinion, cases 2+3+4 should return consistent outputs: either all should return no violations, or they should return one violation.

Of course, from my point of view, it would be best if one violation is returned

If it’s decided to fix this, it would be great to backport to javax.validation as well please.