hi @ all,
for extracting constraints (e.g. to send (meta-)data, scripts,... to the
client-side), we
introduced ElementDescriptor#ConstraintFinder#unorderedAndMatchingGroups.
some details in view of jsf:
3 years ago we started to brainstorm such an idea for bv+jsf and we came up
with 10 very basic requirements.
however, there are too many different ideas out there how it should work
and each of them isn't trivial (+ has some issues).
since validation via ajax-requests doesn't have most issues we identified
with a client-side approach and it's available in jsf already, we stopped
working on it.
regards,
gerhard
2012/6/28 Michael Isvy <michael.isvy(a)gmail.com>
Hi,
I was discussing this topic with Emmanuel Bernard by email and Emmanuel
suggested that we move this conversation to this mailing-list, so here I
am :).
The idea would be to propose a javascript export of the bean validation
rules. In that way, it would become fairly easy to do "true client side
validation" (that is: validation that does not require access to the server
side until the form is completely valid, or nearly completely valid).
Many web technologies such as JSF, Spring MVC, Wicket, Tapestry...
integrate with JSR 303. Providing such export would be of great help for
users of those frameworks (or standard in the case of JSF).
Cheers,
Michael.
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev