[bv-dev] Value extractors and the TCK

Matt Benson mbenson at apache.org
Fri Mar 2 18:27:07 EST 2018

Hmm, I think I am seeing the difference. The value extractor node would
show up for constraints validated directly against the container element,
then I'm extrapolating that legacy containers would cascade validation as
prior to BV 2 and thus elide this node. Can anyone confirm this
interpretation, or better yet show it to me in the spec?


On Mar 2, 2018 5:17 PM, "Matt Benson" <mbenson at apache.org> wrote:

> Hi all,
> We are progressing on the Apache BVal implementation of BV 2.0 and I have
> a question. Taking as a concrete example, CascadingOnContainerElementsTe
> st#cascading_on_container_element_of_constructor_parameter_is_applied():
> BarService#<init>(List) annotates the Bar element type of the List
> parameter, yet the unit test appears to treat this identically to a BV < 2
> @Valid List, from the perspective of the expected path nodes. I can perhaps
> accept that, but if that is what is expected by the spec (I don't find this
> explicitly stated, but that may be my problem), when would the built in
> list element value extractor be expected to kick in and supply the <list
> element> node as stated in the spec, and/or when would said node be
> expected to show up in a path?
> Thanks,
> Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20180302/c1ae89aa/attachment-0001.html 

More information about the beanvalidation-dev mailing list