You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2011/08/12 00:12:27 UTC

[jira] [Closed] (TAP5-172) It should be possible to merge validation constraints from the @Validate annotation with those explicitly set via the validate parameter

     [ https://issues.apache.org/jira/browse/TAP5-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Massimo Lusetti closed TAP5-172.
--------------------------------

       Resolution: Won't Fix
    Fix Version/s: 5.3

Please open a new one for 5.3 if this still applicable

> It should be possible to merge validation constraints from the @Validate annotation with those explicitly set via the validate parameter
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-172
>                 URL: https://issues.apache.org/jira/browse/TAP5-172
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>             Fix For: 5.3
>
>
> It seems that some validation concerns (such as validations that relate two fields) can't be expressed in the @Validate annotation; at the same time, we don't want to have needless duplication.
> I propose the special name "default" as a validator name that means the default validators derived from the @Validate annotation (or other rules).
> Thus:
> <t:textfield t:id="backOrderCount" validate="default,lteq=orderCount"/>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira