[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-user
Subject:    RE: A bunch of belated answers about ADF
From:       "James Moores" <James.Moores () smartspread ! com>
Date:       2006-02-28 15:29:15
Message-ID: 5E0BE8CB5454854291780708D51BCB1203153B () ldn1s001pexc ! VAMEUROPE ! COM
[Download RAW message or body]

Ok, I'll give that a go, thanks.

Jim 

-----Original Message-----
From: Adam Winer [mailto:awiner@gmail.com] 
Sent: 28 February 2006 15:27
To: MyFaces Discussion
Subject: Re: A bunch of belated answers about ADF

The simplest possible PhaseListener I can imagine is one that just does:
  processScope.put("a", "b");

... that is, chucks some nonsense data on, and makes sure that the
system always generates a new token for every request.  That'd be enough
to bypass the issue you're encountering.

-- Adam



On 2/28/06, James Moores <James.Moores@smartspread.com> wrote:
> Adam,
>
> Thanks for getting around answering so many of our questions.  I gave 
> up on the use of processScope in the end (and switched back to session

> scopes), but I've kept access to all my properties abstracted so I can

> easily switch back to processScopes if/when I can get one of the 
> suggested solutions to work.  I started on the phaseListener idea but 
> quickly realized it would be a bit of a nightmare because each 
> initialization is page specific (and phaseListeners aren't), so I 
> might now give one of the other ideas a go.
>
> Thanks again to you (and all those others who gave advice on this 
> topic),
>
> Cheers,
>
> Jim
> --
> Jim Moores, SmartSpread Ltd, UK.
>
> -----Original Message-----
> From: Adam Winer [mailto:awiner@gmail.com]
> Sent: 26 February 2006 21:21
> To: users@myfaces.apache.org
> Subject: A bunch of belated answers about ADF
>
> <snip>
> - "I use the ADF Faces 'Process scope' facility a great deal...."
>
> This was a problem with values disappearing from the process scope.
> The code was relying on a dummy "get" method being triggered during 
> Render Response to do initialization.  It does hit a limitation of our

> processScope - it's not thrilled with being mutated during Render 
> Response..  Laurie Harper's suggestion of using Shale is a good one; 
> with JSF 1.2, a beforePhaseListener on the f:view would work well too.
>  You could hack around the processScope limitation by forcibly putting

> something, anything, in the processScope before Render Response, so 
> we'll at least generate an ID correctly.
>
> <snip>
> Regards,
> Adam Winer
>

[prev in list] [next in list] [prev in thread] [next in thread]