[
https://issues.apache.org/jira/browse/TAP5-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658753#action_12658753
]
Vjeran Marcinko commented on TAP5-182:
--------------------------------------
Yes, I'm currently using "validateForm" event handler, but it really feels as
workaround.
If implementation of this issue is problematic for some reason (eg.
back-compatibility or somethig internal), I would suggest that this workaround
be documented in T5 docs, something like -
"After form submits, use 'success' event handler to call business method when
all input validation passed successfully, but if for some reason you need to
stay on same page with form input fields shown (eg when business checked
exception is handled), then use 'validateForm' and return navigational result
to bypass input field clearing."
This would help T5 newbies to handle this frequent situation, though I guess it
would lead to "this isn't the simpliest solution" feeling.
> ValidationTracker input values should not be cleared before "success" event
> ---------------------------------------------------------------------------
>
> Key: TAP5-182
> URL: https://issues.apache.org/jira/browse/TAP5-182
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Vjeran Marcinko
> Assignee: Howard M. Lewis Ship
>
> As far as I understand, "success" handler is used to call business method
> after all input values have been successfuly validated. Unfortunately,
> ValidationTracker's input values are cleared prior to this "success" event,
> and two cases come to my mind when this is undesirable, both of which are
> rendering same form page after submit.
> 1. Some validation cannot be executed prior to calling business method and
> checked exceptions are thrown when action fails. These failures have to be
> caught inside "success" handler and user should stay on same form page
> displaying error message. Naturally, all input values should be displayed.
> 2. Input validation passed successfuly, but user wants to stay on same page -
> eg. displaying search results below search form. It is usually needed to see
> all those input values still there to let user know what search criteria he
> just entered.
> My suggestion is to not clear input values ever. If user leaves the form
> page, input values will get lost then, since ValidationTracker has "flash"
> persistance strategy, so it's all good in that case. In some rare cases where
> user wants to stay on same form page, but clear those input values, he should
> do it explicitly by calling some ValidationTracker.clear() method or such.
--
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]
