You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2010/04/13 08:20:51 UTC
[jira] Commented: (WICKET-2825) Create abstract form and property
validators to integrate JSR-303 beanvalidation
[ https://issues.apache.org/jira/browse/WICKET-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856319#action_12856319 ]
Martin Grigorov commented on WICKET-2825:
-----------------------------------------
Just to let you know that few developers created https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/jsr303-parent recently.
You can join forces and create a very nice and robust integration.
I am not Wicket core developer but if you want your work to be included in Wicket main libraries then you have to provide unit tests as well.
> 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
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira