> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz > Sent: Monday, October 09, 2006 1:26 PM > To: users@myfaces.apache.org > Subject: Re: <t:savestate.. component binding serializable problem > > CarlHowarth schrieb: > > Hi, > > > > I have an app that uses the tomahawk savestate component to save the > state > > of the backing bean. I have just tried bind a selectonemenu component to > the > > backing bean however as the HtmlSelectOneMenu class is not serializable > I > > get an error as this can not be saved. > > > > If I change to session scope, removing the savestate component the app > > works, however I do not want the bean to be stored at session level. Has > > anyone had this problem/got a work-around?
[[Madhav]] If you look at the tomahawk code, then you will realize that the savestate also uses the session to store. However it takes the entire responsibility of putting the state in session and then removing it as well. The general feeling that developers have got is that I am not using the session, but is it really true? **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***
