That's very, very strange. Is there any possibility that you have a persistent page property that points to a component?
If you do, then that's a problem ... you should store the component's id persistently, and re-resolve the component from the id. -- [EMAIL PROTECTED] http://tapestry.sf.net > > We use WebSphere's session persistence which complains whenever anything is > put into session that is not serializable. We've been using a 1.0.7+ build > for some time with no issues. We are trying to upgrade to 2.0.2a and are > now getting an error about Foreach not being serializable. Has anything > changed in this area? > > > -C > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
