Ah that's an angle I have not thought about.

We could have constraints annotated with both @CrossParameterConstraint and @Constraint. The nature of the constraint would be solved by a parameter value.
Note that the signature is different between the validator for a @Constraint (any of the targeted types) and a @CrossParameterConstraint (Object[]).

Such feature would be useful for generic constraints like @ScriptAssert and a generic @EqualsPasswords

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira