Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

This issue can't be edited

Because it belongs to an archived project. Jira admins can restore projects from the archive.

Fix wrong test around value extractors for inheritance hierarchies

Description

CascadingValueExtactorResolutionAlgorithmTest#parallelValueExtractorDefinitionsCausesException() expects an exception, but a correct implementation of the spec will not raise an exception in this case actually.

The exception is expected based on the assumption that two value extractors are type-compliant and container-element-compliant with the the first container element of IWrapper212<@Valid Bean21, @Valid Bean22> wrapper. While two of the value extractors registered in the test are type-compliant (IWrapper211ValueExtractor0 and IWrapper212ValueExtractor0), only one of them is container-element-compliant (IWrapper212ValueExtractor0).

The fix is to change the type of wrapper into IWrapper21, in which case indeed the two extractors both are type-compliant and container-element-compliant and an exception must be raised.

Environment

None

Activity

Show:
Fixed

Details

Assignee

Reporter

Bug Testcase Reminder (view)

Bug reports should generally be accompanied by a test case!

Bug Testcase Reminder (edit)

Bug reports should generally be accompanied by a test case!

Participants

Guillaume Smet
Gunnar Morling

Pull Request

https://github.com/beanvalidation/beanvalidation-tck/pull/149
https://github.com/beanvalidation/beanvalidation-tck/pull/149

Components

Fix versions

Affects versions

Priority

Created July 24, 2017 at 10:18 AM
Updated August 3, 2017 at 4:19 PM
Resolved July 24, 2017 at 10:32 AM