[ 
https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405026#comment-13405026
 ] 

Geoff Callender commented on TAP5-1808:
---------------------------------------

Does this mean that the browser will show the URL of the submit?
                
> Change Form to (by default) immediately render markup when there are 
> validation errors, to avoid creating the session
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1808
>                 URL: https://issues.apache.org/jira/browse/TAP5-1808
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: form, redirect-after-action
>             Fix For: 5.4
>
>
> Historically, Tapestry has needed to keep an instance of ValidationTracker in 
> the session between a form submit and a page re-render, to track user input 
> and input errors; this often means that it is necessary to create the 
> HttpSession just to store this transient value.  Tapestry 5.2 went through 
> some contusions to avoid creating the persistent ValidationTracker instance 
> until there were actual errors, to avoid creating the session.
> A better approach is to treat successful and failed form submits differently, 
> at least by default. For failed form submits, where the default is to 
> re-render the active page, the Form component could instead immediately 
> re-render the page.  The ValidationTracker instance would not ever have to be 
> persistent at that point.
> In this way, failed form submissions would be treated somewhat like requests 
> with unhandled exceptions: markup is streamed to the client web browser even 
> during a component event request.

--
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

        

Reply via email to