That's certainly one option, and has serious advantages with respect to
"just working". In the meantime, not using BasicServletConfiguration
and just putting the map xml files on the class path works well.
In some respects it's kind of nasty for the servlet container to do
stuff to sessions from a servlet before initializing at least one
instance of the servlet. But I don't think the servlet spec says
anything about that, so we're out of luck.
I'll look into deferring getting the parent of the DataContext until
needed.
Craig
On Sun, 2003-01-05 at 14:03, Andrus wrote:
> 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 : Mon Jan 06 2003 - 17:35:11 EST