You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (Created) (JIRA)" <ji...@apache.org> on 2011/12/30 20:20:31 UTC
[jira] [Created] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
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
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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405208#comment-13405208 ]
Howard M. Lewis Ship commented on TAP5-1808:
--------------------------------------------
Also, some larger context: Over the next few releases, we will certainly be see a shift from HTML-based forms to Ajax-based forms, which bypasses the question of what's in the URL.
> 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405212#comment-13405212 ]
Howard M. Lewis Ship commented on TAP5-1808:
--------------------------------------------
To be clear; traditional HTML forms will be around, but will start to be used for less critical data entry. Anything sophisticated (i.e., anything that would require an FormInjector, FormFragment, etc.) today will be built using JavaScript client-side controller logic with a update via an Ajax request in the future. The work in 5.4 is to clear the hurdles that Tapestry 5.3 (and earlier) put up against this approach.
> 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405204#comment-13405204 ]
Howard M. Lewis Ship commented on TAP5-1808:
--------------------------------------------
Yes it does. There's a trade-off here. On the one hand, we are vastly simplifying things on the server, and significantly minimizing persistent state, as well as helping defer the creation of the HttpSession. On the other hand, forms with errors will be re-rerendered directly in the component event request, meaning that the URL will display a component-event URL; at least until the errors are corrected and the form submitted; at which point it will redirect to a normal, stable, page render URL.
> 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405803#comment-13405803 ]
Geoff Callender commented on TAP5-1808:
---------------------------------------
Sounds good to me. Bring it on!
> 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405208#comment-13405208 ]
Howard M. Lewis Ship commented on TAP5-1808:
--------------------------------------------
Also, some larger context: Over the next few releases, we will certainly be see a shift from HTML-based forms to Ajax-based forms, which bypasses the question of what's in the URL.
> 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405204#comment-13405204 ]
Howard M. Lewis Ship commented on TAP5-1808:
--------------------------------------------
Yes it does. There's a trade-off here. On the one hand, we are vastly simplifying things on the server, and significantly minimizing persistent state, as well as helping defer the creation of the HttpSession. On the other hand, forms with errors will be re-rerendered directly in the component event request, meaning that the URL will display a component-event URL; at least until the errors are corrected and the form submitted; at which point it will redirect to a normal, stable, page render URL.
> 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
[jira] [Closed] (TAP5-1808) Change Form to (by default) immediately
render markup when there are validation errors, to avoid creating the
session
Posted by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1808.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.4
Assignee: Howard M. Lewis Ship
> 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Closed] (TAP5-1808) Change Form to (by default) immediately
render markup when there are validation errors, to avoid creating the
session
Posted by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1808.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.4
Assignee: Howard M. Lewis Ship
> 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Geoff Callender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405803#comment-13405803 ]
Geoff Callender commented on TAP5-1808:
---------------------------------------
Sounds good to me. Bring it on!
> 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
[jira] [Commented] (TAP5-1808) Change Form to (by default)
immediately render markup when there are validation errors, to avoid
creating the session
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405212#comment-13405212 ]
Howard M. Lewis Ship commented on TAP5-1808:
--------------------------------------------
To be clear; traditional HTML forms will be around, but will start to be used for less critical data entry. Anything sophisticated (i.e., anything that would require an FormInjector, FormFragment, etc.) today will be built using JavaScript client-side controller logic with a update via an Ajax request in the future. The work in 5.4 is to clear the hurdles that Tapestry 5.3 (and earlier) put up against this approach.
> 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