Donie,
perhaps you have some initialization code in the doFilter method? That would explain
why the first request does not do what it should but all the subsequent runs do.
Check that all initialization code is in the constructor and/or in init(FilterConfig)
method of your filter.
Christoph
On -1 xxx -1, Donie Kelly wrote:
From: Donie Kelly [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Filters in Tomcat 4.0
We have a filter attached to a servlet. Works fine except that on
initial startup of Tomcat the filter fails to run
: 01 November 2001 16:48
To: Tomcat Users List
Subject: Re: Filters in Tomcat 4.0
On -1 xxx -1, Donie Kelly wrote:
From: Donie Kelly [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Filters in Tomcat 4.0
We have a filter attached to a servlet
Craig McClanahan [EMAIL PROTECTED] wrote:
What does fails to run mean? Does it throw an exception?
It's difficult to respond to a question like this without a lot more
details.
---
This message has been posted through the
Donie Kelly [EMAIL PROTECTED] wrote:
Sorry Craig but I would have include more information if I had it...
Basically, no exceptions are thrown. It just acts as if the filter is not
there. Subsequent requests work fine.
What more can I say?
On Thu, 1 Nov 2001, Donie Kelly wrote:
Date: Thu, 1 Nov 2001 17:17:42 -
From: Donie Kelly [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Subject: RE: Filters in Tomcat 4.0
Sorry Craig but I would have include more
your not using a requestdispatcher.forward are you because this does not
trigger
the filters
- Original Message -
From: Donie Kelly [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Thursday, November 01, 2001 5:17 PM
Subject: RE: Filters in Tomcat 4.0
Sorry
