[bv-dev] validation-configuration.xsd and value-extractors
gunnar at hibernate.org
Wed Jun 7 03:28:33 EDT 2017
Guillaume made a good case for *not* wrapping the value extractors in
validation.xml: we also don't do it for other elements in that
descriptor that can be given more than once: "constraint-mapping" and
"property". So we should leave this as is.
2017-05-23 16:59 GMT+02:00 Gunnar Morling <gunnar at hibernate.org>:
> It's a bit more verbose, but the wrapper makes more explicit that
> multiple extractors can be given. So +1 for the wrapper.
> 2017-05-20 12:57 GMT+02:00 Michael Nascimento <misterm at gmail.com>:
>> Consistency is a great argument imho, so +1 for wrapping it.
>> On 18 May 2017 07:04, "Guillaume Smet" <guillaume.smet at gmail.com> wrote:
>>> In the current revision of the spec, the value-extractor element is at the
>>> same level as message-interpolator for instance.
>>> So, when you want to add several value-extractors, you end up having the
>>> I was thinking that we should maybe wrap it into a value-extractors
>>> element. It would be nicer and more consistent with the usual conventions.
>>> What do you all think about it?
>>> beanvalidation-dev mailing list
>>> beanvalidation-dev at lists.jboss.org
>> beanvalidation-dev mailing list
>> beanvalidation-dev at lists.jboss.org
More information about the beanvalidation-dev