|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
Going to move this to 1.1.0.Final.
I initially thought I could quickly retrofit the tests to expect a ConstraintDeclarationException upon validation. Indeed we get this exception, but already upon building up the metadata for the bean. This causes several other tests using the same class to fail, also if they don't use the illegally annotated method. Other exceptions related to illegal method constraints are built up during metadata creation but are thrown only upon metadata retrieval for a given method. The exception here is thrown eagerly in ConstraintDescriptorImpl#determineConstraintType().
Thinking about it, maybe we should also have this clarified in the spec, i.e. Must other methods of a bean be validatable if one method is wrong?