From adffaces-user-return-780-apmail-incubator-adffaces-user-archive=incubator.apache.org@incubator.apache.org Thu Aug 24 05:45:29 2006 Return-Path: Delivered-To: apmail-incubator-adffaces-user-archive@locus.apache.org Received: (qmail 64393 invoked from network); 24 Aug 2006 05:45:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Aug 2006 05:45:28 -0000 Received: (qmail 32328 invoked by uid 500); 24 Aug 2006 05:45:28 -0000 Delivered-To: apmail-incubator-adffaces-user-archive@incubator.apache.org Received: (qmail 32148 invoked by uid 500); 24 Aug 2006 05:45:28 -0000 Mailing-List: contact adffaces-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: adffaces-user@incubator.apache.org Delivered-To: mailing list adffaces-user@incubator.apache.org Received: (qmail 32138 invoked by uid 99); 24 Aug 2006 05:45:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2006 22:45:28 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mwessendorf@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2006 22:45:27 -0700 Received: by ug-out-1314.google.com with SMTP id u40so383536ugc for ; Wed, 23 Aug 2006 22:45:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Y5IyHINdu/kNo/QHWRHCTX54Pk+5xRa3nSkr7QN/tcDD5u3QPL2I02Ci/PcfrQLBAVDOhRBo3z6U76+3IMNar875U+CT8TisagpJ/A+1WLD2Fv13T5IX4gBBaKC4LlBWAu7NUIeRUiZOVy1cKGWVfvwnb8Rh6OmnG0nTtAYA1oo= Received: by 10.66.221.19 with SMTP id t19mr693037ugg; Wed, 23 Aug 2006 22:45:05 -0700 (PDT) Received: by 10.66.225.14 with HTTP; Wed, 23 Aug 2006 22:45:05 -0700 (PDT) Message-ID: <71235db40608232245n4a45a241t93504999279daecb@mail.gmail.com> Date: Wed, 23 Aug 2006 22:45:05 -0700 From: "Matthias Wessendorf" Sender: mwessendorf@gmail.com To: adffaces-user@incubator.apache.org Subject: Re: Closing dialogs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <71235db40608232048h7bacbb97j898136d64cee81ec@mail.gmail.com> X-Google-Sender-Auth: d593c2c18a3e0dca X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N oh yes, that is very specific to my use case. I create a user during my wizard and return it on the last page. that's all (I use the processScope here, not a must) returnFromDialog() works too. I think Jonas will port this article to Trinidad ([1]). [1] http://www.oracle.com/technology/products/jdev/101/howtos/adfdialog/index.html On 8/23/06, Laurie Harper wrote: > Hmm, I'm not sure what you mean. Presumably ${processScope.tmpUser} > refers to an instance of a return listener that calls returnFromDialog > ()? I realized after posting that I could always put the > returnFromDialog() call into a method on a managed bean that wasn't > tied to a specific view. I guess that reduces the need for a 'magic' > outcome for closing dialogs. > > L. > > On 23-Aug-06, at 11:48 PM, Matthias Wessendorf wrote: > > > inside my dialog, i have two pages (use the processScope for > > storing stuff) > > > > that is in my button from the last page > > > > > > > > > > > > > > > > On 8/23/06, Laurie Harper wrote: > >> A dialog can be launched purely through navigation configuration, > >> as in > >> > >> > >> ... > >> > >> > >> dialog:blah > >> /some/view > >> > >> > >> > >> A dialog is initiated based on the from-outcome having the > >> appropriate prefix; no Java code is required. As far as I can tell, > >> that's not true for terminating a dialog, though; you have to call > >> RequestContext.returnFromDialog() from somewhere. > >> > >> Is that correct? Or is there a 'magic' outcome that can be used to do > >> this implicitly, as in something like > >> > >> > >> > >> If there isn't, would this be worth adding? > >> > >> L. > >> -- > >> Laurie Harper > >> Open Source advocate, Java geek: http://www.holoweb.net/laurie > >> Founder, Zotech Software: http://www.zotechsoftware.com/ > >> > >> > >> > >> > > > > > > -- > > Matthias Wessendorf > > > > further stuff: > > blog: http://jroller.com/page/mwessendorf > > mail: mwessendorf-at-gmail-dot-com > > -- > Laurie Harper > Open Source advocate, Java geek: http://www.holoweb.net/laurie > Founder, Zotech Software: http://www.zotechsoftware.com/ > > > > -- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com