Hi all,

I have following problem:
I have a jsf-page using a simple requestscoped backingbean, without any 
customcomponents etc..
I am using t:saveState to keep data between the requests.
The backingbean is inheriting from a common base class in which a HtmlInputDate 
is being used for an attributetype.
Everything is working fine as long as I have defined the following in my 
web.xml:

     <param-name>org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</param-name>
     <param-value>false</param-value>

When changing this config to "true" I get the following:

[2009-01-26 20:14:25,968] [http-8080-2] [ERROR] 
javax.faces.webapp._ErrorPageWriter - An exception occurred
javax.faces.FacesException: java.io.NotSerializableException: 
org.apache.myfaces.custom.date.HtmlInputDate

I'm not quite sure whether this is a bug or a feature but I was not aware that 
backingbeans should implement the Stateholder-interface...
I had a short discussion in: https://issues.apache.org/jira/browse/MYFACES-2141

Could anybody please bring light into my thoughts? :-)

The reason for me to try this change was that pages that work fine in a normal 
clickflow throw an exception
when waiting, let's say 90 min.
javax.servlet.ServletException /jsp/app/time/projecttimes.jsfNo saved view 
state could be found for the view identifier: /jsp/app/time/projecttimes.jsf

regards

Andrej

Reply via email to