Re-use the instance of PreInvocationAuthorizationAdvice in the GlobalMethodSecurityConfiguration

Expected Behavior

If I create my own factory method, instantiating PreInvocationAuthorizationAdvice, which will be used in the GlobalMethodSecurityConfiguration.accessDecisionManager(), or at least if I override the preInvocationAuthorizationAdvice(), the result to be used when constructing the access decision manager.

Current Behavior

Currently, the accessDecisionManager() constructs its own instance of PreInvocationAuthorizationAdvice(ExpressionBasedPreInvocationAdvice), which is not even taken from its factory method PreInvocationAuthorizationAdvice preInvocationAuthorizationAdvice()
In fact, I currently don't see the point of this factory method.

Context

In this way, I could inject my custom implementation of PreInvocationAuthorizationAdvice. Now if I want to extend the behavior accessDecisionManager(), I have to copy/paste the original code and customize, while in my case, it's sufficient if I extend the ExpressionBasedPreInvocationAdvice class and use it in a factory method.

Start with GlobalMethodSecurityConfiguration.accessDecisionManager() and preInvocationAuthorizationAdvice(), then inspect how PreInvocationAuthorizationAdvice is instantiated. The change is done when the access decision manager uses the factory method's result, including an overridden or custom implementation, instead of constructing its own instance.