Dear Wiki user, You have subscribed to a wiki page or wiki category on "Shale Wiki" for change notification.
The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/DialogManagerFeature The comment on the change is: Add some really good ideas from Paul Spencer on the dev list ------------------------------------------------------------------------------ 1. State synchronization must deal appropriately with use of browser navigation buttons. 1. Implementation must not modify standard JSF semantics like "return null from an action method means redisplay the current view". 1. Must be possible to enter a dialog as a result of a JSF navigation rule. + 1. It must be possible to use the dialog management features without relying on any state save/restore facilities of the dialog functionality, as long as the application is managing its own state in this scenario. (Credit for this idea to Paul Spencer <paulsp AT apache.org>.) + 1. The framework must provide a configurable mechanism to deal with application exceptions that does not disable dialog functionality. (Credit for this idea to Paul Spencer <paulsp AT apache.org>.) === Desireable Requirements === @@ -58, +60 @@ 1. Support of either a custom dialog-defined JavaBean with properties for individual state data, or a generic Map, as the holder of state data. 1. Programmatic entry into, and exit from, a dialog instance (in addition to navigation based entry and exit state based exit). 1. A stable public API to access the static configuration of a dialog (as opposed to the dynamic state and context of an executing dialog instance). + 1. The framework should recognize updated configuration files and reload them, without requiring an application restart. (Credit for this idea to Paul Spencer <paulsp AT apache.org>.) === Nice To Have Requirements ===
