Actually this seems either like a bug in the RI to me, since savestate does nothing fancy which should not work in the RI. It basically just does what every component does in the save and restore phase. Or a bug by the user.
Maybe some of the classes in the original tree are not serializable, which could cause a problem, due to the fact that the beans themselves are serialized by saveState. Mike Kienenberger schrieb: > Rick, > > Sorry. I can't help you. I've never used the JSF RI, nor do I use > server-side state saving. > > You could either implement the special phase listener described in > TOMAHAWK-134 or you could try asking on the JSF RI list why > saveState/restoreState aren't called for server-side state saving. > > I'm cc'ing your message to the "MyFaces User mailing list" > <[email protected]> as you're far more likely to get help there > than emailing me directly. >
