ConstraintDefinitionContributor would not have to go away completely, it'd just become an implementation detail.
Right, that's a possibiltiy
The service loader based implementation as well as what's configured via ConstraintMapping would use it internally.
Ok, that makes sense. In this case we are talking about removing the user facing exposure of ConstraintDefinitionContributor in HibernateValidatorConfiguration. Fair enough.
That'd not be needed if it's doable via ConstraintMapping. Note we have ConstraintMappingContributor to plug in additional mappings.
Right, I forgot about ConstraintMappingContributor. I am fine with this approach. Just need to make sure to cleanup the docs and online docs. |