| Key: |
SHALE-175
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Hermod Opstvedt
|
| Votes: |
3
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
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
|
|
Description
|
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
|
Show » |
| There are no subversion log entries for this issue yet.
|
|
Dialog statemachine and errorconditions should be queryable