Gerald Turner created RF-12046:
----------------------------------
Summary: JSR303 ConstraintViolation propertyPath support for
graphValidator
Key: RF-12046
URL: https://issues.jboss.org/browse/RF-12046
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.2.0.Final
Reporter: Gerald Turner
Priority: Optional
In JSR303 ยง 4.2 ConstraintViolation, there is the following note:
"From rootBean and propertyPath, it is possible to rebuild the context of the
failure"
Perhaps it would be possible for graphValidator to map ConstraintViolation
propertyPath to ValueExpressions, then iterate child EditableValueHolder
components and assign FacesMessages to clientIds of these components where it
finds a match, otherwise fallback on the current behavior of using the clientId
of the graphValidator itself (perhaps even adding an the option to use a null
clientId for global messages instead).
A more thorough example of this use-case is here:
http://stackoverflow.com/questions/5639088/cross-field-validation-with-inline-messaging-in-jsf-with-jsr-303
Comments at stackoverflow suggest MyFaces ExtVal Bean Validation can do the
trick, however I went down that road, their framework ignores
ConstraintViolation propertyPath as well (see:
http://old.nabble.com/Re%3A-ExtVal-BV-question-to33455513.html)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
