- Using a different id for the same bean on two different pages. - Not correctly implementing Serializable or Stateholder. - Navigating to a new page (or the same page without using null) and using <redirect/> in your navigation rule. - Using facelets and not defining the t namespace.
On 4/20/07, Francisco Passos <[EMAIL PROTECTED]> wrote:
What might cause t:saveState to not maintain the bean state from one request to the next?
