You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/24 23:57:53 UTC

[jira] [Resolved] (TAP5-1856) Documentation for SubmitMode.CANCEL is out of date w.r.t. new 5.3 form cancel logic

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

Howard M. Lewis Ship resolved TAP5-1856.
----------------------------------------

    Resolution: Invalid

On review, the documentation was actually correct (some of my recollections were not).
                
> Documentation for SubmitMode.CANCEL is out of date w.r.t. new 5.3 form cancel logic 
> ------------------------------------------------------------------------------------
>
>                 Key: TAP5-1856
>                 URL: https://issues.apache.org/jira/browse/TAP5-1856
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> The documentation for SubmitMode claims that server-side validation still occurs; this was true in 5.2 (SubmitModel.CANCEL was purely a client-side behavior then), but in 5.3, the CANCEL means that server-side validation and other processing is bypassed.
> What's really needed is a third option, perhaps UNCONDITIONAL, meaning to bypass client-side validation, but continue normally on the server-side.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira