-
Notifications
You must be signed in to change notification settings - Fork 604
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
AbstractMessageChannelBinder
should also handle DisposableBean
s
#953
Milestone
Comments
mbogoevici
added a commit
to mbogoevici/spring-cloud-stream
that referenced
this issue
May 11, 2017
- If the endpoints produced by `createConsumer` or `createProducers` and Spring `DisposableBean` instances then call `Destroy` on unbind. Fix spring-cloud#953
artembilan
pushed a commit
that referenced
this issue
May 12, 2017
- If the endpoints produced by `createConsumer` or `createProducers` and Spring `DisposableBean` instances then call `Destroy` on unbind. Fix #953
mbogoevici
added a commit
that referenced
this issue
May 17, 2017
- If the endpoints produced by `createConsumer` or `createProducers` and Spring `DisposableBean` instances then call `Destroy` on unbind. Fix #953
mbogoevici
added a commit
that referenced
this issue
May 17, 2017
- If the endpoints produced by `createConsumer` or `createProducers` and Spring `DisposableBean` instances then call `Destroy` on unbind. Fix #953
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See the related issue reported in the JMS binder spring-attic/spring-cloud-stream-binder-jms#27.
If the
lifecycle
object passed to theBinding
is aDisposableBean
we can clear it during unbinding.The text was updated successfully, but these errors were encountered: