+1! ADF missed a big feature, though. We should make a custom variable resolver that automatically checks the pageFlowScope Map for a variable name AFTER checking all the other scopes as required by the JSF spec. This would mean that you wouldn't have to prepend "pageFlowScope." onto all of your variable names.
Also the <setActionListener /> sounds handy as well. On Mon, 3 Jan 2005 00:11:37 +0100, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > Travis, > > I just read the article and think it is a fine concept. > Also their <setActionListener/> is nice. > It prevents developers from some work on > creating *detail* pages, as pointed out in the > article. > > So here is my +1 on that! > > Matthias > > -----Original Message----- > From: Travis Reeder [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 02, 2005 11:42 PM > To: MyFaces Discussion > Subject: Re: New Scope > > It looks like the smart people over at Oracle already implemented my > idea in ADF, they call it pageFlowScope: > http://tinyurl.com/5jwdc > > Implemented almost exactly the same way I had proposed. Anyone opposed > to working a new optional scope into my faces? I volunteer if > everyone's ok with it because I really badly need this. > > Travis > > Stefan Langer wrote: > Travis Reeder wrote: > > What do you guys think of this? > > http://www.crack3r.com/2004/12/another-scope-for-web-app-parameters.html > > I don't think this will work since there is no concept of a window in > the http protocol. How does the server know that a new window has been > opened? Unless the client tells it which currently it doesn't. So how do > you decide when to create and when to destroy the window scope? > > I think the idea of Korhonen seems more practical although I quite don't > see how to implement the deserialization behaviour in a consistent > mannor without being corruptible by the client. > > Just my two cents > > Stefan > > -- > Travis Reeder > Ecommstats Web Analytics > www.ecommstats.com > > -- -Heath Borders-Wing [EMAIL PROTECTED]
