From adffaces-user-return-797-apmail-incubator-adffaces-user-archive=incubator.apache.org@incubator.apache.org Sat Aug 26 04:02:17 2006
Return-Path: <adffaces-user-return-797-apmail-incubator-adffaces-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-adffaces-user-archive@locus.apache.org
Received: (qmail 125 invoked from network); 26 Aug 2006 04:02:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 26 Aug 2006 04:02:15 -0000
Received: (qmail 71229 invoked by uid 500); 26 Aug 2006 04:02:14 -0000
Delivered-To: apmail-incubator-adffaces-user-archive@incubator.apache.org
Received: (qmail 71052 invoked by uid 500); 26 Aug 2006 04:02:14 -0000
Mailing-List: contact adffaces-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:adffaces-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:adffaces-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:adffaces-user@incubator.apache.org>
List-Id: <adffaces-user.incubator.apache.org>
Reply-To: adffaces-user@incubator.apache.org
Delivered-To: mailing list adffaces-user@incubator.apache.org
Received: (qmail 71043 invoked by uid 99); 26 Aug 2006 04:02:14 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Aug 2006 21:02:14 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=MSGID_FROM_MTA_HEADER,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of laurieharper@sympatico.ca designates 65.54.191.170 as permitted sender)
Received: from [65.54.191.170] (HELO BAYC1-PASMTP10.CEZ.ICE) (65.54.191.170)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Aug 2006 21:02:13 -0700
Message-ID: <BAYC1-PASMTP10C3CBB920008D918BD0C9AB3A0@CEZ.ICE>
X-Originating-IP: [69.156.12.187]
X-Originating-Email: [laurieharper@sympatico.ca]
Received: from [192.168.1.101] ([69.156.12.187]) by BAYC1-PASMTP10.CEZ.ICE over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 25 Aug 2006 21:04:57 -0700
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <E68B55F8-736D-44B8-974D-50902D75E1D8@holoweb.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: adffaces-user@incubator.apache.org
From: Laurie Harper <laurie@holoweb.net>
Subject: Dialogs and data passing
Date: Sat, 26 Aug 2006 00:01:35 -0400
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 26 Aug 2006 04:04:57.0171 (UTC) FILETIME=[CB025230:01C6C8C4]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

I'm trying to figure out how to pass data into a dialog view, using  
dialog parameters and/or page flow scope. Unfortunately, there seems  
to be a process order disparity, unless I'm missing something  
obvious... ;-)

Say I have a view, view1.xhtml, backed by a managed bean named view1.  
In my view, I include the following markup:

   <tr:commandLink action="#{view1.action}" launchListener="# 
{view1.launch} ...

and in my backing bean, I have the methods defined as

   public String action() {
     System.out.println("action");
     getPageFlowScope().put("pfs", "pfs1");
     return "dialog:view2";
   }
   public void launch(LaunchEvent e) {
     System.out.println("launch");
     getPageFlowScope().put("pfs", "pfs2");
     e.getDialogParameters().put("data", "foo");
   }

I have a navigation rule mapping dialog:view2 to a view, view2.xhtml,  
backed by a managed bean named view2, which is a Shale  
ViewController. The life-cycle methods on view2 look like

   public void init() {
     System.out.println("init:");
     System.out.println("  pfs="+getPageFlowScope().get("pfs"));
     System.out.println("  data="+getPageFlowScope().get("data"));
   }
   public void preprocess() {
     System.out.println("preprocess:");
     System.out.println("  pfs="+getPageFlowScope().get("pfs"));
     System.out.println("  data="+getPageFlowScope().get("data"));
   }
   public void prerender() {
     System.out.println("prerender:");
     System.out.println("  pfs="+getPageFlowScope().get("pfs"));
     System.out.println("  data="+getPageFlowScope().get("data"));
   }

Now, when I click the link, the following is printed to the console:

action
init:
   pfs=pfs1
   data=null
launch
prerender:
   pfs=pfs1
   data=null
init:
   pfs=pfs2
   data=foo
prerender: data=foo
   pfs=pfs2
   data=foo

What I assume is happening is that the action fires, then navigation  
occurs; the Trinidad nav handler calls down to its delegate, which  
creates the target view. Trinidad's launch handler then stores that  
for later processing by the dialog mechanism and restores the  
previous view. Next, the dialog launch process kicks in, firing the  
launch listener, which sets up the dialog parameters. Then the new  
view gets rendered, but can't see the dialog parameters since it was  
created before they got set. Finally, the new window for the dialog  
opens, and a *new* request comes in, asking for the previously queued  
dialog view. The dialogs parameters are only now made available to  
the view.

The problem is if the dialog view needs the data that's passed  
through the dialog parameter ('data' here), which isn't available the  
first time through...

I've got things working for now by putting the data into page flow  
scope in action(), but that effectively means it's in the 'outer'  
scope rather than just the dialog scope -- and makes launch()  
redundant. So the question is, am I fundamentally misunderstanding  
how dialog parameters should be used?

L.
--
Laurie Harper
Open Source advocate, Java geek: http://www.holoweb.net/laurie
Founder, Zotech Software: http://www.zotechsoftware.com/