Annotation processor should support constraint validators added programmatically

Description

I have a project that is using programmatic constraint validation to apply a constraint from a library to a type within my application.

An example that is equivalent to my situation:

My understanding is that the annotation processor cannot actually run the programmatic constraint validation code. However, perhaps this could be solved another way. Maybe provide a processor option to define additional type=>annotation mappings. Possibly there's another way to register the mapping through something in the compiled code itself. Maybe allow supplying a configuration file to specify this sort of override.


I see this as basically a version of but for programmatic constraint definition, rather than the XML constraint mapping file. It's also a more general version of HV-418, rather than a very specific common use case.

Environment

None

Assignee

Unassigned

Reporter

M. Justin