Action: Click on "Car Color" sortable header.
Outcome: Error condition.
war file *
code ^
Action: Click on "Car Color" sortable header.
Outcome: Correct sort in IFrame.
| Shale distro version | Screen 1 | Screen 2 |
| Nightly |
Action: Click on "Car Color" sortable header. |
Outcome: Error condition. |
|
Shale with concept of inconsequential triggers war file * code ^ |
Action: Click on "Car Color" sortable header. |
Outcome: Correct sort in IFrame. |
* - Rename to .war since file will probably download with .zip appended. Scroll to bottom of
welcome page, once deployed, to find link for the dialog whose screenshots appear above.
^ - Thing to see in code is proof of concept of relevant or "inconsequential" triggers,
in handleNavigation()
The proof of concept uses SCXML dialogs, see SCXML in Shale, with implicit transitions, plus the concept of inconsequential triggers (see below).
These are events which do not have any consequence on the state of a Shale dialog, and hence are best delegated to the original dialog navigation handler. An "inconsequential" trigger may be defined as one that does not cause any of the dialog transitions to be followed.
Thus, a dialog navigation strategy should delegate if (and only if) it receives:
This material has not been reviewed by the Apache Struts Shale team.