[
https://issues.apache.org/jira/browse/WICKET-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2825.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg
there is also a project here:
https://github.com/42Lines/wicket-bean-validation
the abstract things are not too helpful because different libraries want to
structure the code differently...
> Create abstract form and property validators to integrate JSR-303
> beanvalidation
> --------------------------------------------------------------------------------
>
> Key: WICKET-2825
> URL: https://issues.apache.org/jira/browse/WICKET-2825
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.4.7
> Reporter: Carlos Vara
> Assignee: Igor Vaynberg
> Attachments: AbstractJsr303FormValidator.java,
> AbstractJsr303PropertyValidator.java, jsr303.tar, wicket-pom.patch
>
>
> There has been many requests and buzz about this in the mailing list.
> However, the available solutions either inject the Validator using some DI
> framework or directly instantiate it, so they are tailored to the personal
> needs of the people that created those solutions.
> I think it would be great for Wicket to add 2 abstract form and property
> validators that left open the way to obtain the validator (an abstract
> getValidator() method), so they are also non-intrusive in wicket's code base
> (they only add javax.validation as dependecy, which is the minimum to
> integrate this).
> I have coded a proposal for these two validators, and also attach the
> additional patch to the pom (adding javax.validation as dependency). I have
> tested it in the trunk and works fine so far.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
