-
Notifications
You must be signed in to change notification settings - Fork 881
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix spring-integration context leak #4673
Fix spring-integration context leak #4673
Conversation
// | ||
// there's an option for this class to implement VetoCapableInterceptor and prevent itself | ||
// from being registered if it's already registered, but the VetoCapableInterceptor interface | ||
// broke backwards compatibility in 5.2.0, and the version prior to 5.2.0 takes a parameter | ||
// of type ChannelInterceptorAware which doesn't exist after 5.2.0, and while it's possible to | ||
// implement both at the same time (since we compile using 4.1.0), muzzle doesn't like the | ||
// missing class type when running testLatestDeps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can remove this part if it seems too much, I just didn't want others to go down this road, at least without knowing the pitfalls ahead of time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is good description 👍
// | ||
// there's an option for this class to implement VetoCapableInterceptor and prevent itself | ||
// from being registered if it's already registered, but the VetoCapableInterceptor interface | ||
// broke backwards compatibility in 5.2.0, and the version prior to 5.2.0 takes a parameter | ||
// of type ChannelInterceptorAware which doesn't exist after 5.2.0, and while it's possible to | ||
// implement both at the same time (since we compile using 4.1.0), muzzle doesn't like the | ||
// missing class type when running testLatestDeps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is good description 👍
No description provided.