From adffaces-user-return-2046-apmail-incubator-adffaces-user-archive=incubator.apache.org@incubator.apache.org Tue Jan 30 08:57:11 2007 Return-Path: Delivered-To: apmail-incubator-adffaces-user-archive@locus.apache.org Received: (qmail 70292 invoked from network); 30 Jan 2007 08:57:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jan 2007 08:57:11 -0000 Received: (qmail 31834 invoked by uid 500); 30 Jan 2007 08:57:17 -0000 Delivered-To: apmail-incubator-adffaces-user-archive@incubator.apache.org Received: (qmail 31814 invoked by uid 500); 30 Jan 2007 08:57:16 -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 31805 invoked by uid 99); 30 Jan 2007 08:57:16 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jan 2007 00:57:16 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [213.203.242.226] (HELO mail2.sinner-schrader.de) (213.203.242.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jan 2007 00:57:07 -0800 Received: from ex1.S2.int (smtp.sinner-schrader.de [172.16.36.1]) by mail2.sinner-schrader.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id l0U8eVtR031683 for ; Tue, 30 Jan 2007 09:40:31 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: AW: Shale and dialog framework Date: Tue, 30 Jan 2007 09:56:40 +0100 Message-ID: <1F701D303A73F2458C1F9B1439C115E40132F981@ex1.S2.int> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Shale and dialog framework Thread-Index: AcdD7rccYwlJy7kbTGO48dx4V3+kuQAXSjWA From: "Meyer, Stefan" To: X-Virus-Checked: Checked by ClamAV on apache.org The issue is pretty obvious. The Dialog framework launches a popup in = the onload js event, if the outcome / action starts with the "dialog:" = keyword and the action was launched by a commandButton/commandLink with = the useWindow attribute set to true. Basically the dialog framework = renders two views in two separate windows at once. The outcome specifies = the view to display in the popup window while the orignial view is left = unchanged. Therefore shale calls the lifecycle methods in both requests = on the same viewController. That Viewcontroller should only handle the = popup view though. Stefan -----Urspr=FCngliche Nachricht----- Von: craigmcc@gmail.com [mailto:craigmcc@gmail.com] Im Auftrag von Craig = McClanahan Gesendet: Montag, 29. Januar 2007 22:44 An: adffaces-user@incubator.apache.org Betreff: Re: Shale and dialog framework On 1/29/07, Laurie Harper wrote: > > On 29-Jan-07, at 2:21 PM, Craig McClanahan wrote: > > On 1/29/07, Meyer, Stefan wrote: > >> The Viewcontroller does not work well with the dialog framework,=20 > >> because the lifecycle methods are called on the popup view bean for = > >> the parent and child request and not at all for the launching view. = > >> Fixing this would maybe mean, that the action outcome cannot define = > >> the view to present in the popup. > > > > Stefan, > > > > I am not sure I quite get what you mean here. > > > > My assumption, when you are using a popup, is that you'll be using=20 > > client side JavaScript to actually create the popup. Here's a=20 > > snippet of code from our "shale-test-dialog-basic" and=20 > > "shale-test-dialog-scxml" test applications that does it: > > > > > ','popup','height=3D600,width=3D400')"/> > > > > Note that this does *not* send back a request for the calling view=20 > > (the page in which the JavaScript above was embedded), so there is=20 > > no reason to invoke any callback methods for it. This request will=20 > > open a new window, and the callbacks for the "menu.faces" page will=20 > > be called as expected. > > > > What part of this behavior is not working for you? > > > > Craig > > I think the OP is talking about how Shale's View Controller=20 > functionality interacts with Trinidad's dialog framework, which relies = > on PPR and has a somewhat more involved request/response structure. Well, that would make sense given this is on the Trinidad list ... gotta = check the mail headers before I make assumptions :-). Stefan, I'd suggest putting together a minimal test application that > demonstrates the problem and posting it as a WAR file in JIRA. A=20 > possibly unintended interaction between features from two different=20 > frameworks will be tough to diagnose without a testcase. That would definitely be helpful. Craig L. > -- > Laurie Harper > Open Source advocate, Java geek: http://www.holoweb.net/laurie > > > >