Re: ParameterFilterInterceptor blocking

Gabe, as I already said, the idea was posted only because I have read
about wildcards (and because I haven't got time to think if * is
enough). I tend to agree with you that regexp may be more confusing.

./alex
--
.w( the_mindstorm )p.


On 6/12/06, Gabe <[email protected]> wrote:
>
> Well, besides the complexity of regular expressions, the tree method the ParameterFilterInterceptor uses currently is there to flexibly allow blocking and allowing of parameters so for example if you have:
>
> person.privateData as blocked but
> person.privateData.favoriteColor as allowed
>
> then only favoriteColor of the subproperties of privateData would be allowed through.
>
> This (as far as I know) can't be done using regular expressions consistently, because the way the above works is that the most specific propertyString (the one with the most dots) would be the one that determines permissions. Since regular expressions can be relatively vague, it would be difficult to determine which should determine the permissions.
>
> Gabe
>
> ----- Original Message ----
> From: Alexandru Popescu <[email protected]>
> To: [email protected]
> Sent: Saturday, June 10, 2006 12:28:22 PM
> Subject: Re: ParameterFilterInterceptor blocking
>
> I am wondering if at this point when speaking about wildcards,
> shouldn't we start looking directly to regexp support. Maybe it is
> overcomplex, but I thought I should ask :-).
>
> ./alex
> --
> .w( the_mindstorm )p.
>
>
> On 6/10/06, Jens <[email protected]> wrote:
> > Hi all,
> >
> > I revised ParameterFilterInterceptor to also filter by (nested) maps and collections. Wildcards for keys are supported as well.
> >
> > I attached the source und tests if someone is interested.
> >
> > Jens
> > ---------------------------------------------------------------------
> > Posted via Jive Forums
> > http://forums.opensymphony.com/thread.jspa?threadID=33614&messageID=65939#65939
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]