You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Craig McClanahan (JIRA)" <ji...@apache.org> on 2006/12/23 03:38:57 UTC
[jira] Resolved: (SHALE-61) [shale] Maintaining dialog
synchronization when browser navigation buttons are used
[ http://issues.apache.org/struts/browse/SHALE-61?page=all ]
Craig McClanahan resolved SHALE-61.
-----------------------------------
Resolution: Fixed
Good catch by Rahul ... I had not yet implemented the event behavior we agreed upon when setOpaqueData() causes a change in the currently executing state. This has now been fixed for the basic implementation in a manner that is consistent with the SCXML implementation.
In addition, I've changed the default strategy for saving/restoring extended state information from "none" to "top". This is the most consistent choice with what the SCXML implementation does, and also covers the majority of use cases for recovering from back/forward button issues, without the overhead of the "stack" strategy (which can be selected if necessary).
> [shale] Maintaining dialog synchronization when browser navigation buttons are used
> -----------------------------------------------------------------------------------
>
> Key: SHALE-61
> URL: http://issues.apache.org/struts/browse/SHALE-61
> Project: Shale
> Issue Type: Bug
> Components: Dialog
> Environment: Operating System: other
> Platform: Other
> Reporter: Rahul Akolkar
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> I thought about making this an enhancement, but based on discussions on the
> dev list, it seems there is a fair bit of interest in solving this at the
> framework level.
> The issue is about maintaining client-server dialog synchronization when
> browser's navigation buttons are used while in the midst of a Shale dialog.
> More details -- and the proof of concept for one potential approach at
> resolving this -- are here:
> http://people.apache.org/~rahul/shale/align-dialog/
--
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