[
https://issues.apache.org/struts/browse/SHALE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig McClanahan reassigned SHALE-399:
--------------------------------------
Assignee: Craig McClanahan
> Add activation and deactivation callbacks to DialogContextListener
> ------------------------------------------------------------------
>
> Key: SHALE-399
> URL: https://issues.apache.org/struts/browse/SHALE-399
> Project: Shale
> Issue Type: Improvement
> Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
>
> Based on user mailing list discussions with Paul Spencer (paulsp AT
> apache.org) and others, it would be nice to enable existing applications that
> use a session scoped variable to store "dialog" state information to using
> the dialog manager facility, *without* having to modify their pages or action
> methods. In particular, this means that value binding expressions using the
> name of the session scoped data bean should continue to work after migration.
> This use case would be facilitated by adding onActivate() and onDeactivate()
> callbacks ot the DialogContextListener interface, which would be invoked when
> a DialogContext instance is first placed into service for a request, and when
> it is removed. Then, provide a convenience DialogContextListener
> implementation which can be configured with a list of value binding
> expressions whose getValue() method should be called on deactivation (with
> the data stored in session scope), and whose setValue() method should be
> called on reactivation (pushing the data back into now-request-scope
> variables).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
