I was working in the ConstraintValidatorContext area and I think Example 3.16. Use of ConstraintValidatorContext was basically wrong.
It seems to me that we were able to return false without creating any ConstraintViolation context.
I have create a JIRA https://hibernate.onjira.com/browse/BVAL-296 and a pull request https://github.com/beanvalidation/beanvalidation-spec/pull/7
Can someone double check to make sure I did not have hallucination.
Emmanuel
Hi,
I just stumbled upon a question on SO [1], which basically is about
whether it's allowed to pass a complete property path (e.g.
"foos[1].bar") to Validator#validateProperty(), or whether only single
properties (e.g. "foos") can be validated using that method.
Based on a quick look into the API doc and the spec, I'd say only
single properties are supported here right now (the doc of the
parameter "propertyName" describes it as "property to validate"), but
I'm not really sure. WDYT?
If this is not supported as of BV 1.0, do you think it should be in 1.1?
--Gunnar
[1] http://stackoverflow.com/questions/10835595/hibernate-validator-calling-v...
It seems there is some kind of consensus that considering the runtime type instead of the satin type to build the property path is better.
Check out https://hibernate.onjira.com/browse/BVAL-226 and let me know if you object.
Otherwise, I plan to clarify this in the spec.
Emmanuel
