2013/5/17 JOSE L MARTINEZ-AVIAL :
> Well, the only part that could break backward compatibility is the idea of
> removing filter of cookies by value. But the CookieProviderInterceptor and
> the idea of being able to OGNL-value the accepted cookie names should not
> break anything.
But I think we a
Well, the only part that could break backward compatibility is the idea of
removing filter of cookies by value. But the CookieProviderInterceptor and
the idea of being able to OGNL-value the accepted cookie names should not
break anything.
2013/5/16 Lukasz Lenart
> If this is gonna break backwa
If this is gonna break backward compatibility, please register an
issue with JIRA and we will introduce the change with Struts 2.5/3
version.
Regards
--
Ćukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/4/4 Maurizio Cucchiara :
>> My proposal would
>> be to simplify the interceptor in two
> My proposal would
> be to simplify the interceptor in two ways:
> 1) Remove the filter by cookie value: I don't know under which
> circumstances that could be useful
I'm not able to identify those circumstances, but AFAIU that filter is
harmless, if you don't define a cookie value, struts will ne
or, you have to implement
CookieAware interface.
>
> The cookie interceptor does not make sense at a general level so far.
> You need to have x, y, z in your actions, and so all your actions would
> need to provide these setters.
IMHO, this is the struts way, and it's simila
>> Porfavor..no altere ni interrumpir esta communicacion...Gracias
>>
>>
>>
>>
>> > Date: Wed, 3 Apr 2013 16:30:19 -0400
>> > Subject: Re: Cookie Interceptor
>> > From: jlm...@gmail.com
>&
ile JIRA ?
> https://issues.apache.org/jira/browse/WW
>
>
> Saludos Cordiales desde EEUU
> Martin
> __
> Porfavor..no altere ni interrumpir esta communicacion...Gracias
>
>
>
>
> > Date: Wed, 3 Apr 2013 16:30:19 -0400
> > Su
__
Porfavor..no altere ni interrumpir esta communicacion...Gracias
> Date: Wed, 3 Apr 2013 16:30:19 -0400
> Subject: Re: Cookie Interceptor
> From: jlm...@gmail.com
> To: dev@struts.apache.org
>
> I use CookieAware in Struts 2.2.3, and I don
ected to the action.
>
> The cookie interceptor does not make sense at a general level so far.
> You need to have x, y, z in your actions, and so all your actions would
> need to provide these setters. Also "*" is risky: if you set a cookie for
> use in
> Action A it might
Hi,
the CookieInterceptor currently looks for all available cookies. Lets say there
are cookies x, y, z. Now it would call setX, setY, setZ on the action.
In addition it creates a cookie-map which is then injected to the action.
The cookie interceptor does not make sense at a general level so
10 matches
Mail list logo