Annotation processor should consider validators registered by XML constraint mapping

Description

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'").

Environment

None

Activity

Show:
Hardy Ferentschik
January 14, 2011, 9:38 PM

Do you have any plans for implementing this?

Gunnar Morling
January 18, 2011, 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 18, 2011, 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 19, 2011, 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

Assignee

Unassigned

Reporter

Gunnar Morling

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

Yes, likely

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Priority

Major
Configure