Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
SEC-1897: Remove raw types from AbstractAccessDecisionManager implementations #2124
AbstractAccessDecisionManager, AffirmativeBased, ConsensusBased, and UnanimousBased should use generic types for AccessDecisionVoter
h1. Original Description
After upgrading from Spring Security 3.0.6 to 3.1.0, I can no longer construct an
My old code using the default constructor and
The new constructor
Rob Winch said:
This seems more like an improvement rather than a bug as it is not impacting an behavior. Unfortunately updating it now would cause incompatibilities. For example, the following works right now but would not after the proposed changes:
With the above in mind, this is going to be pushed to the 3.2.0.M1 release as an improvement.
Out of curiosity is there a reason you are programmatically accessing AffirmativeBased? I would expect most would create using Spring Configuration. This is more of a curiosity factor to get an understanding of how things are being used.
Harald Wellmann said:
Spring Configuration is no longer synonymous with XML. We're now using Spring 3.1 Java configuration without any XML definitions throughout our projects, and it is rather sad that Java Config still seems to be a second-class citizen for Spring Security.