Skip to content
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

ApplicationListener notifications to reflect Ordered interface [SPR-5240] #9914

Closed
spring-projects-issues opened this issue Oct 23, 2008 · 0 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Ben Alex opened SPR-5240 and commented

At present Spring Framework offers no guarantees as to the order in which ApplicationEvent messages will be delivered to ApplicationListener instances.

It would be desirable for ApplicationListener instances that also implement Spring's Ordered interface to be notified of ApplicationEvents in the requested order. This would permit more complex use cases to be addressed by the ApplicationListener capability, plus provide consistency with other parts of Spring Framework which rely on Ordered.

As an interim solution, a user-provided OrderedApplicationEventMulticaster can be registered by AbstractApplicationContext. Nevertheless, it would be desirable for Spring Framework to provide this capability as part of its core functionality.


No further details from SPR-5240

@spring-projects-issues spring-projects-issues added 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 3.0 M2 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) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants