RE: savestate question

[Tom Butler]

Found the problem here.  On the second page, I also included  a t:saveState tag for the backing bean from the previous page (page that linked to second page): <t:saveState value="#{searchispbean}" />   I must of missed this somewhere, but also this did not seem obvious.  It seemed logical that if I used <t:saveState> on the first page with the backing bean, that when I linked to the second page, and then came back to the first page, then the object would be read from wherever it was serialized to.  Having to place a <t:saveState> on the second page (to save the state for the same backing bean from the first page) does not seem to make sense?  Why would I need to re-serialize the bean again on the second page?  Anyways, if this works I’ll leave it as is – I’d just like to understand the ‘why?’.   From: Tom Butler [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 05, 2006 10:09 PM To: users@myfaces.apache.org Subject: t:savestate question   Within .jsp page I use t:saveState to save the backing bean. <t:saveState value="#{searchispbean}" />   t:saveState works to some degree, because when I remove it, t:datascroller can not display the datamodel (property on backing bean) when I scroll from the first page to the second page - with t:saveState enabled, this works.   However, when I leave the page with the t:saveState to another page, and then come back, the backing bean data has not been saved.     The backing bean does implement the Serializable interface (the only addition I have made to the class is adding the “implements Serializable” on the class definition – I did not add a serialVersionUID variable or anything else?): public class SearchIspBean extends SortableList implements Serializable  {….}   Any suggestions?