[
https://issues.apache.org/jira/browse/TAPESTRY-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588747#action_12588747
]
Howard M. Lewis Ship commented on TAPESTRY-2354:
------------------------------------------------
I believe this would work; it's a bit of disruptive change.
I think if you want the tracker to have a different lifecycle than "flash", you
will need to explicitly bind it to a property whose field has the desired
lifecycle.
> Use "flash" persistence on Form's ValidationTracker
> ---------------------------------------------------
>
> Key: TAPESTRY-2354
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2354
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.11
> Reporter: Geoff Callender
>
> Currently, a Form's ValidationTracker inherits the default persistence
> strategy. The result is that by default the session becomes littered with
> ValidationTrackerImpl objects as you move from page to page.
> In response to this problem there have been several workarounds proposed in
> the mailing lists. They all involve making the ValidationTracker use "flash"
> persistence.
> Consequently, I'm proposing that we make "flash" the default for Form's
> ValidationTracker so we can all forget about it. After all, it would be very
> unusual to want a form's validation errors to be retained after the form has
> been displayed, regardless of what persistence strategy makes sense for any
> other component of the form.
> If there remains a situation in which it makes sense to override it, then
> perhaps that could be possible through a new parameter of the Form component.
--
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]
