Return-Path: Delivered-To: apmail-shale-issues-archive@locus.apache.org Received: (qmail 20015 invoked from network); 4 Dec 2006 18:01:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Dec 2006 18:01:18 -0000 Received: (qmail 93436 invoked by uid 500); 4 Dec 2006 18:01:27 -0000 Delivered-To: apmail-shale-issues-archive@shale.apache.org Received: (qmail 93383 invoked by uid 500); 4 Dec 2006 18:01:27 -0000 Mailing-List: contact issues-help@shale.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@shale.apache.org Delivered-To: mailing list issues@shale.apache.org Received: (qmail 93367 invoked by uid 99); 4 Dec 2006 18:01:26 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 10:01:26 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 10:01:17 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7A6FE7141E4 for ; Mon, 4 Dec 2006 10:00:57 -0800 (PST) Message-ID: <1833912.1165255257481.JavaMail.jira@brutus> Date: Mon, 4 Dec 2006 10:00:57 -0800 (PST) From: "Craig McClanahan (JIRA)" To: issues@shale.apache.org Subject: [jira] Created: (SHALE-351) Support events from DialogContextManager in addition to DialogContext MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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 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