[ http://issues.apache.org/struts/browse/SHALE-175?page=comments#action_37575 ]
Dominique Jean-Prost commented on SHALE-175: -------------------------------------------- one of the problem is that the exception raised is very generic (ie IllegalArgumentException). I think it could be at least changed to something a bit more specific, for example : ShaleStateMachineUnsynchronizedException or whatever instead of the IllegalArgument. Without needing a too much complex change that seems to be needed to fix the whole stuff, it could add a way to deal with the issue. > 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
