You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Adam Brod (JIRA)" <ji...@apache.org> on 2006/06/06 23:33:16 UTC
[jira] Commented: (SHALE-175) Dialog statemachine and
errorconditions should be queryable
[ http://issues.apache.org/struts/browse/SHALE-175?page=comments#action_37442 ]
Adam Brod commented on SHALE-175:
---------------------------------
It seems that using the back-button will often get the dialog into the intractable error state. We don't have to be super back-button friendly, but we can't pollute the user's session and give them errors on everything they do, just because they hit the back button one time.
> Dialog statemachine and errorconditions should be queryable
> -----------------------------------------------------------
>
> Key: SHALE-175
> URL: http://issues.apache.org/struts/browse/SHALE-175
> Project: Shale
> Type: Improvement
> Components: Core
> Versions: 1.0.3
> Reporter: Hermod Opstvedt
>
> Hi
> Having been fiddling around with the Shale dialogs, there is one thing that I feel could be improved on. The way it is now, if there is an error situation or if the user navigates away from a dialog and later on navigates to say the start of the dialog, an exception is raised. There is no way out of this, short of restarting the server. I think a more elegant sultion would be if the state-engine could be queried by for instance the bean that kicks off the dialog sequence. This way one could present a more meaningful and customizeable feedback to the user.
> Hermod
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira