Just submitted a bug about Tapestry session deserialization:
http://sourceforge.net/tracker/index.php?func=detail&aid=662418&group_id=48132&atid=452068
Basically the problem is that Tomcat tries deserializing saved sessions on
startup before the application initializes the right shared Configuration
object. I wonder what what be the good way around it?
Maybe create some kind of "unlinked" DataContext, deferring the call to
"Configuration.getSharedConfig()" till the first attempt to access it?
Andrus
This archive was generated by hypermail 2.0.0 : Sat Jan 04 2003 - 20:02:51 EST