shale-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig McClanahan (JIRA)" <>
Subject [jira] Resolved: (SHALE-175) Dialog statemachine and errorconditions should be queryable
Date Fri, 20 Oct 2006 03:21:25 GMT
     [ ]

Craig McClanahan resolved SHALE-175.

    Fix Version/s: 1.0.4-SNAPSHOT
       Resolution: Fixed

While there is still a bit more work to do for browser buttons (and there's an open issue
for that already), the current shale-dialog functionality provides a much more robust mechanism
for dealing with exceptions thrown during execution of a dialog -- you can register a listener
whose onException() method will be called when such an exception is thrown, and can therefore
deal with it as desired.  So, I'm going to mark this improvement request as fixed.

> Dialog statemachine and errorconditions should be queryable
> -----------------------------------------------------------
>                 Key: SHALE-175
>                 URL:
>             Project: Shale
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.3-SNAPSHOT
>            Reporter: Hermod Opstvedt
>             Fix For: 1.0.4-SNAPSHOT
> 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:
For more information on JIRA, see:


View raw message