We are using ADF's token state saving, so I had to add a mechanism to increment the token hidden field on the document during the AJAX request. That resolved this.
Matt Matt Tyson wrote: > > I've got a phaseListener that handle my ajax requests. I can successfully > recover the view and component by either manually using restoreView or by > waiting till the afterPhase() of the restoreView phase. > > Once I have the component, I manually call its encode methods, followed by > the saveSerializedView method. > > This works fine, except that the state on the component that has changed > is not preserved. So, on the next request to the page, the updated state > is lost. > > Using some trickery, I have discovered that the saveSerializedView call is > writing the correct state out, however, on the subsequent request, the old > state is what is restored. > > So to summarize, I am trying to mimick the lifecycle by manually > performing: restoreView, encodeResponse, and saveState. I am apparently > missing some part of this saveState process (something that the > renderResponse phase handles, the writeState method perhaps - it throws an > NPE if I call it manually at this stage). > > Best Regards, > Matt > -- View this message in context: http://www.nabble.com/PhaseListener-and-saveSerializedView-tf3043069.html#a8476058 Sent from the MyFaces - Users mailing list archive at Nabble.com.
