Depends, It saves the information into the component tree. So if you are using client-side state saving, it is saved to the client's browser inside a hidden input tag. If you are using server-side state, it is saved into the users HttpSession and lives as long as the session, unless booted by another view state (once the maximum number of views to save has been reached).
-Andrew On 9/19/07, kewldude <[EMAIL PROTECTED]> wrote: > > How long is the duration of the objects in <t:saveState>. Ive read somewhere > that it lasts longer than request, but shorter than session. Is there a > fixed value with regard to its duration in memory? The reason I ask is > because I have a managed bean that is saved in t:saveState and there comes a > time that it expires and when a user clicks a button that is wired to my > managed bean, a popup windows displays gthis message: > > Reqest error, status:500 Internal Server Error > Message : undefined > > I want to trap this kind of scenario so I can give a more meaningful status > to the user. > -- > View this message in context: > http://www.nabble.com/%3Ct%3AsaveState%3E---how-long---tf4483153.html#a12784550 > Sent from the MyFaces - Users mailing list archive at Nabble.com. > >
