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/12 08:01:57 UTC
[jira] Resolved: (SHALE-351) Support events from
DialogContextManager in addition to DialogContext
[ http://issues.apache.org/struts/browse/SHALE-351?page=all ]
Craig McClanahan resolved SHALE-351.
------------------------------------
Fix Version/s: 1.0.4-SNAPSHOT
Resolution: Fixed
The bootstrapping concern has been addressed. In addition, the most common use cases for dialog events have been dealt with by automatically registering the "data" object as a DialogContextListener if it implements this interface.
> Support events from DialogContextManager in addition to DialogContext
> ---------------------------------------------------------------------
>
> Key: SHALE-351
> URL: http://issues.apache.org/struts/browse/SHALE-351
> Project: Shale
> Issue Type: New Feature
> Components: Dialog
> Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> The current dialog APIs make it possible to register for fine grained events on a particular DialogContext, but not on events from DialogContextManager. In particular, it is not currently possible to be notified when a new DialogContext instance is created via navigation. Address this by adding eventing to DialogContextManager along the following lines:
> * New DialogContextManagerListener interface with onCreate() and onRemove() methods
> * New AbstractDialogContextManager that implements the listener registration stuff
> (analogous to AbsractDialogContext for context level event)
> * Modify the two DialogContextManager implementations to extend this new base class
> and to call the event firing methods at the right times
> * Unit tests for all of the above (of course :-)
> * For naming consistency, consider renaming DialogListener to DialogContextListener
> and associated ripple effects. We can minimize transition impacts on current apps
> by leaving a deprecated DialogListener interface that simply extends DialogContextListener
> (and so on).
--
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