return acceptableName(name) || (parameterNameAware != null && parameterNameAware.acceptableParameterName(name) ^^ this part was changed from && to || - ParametersInterceptor, line 348
Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ 2013/8/6 Paul Benedict <pbened...@apache.org>: > Can you clarify what changed in 2.3.7? > > > On Tue, Aug 6, 2013 at 3:01 AM, Lukasz Lenart <lukaszlen...@apache.org>wrote: > >> 2013/8/2 Paul Benedict <pbened...@apache.org>: >> > If we changed ParameterNameAware interceptor so that it adheres to the >> > filtering of the interceptor, then I think we did the right thing. That >> > should be how the two work together. I would add how the two interact to >> > BOTH javadoc headers. >> >> I'm not sure if I get you right - the behaviour of these two changed >> sometime ago (as from 2.3.7 as I can recall). And my doubt is if it >> was a good move. Right now is clearer for me what are the >> responsibilities of these two. But maybe I'm wrong? >> >> >> 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org