Thanks Musachy. I've been looking at the src for
ParameterRemoverInterceptor and it looks like I can easily modify it to
meet my needs. I just wanted to insure that I was approaching the
problem in a "S2 way" since it would seem to be a common problem.
--john
Musachy Barroso wrote:
By the
By the way, the Parameters interceptor uses the "wrap" parameters map,
so removing them from there would work.
musachy
On Wed, Jan 7, 2009 at 11:52 AM, Musachy Barroso wrote:
> Parameters interceptor can ignore parameters based on the name, but
> not on value. You could extend the parameters int
Parameters interceptor can ignore parameters based on the name, but
not on value. You could extend the parameters interceptor and check
for values before binding, or what Dave suggested. A tip there, if you
go with Dave's suggestion, have into account that the parameters in
the context is a new map
Thanks for your prompt response Dave. So an custom interceptor before
Params could modify the servlet request and Params interceptor would
never seem them? Is there not a way to configure the existing Params
interceptor to ignore any request parameters w/ a value of empty string?
The problem
John Cartwright wrote:
Can someone provide a recommendation for removing empty request
parameters before the Params interceptor sees them? Can Params
interceptor simply be configured to ignore request parameters with no
value?
I'd probably just create a quick interceptor to do that, if that'
Hello All,
Can someone provide a recommendation for removing empty request
parameters before the Params interceptor sees them? Can Params
interceptor simply be configured to ignore request parameters with no value?
Thanks!
--john
---
6 matches
Mail list logo
