[
http://opensource.atlassian.com/projects/hibernate/browse/HV-269?page=com...
]
Gunnar Morling commented on HV-269:
-----------------------------------
I think we should start with specifying explicitly the BV annotations to keep things
simple. Claiming all annotations (*) seems to be considered problematically by the means
of performance according to the API doc.
To allow for people checking custom constraints, we might provide some sort of SPI
mechanism by overriding AbstractProcessorr#getSupportedAnnotationTypes(), which could load
additional supported annotations and accompanying validation logic by using the JDK
service loader for instance.
Any ideas on how to specify mentioned flag? I don't think one can parametrize
processors upon instantiation, therefore reading the property from some sort of resource
seems viable.
Create an annotation processor validating constraint and property
matching
--------------------------------------------------------------------------
Key: HV-269
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-269
Project: Hibernate Validator
Issue Type: New Feature
Components: engine, validators
Affects Versions: 4.0.2.GA
Reporter: Emmanuel Bernard
Assignee: Hardy Ferentschik
Fix For: 4.1.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira