"I've got a fever... and the only cure is more cowbell!"
LOL. :-D
"Tim Funk" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> You won't be able to get the servlet reference. A possibility is to define
> the filter multiple times with different parameters. For example, here is
the
>
Howdy,
>> You won't be able to get the servlet reference. A possibility is to
>> define the filter multiple times with different parameters. For
example,
>> here is the same class name defined 4 times as 4 different filters.
>
>Good idea. Thanks for the helpful response. Since I can't get a
>re
Tim Funk wrote:
You won't be able to get the servlet reference. A possibility is to
define the filter multiple times with different parameters. For example,
here is the same class name defined 4 times as 4 different filters.
Good idea. Thanks for the helpful response. Since I can't get a
refer
Howdy,
>I don't think this is possible, but I'm giving it a shot anyway. :)
>
>I'd like to get ahold of a servlet reference from within a filter. Is
>there a way?
Your intuition is right in this case -- the above is impossible (using
only the Servlet APIs -- it IS possible [though not trivial]
You won't be able to get the servlet reference. A possibility is to define
the filter multiple times with different parameters. For example, here is the
same class name defined 4 times as 4 different filters.
filter1
more.Cowbell
my
attribute
filter2
more.Cowbell
fil
Hello,
I don't think this is possible, but I'm giving it a shot anyway. :)
I'd like to get ahold of a servlet reference from within a filter. Is
there a way?
I have a filter that creates objects and places them within the request
scope, but it does it differently for each end-result servlet.
