Mark Galbreath wrote:
[Re. overriding request parameters using request wrappers]
> This is actually pretty cool in concept! Have you used it?
Yes, it shows up in two slightly different formats in my current
project. I extend HttpServletRequestWrapper with a custom implementation
partly in order
>The only way I could see, using the API, was to extend
>HttpServletRequestWrapper and override the parameter methods. If
>you know that your added parameter name won't ever conflict with
>any of the original request parameters (or any added during an
>include or forward), I think it can be fairly
This is actually pretty cool in concept! Have you used it?
Cheers!
Mark
- Original Message -
From: "Gennis Emerson" <[EMAIL PROTECTED]>
Sent: Wednesday, October 17, 2001 7:19 PM
> You might be able to do something container-specific - cast the
> ServletRequest to some container implem
Tim Panton wrote:
>
> I am trying to use the 'new' filter api to add a parameter to a
> request before a servlet is invoked. My first try involved
> calling getParameterMap()and doing a put() into it. It seems
> that map is locked readonly. So now I'm looking at
> HttpRequestWrapper but to use t
I am trying to use the 'new' filter api to add a parameter to a request before a
servlet is invoked.
My first try involved calling getParameterMap()and doing a put() into it. It seems
that map is locked readonly.
So now I'm looking at HttpRequestWrapper but to use that I think I will have to
em
