Laurie, Thanks very much for replying to my query - I've been pondering this one over the weekend and I thought I had a reason it wouldn't work, but having just reread what you said I think you might be right. I have been wondering about using a phase listener for a while for performing initialization (I'll take a look at Shale too) so I'll give that a go before I chuck the towel in with process scopes and go back to session scopes.
It won't be particularly elegant though because I'll have to check which page is being loaded in the phase listener. Oh well, if it works, then that'll be progress. Thanks again for the insight, Jim -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper Sent: 16 February 2006 19:07 To: users@myfaces.apache.org Subject: Re: ADF Faces processScope problem Based on the comment, it would seem that your problem is that you need to do your initialization *earlier* in the phase cycle -- i.e. before the Render Response phase begins. Shale's View Controller feature [1] provides a great solution to this; the init() and prerender() hooks would be the two options you'd want to consider for doing your initialization. If you don't want to use Shale, you could implement the same approach in your own app with a little bit more work. Basically, you'd implement your own phase listener and call your initialization logic in beforePhase(). I don't have a sample code snip to hand, but it's fairly straightforward. L. [1] http://struts.apache.org/struts-shale/features-view-controller.html James Moores wrote: > <snip> > // =-=AEW This strategy assumes that the ProcessScopeMap > // will be inherited from a prior request, have things > // added and removed prior to Render Response *without > // the token being requested*, then have the token used > // repeatedly during Render Response *without further > // mutations*. Both of these assumptions seem very > // dubious! > <snip>
