RE: Client-side state saving (Was: Back Button problems)

[Arinaya <ar...@realidea.ca>]

Hi Manfred,

Mmmm... (light bulb illumines overhead) yes I had a few x:saveStates kicking
around.

It seems to me that I tried at one point to make the backing beans
serializable, and was still getting the same error, but removing those
saveStates (and changing backing bean scope to session) fixes the problem.

However, more problems arising....

Input Calendar gives an error: javax.servlet.jsp.JspException: Duplicate
component ID found in view. This only occurs when renderAsPopup=true, so I
assume that MyFaces assigns the same id to the input field and the button,
and that this is only a problem when state is saved on the client. How can I
fix this.

Also a bunch of problems with dataTables, sortableColumns and dataScrollers,
but need to look a little deeper into it before I can say anything.

Thanks,
Arinaya

> -----Original Message-----
> From: Manfred Geiler [mailto:manolito@apache.org] 
> Sent: Tuesday, November 16, 2004 11:25 AM
> To: MyFaces Discussion
> Subject: Re: Antwort: Re: Back Button problems
> 
> Arinaya wrote:
> > OK. I started deleting things a little more ruthlessly in my Tomcat 
> > directories, and got it working.
> > 
> > But I still get a java.io.NotSerializableException when 
> running with 
> > client side state saving. So I raised a bug on Jira.
> > 
> > I find it hard to believe that everyone who uses MyFaces is 
> forced to 
> > use server-side state saving. Is this the case? Is the cause of the 
> > NotSerializableException known?
> 
> No, definitive not!
> I personally always use client-side state saving and never 
> had this NotSerializableException problem.
> Are you using the <x:saveState> feature or <x:dataTable> with 
> preserveData set to true? Please examine your managed beans. 
> Any bean that is (perhaps indirectly) saved in state and is 
> not serializable?
> 
> 
> > Maybe I will just switch to RI.
> 
> Client-side state saving should *not* be a reason to switch to RI.
> 
> Please give us more infos about your problem.
> 
> Thanks,
> Manfred
> 
>