Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
From: =?us-ascii?Q?Michael_Sudkamp?= <michael.suedkamp@docware.de>
To: "'Tomcat Users List'" <tomcat-user@jakarta.apache.org>
Subject: AW: sessionS info persistence when restart Tomcat
Date: Fri, 10 Dec 2004 10:38:29 +0100
Message-ID: <002b01c4de9c$02597ca0$720a0a0a@Fuerth.docware.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <000001c4de99$64e75020$0201a8c0@sjklaptop>

Hi Steve,

I am jumping into this discussion rather late and I am probably not going to
answer any of your questions. I just would like to add that I examined the
session persistence and listeners topic also very deep some weeks ago. After
all I found it not really practical because the servlet 2.3/2.4 spec is not
clear enough about how the sequence the variuos listeners should be called
by the container. In my case it was vital that the contextInitialized()
method must be called before sessionActivated(). This because in
sessionActivated we restore our transient members and for this WE need a
fully initialized ServletContext (and preferably also the init() methods of
preloaded servlets have been called).

Yoav confirmed me that it is a spec problem and encouraged me to contact the
spec group, what I did. They told me that  they will address the problem in
a next spec.

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org