I’m trying out using BeanValidation for the JSR 303 parameter validation
extensions. It seems to work great, EXCEPT, it deoesn’t seem that there is
any way through the ConstraintViolation API to identify **which** parameter
caused a constraint violation.



Am I missing something, or is there really no way to determine which
parameters are in violation from the return value of a
MethodValidator.validateParameters() invocation?


-- 
Best regards,
Brian Maso
(949) 395-8551
[email protected]

Reply via email to