Annotation processor should consider validators registered by XML constraint mapping
Description
Environment
None
Activity
Show:
Former user January 10, 2022 at 7:14 PM
Has this been implemented since 4.3 or one can start working on it?
Gunnar Morling January 19, 2011 at 1:41 AM
Ok, let's start with HV-418. Another story is checking method level constraints with the AP, I'll create another JIRA issue for this, but this definitely can be done in 4.3
Hardy Ferentschik January 18, 2011 at 2:14 PM
It would be nice if we could get it into 4.2, but not essential imo. seems more important and hopefully not so hard to fix.
I move it into the 4.2.0 final release. If we don't have time for it we move it out later.
Gunnar Morling January 18, 2011 at 12:21 AM
No, not really at this point. Do you think, we should do it for 4.2? Another issue in this context is HV-418, at least this one should ship with 4.2
Hardy Ferentschik January 14, 2011 at 9:38 PM
Do you have any plans for implementing this?
Details
Details
Assignee
Reporter
Gunnar Morling
Gunnar MorlingParticipants
Former user
Gunnar Morling
Hardy Ferentschik
Components
Priority
Created April 13, 2010 at 9:34 PM
Updated May 31, 2024 at 7:19 AM
Background:
The Bean Validation API allows the set of validators for a given constraint to be specified/overridden using XML constraint mapping files (http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/#d0e1957).
Right now the annotation processor does not process any XML configuration files at all (neither validation.xml nor mapping files).
To do:
While it seems ok for now that the AP does not check constraint declarations given in XML (after all it's an annotation processor), I think it should evaluate the constraint definitions and the validators configured in XML. Otherwise the AP would raise false errors (as validators added in XML are ignored) or would give false positives (as validators given in @Constraint#validatedBy could be removed by "include-existing-validator='false'").