RE: another commandLink problem

[Garner, Shawn]

I tried client and now it blows up on every link on pages that use to work. I don't use the back button.  I just use the same url from a new browser window after I restart the server.   Shawn   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:55 PM To: MyFaces Discussion Subject: Re: another commandLink problem   >From: "Garner, Shawn" [EMAIL PROTECTED] >I've noticed my commandLinks don't go to the page the first time.  >It seems to reload the page and then if I click on it again it goes to >the next view. >    This is common behavior in MyFaces when you use the brower back button to a dirty page and repost it.  I believe it has to do with how the component tree's state is saved.  I suspect that myfaces only caches a single page.  So, navigation to a new page overrides the cached state of the old.  The double post is needed because the state manager can't resort the view and just skips to the render phase.     The RI behaves differently here.      >Anyone know what is causing this, how to fix it? >    Try turning on client side state saving.  You do this in your web deployment descriptor.     <context-param>     <param-name>javax.faces.STATE_SAVING_METHOD</param-name>     <param-value>client</param-value>   </context-param>   >Shawn     Gary **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.  ***************************************************************************