Skip to content

SchedulingConfigurer and JmsListenerConfigurer should respect @Order [SPR-16090] #20639

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
spring-projects-issues opened this issue Oct 20, 2017 · 2 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) in: messaging Issues in messaging modules (jms, messaging) status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Yanming Zhou opened SPR-16090 and commented

I have multiple SchedulingConfigurer, I want control order of SchedulingConfigurer::configureTasks, currently they are not ordered by @Order, perhaps other XxxConfigurer have the same problem.


Affects: 4.3.12, 5.0 GA

Referenced from: commits 40f3fb2, d1fac36

Backported to: 4.3.13

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Indeed, for other such delegates we already support @Order, just @SchedulingConfigurer and JmsListenerConfigurer are missing.

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

This is fixed in master for 5.0.1 now and will be backported to 4.3.13 by Monday.

@spring-projects-issues spring-projects-issues added in: messaging Issues in messaging modules (jms, messaging) status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement in: core Issues in core modules (aop, beans, core, context, expression) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 5.0.1 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) in: messaging Issues in messaging modules (jms, messaging) status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants