Frank Russo wrote:
O. That's good. I didn't know that.
*From:* Conway. Fintan (IT Solutions) [mailto:[EMAIL PROTECTED]
The big difference is that myFaces removes whatever it saves when there
is no longer any t:saveState's for the bean that was saved.
*From:* Frank Russo [mailto:[EMAIL PROTECTED]
*Subject:* Where does t:saveState save?
Is it in session? If so, how is that different from using a bean in
session?
Another advantage is that because it's saved in the component tree, if
you use the back button to go back a few pages and then click on a link
or button, you will get the value of that bean /as used on that page/
rather than one in the session which may subsequently have been changed.
(Assuming using client-side state saving or, I believe, MyFaces 1.1.2.)
Jon
--
.....................................................................
Dr Jonathan Harley .
. Email: [EMAIL PROTECTED]
Zac Parkplatz Ltd . Office Telephone: 024 7633 1375
www.parkplatz.net . Mobile: 079 4116 0423
