Caldarale, Charles R wrote:
>> From: Ken Bowen [mailto:kbo...@als.com]
>> Subject: Re: [Solved+Question]SessionListener not being invoked
>>
>> This project has been sputtering along for a fair number of
>> years, and my context.xml almost certainly began
> From: Ken Bowen [mailto:kbo...@als.com]
> Subject: Re: [Solved+Question]SessionListener not being invoked
>
> This project has been sputtering along for a fair number of
> years, and my context.xml almost certainly began life inside
> conf/server.xml.
Once upon a time, I bel
e now.
Cheers,
Ken
On Dec 3, 2009, at 11:02 PM, Caldarale, Charles R wrote:
From: Ken Bowen [mailto:kbo...@als.com]
Subject: Re: [Solved+Question]SessionListener not being invoked
One question: What does it mean to say "the path attribute is not
allowed"? (My context.xml is in META-INF
> From: Ken Bowen [mailto:kbo...@als.com]
> Subject: Re: [Solved+Question]SessionListener not being invoked
>
> One question: What does it mean to say "the path attribute is not
> allowed"? (My context.xml is in META-INF). Should I be seeing a
> complain
..@als.com]
Subject: Re: [Solved+Question]SessionListener not being invoked
Note that the path attribute is not allowed (if your
element is in a standard location), and the debug attribute hasn't
been used in some years. Use conf/logging.properties to set the
desired logging level.
> From: Ken Bowen [mailto:kbo...@als.com]
> Subject: Re: [Solved+Question]SessionListener not being invoked
>
>
Note that the path attribute is not allowed (if your element is in a
standard location), and the debug attribute hasn't been used in some years.
Use conf/logging.
Chris,
This seems to be the source of the problem. Just to be sure I'm on
target, I'll run through
a few details, and then I have a follow-on question. My tomcat-6.0.20/
conf/context.xml is the
one shipped with the download:
WEB-INF/web.xml
And the app-
Chris,
That's a point I hadn't thought of. I'll explore it.
Thanks,
Ken
On Dec 2, 2009, at 12:31 PM, Christopher Schultz wrote:
That might be possible, even after a webapp/container restart if you
have Tomcat configured to persist sessions across such restarts (which
is the default configurat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken,
On 12/1/2009 2:36 PM, Ken Bowen wrote:
> No, we always create a session (or want to).
> The only <%@ in the welcome page are
>
> <%@ page contentType="text/html;charset=UTF-8" language="java" %>
> <%@ taglib uri="http://tiles.apache.org/tags-til
No, we always create a session (or want to).
The only <%@ in the welcome page are
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<%@ taglib uri="http://tiles.apache.org/tags-tiles"; prefix="tiles" %>
<%@ taglib uri="http://java.sun.com/jstl/core_rt"; prefix="c" %>
As I mentio
> From: Ken Bowen [mailto:kbo...@als.com]
> Subject: SessionListener not being invoked
>
> I have a SessionListener which is not being invoked when I connect to
> the webapp, and I don't understand why.
Most likely because your webapp didn't choose to create a session.
My setup: Mac OS X 10.5.8, Tomcat/6.0.20[from apache], java version
"1.6.0_15"
I'm starting Tomcat with ~bin/startup.sh.
I have a SessionListener which is not being invoked when I connect to
the webapp,
and I don't understand why.
The SessionListener works correctly in a a slight variatio
12 matches
Mail list logo
