wt., 8 lis 2022 o 21:30 i...@flyingfischer.ch <i...@flyingfischer.ch> napisał(a): > I like the new feature to disable a specific interceptor within an > existing stack: > > https://issues.apache.org/jira/browse/WW-4173 > > But this change has consequences: > > This basically means that each custom implementation of the class > Interceptor, now needs to add a method isDisabled(ActionInvocation). I'm > unsure if this affects many applications, but at least this is not a > drop-in replacement. > > I am not suggesting the roll back of the function, just want to share > this as a feedback to think about.
Good point, this is a MINOR release so some breaking changes are allowed, but from the other side it would be better to have a smooth migration path for the users. Maybe I will add a "disableable interceptor" interface which will be used to check if a given interceptor should be disabled or not. Thanks for bringing this to my attention! 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
