Looking closer I'm not sure it's a bval bug, the problem also goes away if I add a constraint annotation to the accessor, I've worked around it by only attempting validation if the constraint metadata says that the property is constrained.
On 9 July 2015 at 08:36, Tony Baines <[email protected]> wrote: > I've been migrating a project from the Hibernate JSR-303 implementation to > Bval and come across an odd corner case. > > If I define an accessor to a Boolean property with the 'is' prefix, I get > an IllegalArgumentException using Validator#validateValue. > > Switching to either a 'get' prefix or returning a primitive boolean brings > me back to expected behaviour. > > There's a test case here > > https://gist.github.com/tonybaines/1875be338c3545763245#file-booleanvalidationtest-java > > I'll take a look at the Bval code myself, but any suggestions for > something I've missed would be welcome (I couldn't find anything similar in > JIRA). > > Thanks > ~Tony > > > -- > > ~Tony > -- ~Tony
