See https://github.com/beanvalidation/beanvalidation-spec/compare/2a9d0ce21856386a8bf9a1d9e963ebffc049604a...spec-full#diff-09dfff2a72d8d7a7663084247ccc6b32R13072

Reasons for raising ValueExtractorDefinitionException include:
[...]

• A non-wildcard type parameter has been marked with `@ExtractedValue`

I wonder if mandating the exception in that case will make the experimentation by specific providers impossible. I'd rather have the window open with a "can" in the spec on that subject.

Thoughts?