Skip to content

setTaskScheduler in StompBrokerRelayRegistration breaks chaining #26049

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

Closed
rstoyanchev opened this issue Nov 9, 2020 · 1 comment
Closed
Assignees
Labels
in: messaging Issues in messaging modules (jms, messaging) type: bug A general bug
Milestone

Comments

@rstoyanchev
Copy link
Contributor

The recently added setTaskScheduler returns void instead of StompBrokerRelayRegistration and so does setTcpClient which was added longer ago might be worth addressing.

Originally reported in #22822 (comment).

@rstoyanchev rstoyanchev added in: messaging Issues in messaging modules (jms, messaging) type: bug A general bug labels Nov 9, 2020
@rstoyanchev rstoyanchev added this to the 5.3.1 milestone Nov 9, 2020
@rstoyanchev rstoyanchev self-assigned this Nov 9, 2020
@jhoeller
Copy link
Contributor

jhoeller commented Nov 9, 2020

Let's address both in 5.3.1 indeed. This is still early enough, in particular since the change is source compatible (just not binary compatible), so fresh application builds won't see any regression.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: messaging Issues in messaging modules (jms, messaging) type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants