Fixed
Details
Assignee
Marko BekhtaMarko BekhtaReporter
Marko BekhtaMarko BekhtaBug 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
Marko BekhtaComponents
Fix versions
Priority
Major
Details
Details
Assignee
Marko Bekhta
Marko BekhtaReporter
Marko Bekhta
Marko BekhtaBug 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
Marko Bekhta
Components
Fix versions
Priority
Created August 20, 2024 at 11:06 AM
Updated September 4, 2024 at 4:24 PM
Resolved September 3, 2024 at 2:40 PM
Assume having two classes/interfaces as follows:
Where both
setAddresses
methods define exactly the same convert groups.Currently, this leads to a constraint declaration exception. According to the spec the group convert rule can be defined where the
@Valid
is placed, and that the same rules as for constraints in hierarchies should apply.Since we allow exactly the same set of constraints to be placed on the same methods in the hierarchy, we should also allow the placement of the group convert rules.
See also