[
https://issues.apache.org/jira/browse/TAPESTRY-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590676#action_12590676
]
Geoff Callender commented on TAPESTRY-2362:
-------------------------------------------
Scratch that - it's just wrong.
> It should be possible to merge validation constraints from the @Validate
> annotation with those explicitly set via the validate parameter
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2362
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2362
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.11
> Reporter: Howard M. Lewis Ship
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
