Log4J. Haven't tried anything else, since Log4J works and is very adaptable
by just altering configuration (no code changes).
- Tatu V.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] Behalf Of Bill Barker
Sent: 21. marraskuuta 2003 8:36
To: [EMAIL PROTECTED]
Subject: Re:
You might be able to use HttpSessionAttributeListener
...or HttpSessionBindingListener. The container calls the
valueUnbound(HttpSessionBindingEvent event) when the object is removed from
the session (e.g. when session is destroyed). I am using this one =)
- Tatu V.
Peter Maas wrote:
What
Hello,
We have a development environment where each developer has a separate Tomcat
instance to play with. Each Tomcat should listen in it's port for requests
coming from the Apache front-end. The mappings for each user's Tomcat should
be based on the request uri, i.e.
If I test this code from the Linux Tomcat Server (just typing
http://myserver/session.jsp ) jsessionid doesn´t change each
time a refresh
the page...
Isn't it the way it should work ? Keeping a single session
between requests ?
I agree.
And the link doesnt show jsessionid either, as
Hello
I have two questions about Tomcat and connnectors. The front-end web server
is Apache.
1.) When using Tomcat 4.1.24 and the Warp- connector, the creation of the
servlet and the call to init() happens two times (even the class loading).
Normally this would not be a great problem, but in my
Hello
I have two questions about Tomcat and connnectors. The front-end web server
is Apache.
1.) When using Tomcat 4.1.24 and the Warp- connector, the creation of the
servlet and the call to init() happens two times (even the class loading).
Normally this would not be a great problem, but in my
