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.
Best regards
Markus
Am 08.11.22 um 16:13 schrieb Lukasz Lenart:
Hello,
This is the first minor version of Struts 6.x series. Please take the
time and test the bits - any help is appreciated. Please report any
problems you will spot.
Here are the changes from the previous 6.0.3 version:
https://github.com/apache/struts/releases/tag/STRUTS_6_1_0
Staging Maven repo
https://repository.apache.org/content/groups/staging/
Standalone artifacts
https://dist.apache.org/repos/dist/dev/struts/6.1.0/
Release notes
https://cwiki.apache.org/confluence/display/WW/Version+Notes+6.1.0
Kind regards
--
Łukasz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
