DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3733>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3733
session serialization problem
------- Additional Comments From [EMAIL PROTECTED] 2001-09-20 01:01 -------
Thanks for the analysis. The lifecycle is relatively easy to figure out by
looking at StandardContext.start.
I'm -1 for the patch. We can't init or load a servlet before the supporting
components (logger, context, servlet context) are created and / or started.
This is not a spec issue since the spec doesn't say anything about this.
As you point out, it's a special case anyway, since only init on startup
servlets can have a chance to behave like that.
I also have no idea how it can be fixed, except if we change the initialization
of the manager (and load the serialized session in a post-start method).
So I vote WONTFIX (I'll let Craig close the bug if he approves), although it's
more CANTFIX than WONTFIX.
