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
