> Why do you want to have JspStateManagerImpl serializable?! > From what I see from the code, the only thing that has to be > Serializable is the SerializedView. > SerializedView includes the two fields _structure and _state. > _structure is a TreeStructComponent which is Serializable and _state is > fetched from viewRoot.processSaveState, so must also be Serializable.
I don't really want it Serializable. That was just my initial reaction to the exception I experienced in Tomcat. Something is definitely amiss though because for some reason, Tomcat was trying to serialize that class. I assumed this was related to the state saving. In fact, I'm pretty sure it is because if you change to client-side state saving you do not get the exception. I don't really know anything about the particulars regarding state saving in JSF (yet.) Perhaps you could try running some simple examples with server-side state saving and reproduce? Matthias was able to reproduce this easily. I will start investigating more seriously once I finish up on the forceId project I've embarked on. > Manfred sean
