Return-Path: Delivered-To: apmail-shale-issues-archive@locus.apache.org Received: (qmail 26819 invoked from network); 3 Jul 2007 21:51:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Jul 2007 21:51:48 -0000 Received: (qmail 30083 invoked by uid 500); 3 Jul 2007 21:51:51 -0000 Delivered-To: apmail-shale-issues-archive@shale.apache.org Received: (qmail 30061 invoked by uid 500); 3 Jul 2007 21:51:50 -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 30052 invoked by uid 99); 3 Jul 2007 21:51:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2007 14:51:50 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED 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; Tue, 03 Jul 2007 14:51:47 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0561F7141F2 for ; Tue, 3 Jul 2007 14:51:27 -0700 (PDT) Message-ID: <1002159.1183499487019.JavaMail.jira@brutus> Date: Tue, 3 Jul 2007 14:51:27 -0700 (PDT) From: "Rahul Akolkar (JIRA)" To: issues@shale.apache.org Subject: [jira] Commented: (SHALE-454) extending AbstractDialogContextListener getDialogContext().getName() returns null in onStart() method In-Reply-To: <25470842.1183405046422.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/struts/browse/SHALE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41341 ] Rahul Akolkar commented on SHALE-454: ------------------------------------- The reason is similar. I think you may have posted a simplified snippet, otherwise its possible to set the dialog data in the dialog descriptor itself, rather than using the approach above. In any case, in the above scenario, I'd recommend using onStart() for making sure all resources are available for the instantiation of dialog data, but actually instantiating (and configuring) it in onActivate(). As an aside, at first glance, I suspect a single onEntry() callback might be escaping out before the onActivate() call, and I intend to take a better look at that later in the week. > extending AbstractDialogContextListener getDialogContext().getName() returns null in onStart() method > ----------------------------------------------------------------------------------------------------- > > Key: SHALE-454 > URL: https://issues.apache.org/struts/browse/SHALE-454 > Project: Shale > Issue Type: Bug > Components: Dialog > Affects Versions: 1.1.0-SNAPSHOT > Reporter: mario buonopane > > i'm using Shale Basic Dialog 1.1.0 and I have a my DialogContextListener extending AbstractDialogContextListener. In onStart() and onStop() methods, getDialogContext().getName() returns null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.