Michal Vavřík
Michal Vavřík
cc @sberyozkin @geoand
@sberyozkin yes, it would be possible and I actually already had it in progress... I stopped as the binding is between annotation (and its values) and the interceptor, not between...
My point is that the check can only be removed on "method invocation" scope, not request scope as you need nested CDI beans to be able to perform its own...
Sure, I'll find a build time solution as discussed. I changed PR to draft then.
@sberyozkin ready for review
Sure, conflict resolved.
but we should keep the annotation in place as the developers will count on it. what if they will bind their own interceptors to it. It's dodgy. Or did I...
In short - annotation transformer solution: one annotation instance - possibly many interceptors -> you remove it -> you loose all the bindings this pr: one annotation instance - possibly...
there is the test from which the behavior should be clear - `MethodInterceptorBindingFilterTest`
I think this solution was isolated to repeated checks while other assumes we know what developers do (it could be breaking change theoretically, right?). I accept that you agreed it's...