Side note... My suggestion reminds me of an issue I had when I first learned Struts 2. I wished (and still wish) there was a way to specify the <interceptor> tag with an "exclude" or "disabled" attribute. I never liked the idea of having to rebuild my stack when all I wanted to do was take away an interceptor (or a few) from my default.
For me, if I want all unfiltered parameters, I would get rid of the filter -- not use the interface. That's my logic. On Wed, Aug 7, 2013 at 9:28 AM, Lukasz Lenart <lukaszlen...@apache.org>wrote: > 2013/8/7 Paul Benedict <pbened...@apache.org>: > > If you need unfiltered access, wouldn't the "correct" answer be to remove > > the filter on the action? > > I'm not sure if I get you right, but as I understand it's like that > right now - you cannot enable filtering on action without enabling > first filtering in interceptor. > > I see one disadvantage right now - it's more complicated to understand > for users. With "&&" in place, user can simple implement > ParameterNameAware and enable filtering per action - which is fine but > with time and additional "filters per actions" is going to be > complicated to understand what and why. > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- Cheers, Paul
