Hey Guillaume,

I think that this is a matter of taste, but I don't think that an extra wrapper element is necessary. So I'm fine with the current way of doing it. Not sure if using a wrapper element is an "usual convention". But I'm not strong on this one.

Other thoughts?

Christian

2017-05-18 11:35 GMT+02:00 Guillaume Smet <guillaume.smet@gmail.com>:
Hi,

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 following:
<validation-config>

    <message-interpolator>org.hibernate.beanvalidation.tck.tests.integration.cdi.managedobjects.MessageInterpolatorUsingDependencyInjection</message-interpolator>

    <value-extractor>package.MapKeyValueExtractorUsingDependencyInjection</value-extractor>
    <value-extractor>package.MapValueValueExtractorUsingDependencyInjection</value-extractor>

</validation-config>

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?

--
Guillaume

_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev



--
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal