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

Add support for Component-level EventListener registrations between Components [SPR-17251] #21784

spring-projects-issues opened this issue Sep 6, 2018 · 0 comments
in: core status: waiting-for-triage


Copy link

@spring-projects-issues spring-projects-issues commented Sep 6, 2018

Jeffrey Schultz opened SPR-17251 and commented

I am interested in having the ability to use either XML or Java Config to register implementations of the EventListener with components that provide addXXXListener(XXXListener) and removeXXXListener(XXXListener) methods. The EventListener registrations should follow the bean lifecycle and unregister themselves with the event source when being disposed.

I know that a custom bean could be developed that can handle invocations of the addXXXListener/removeXXXListener methods and pass a reference of the EventListener object, but would like to see what the Spring team thinks of this feature.

Even if you decide this doesn't fall inline with the overall direction of Spring, could you at least provide some pointers that I could follow to investigate its implementation? The Application Event support is great, but I am looking for a more point to point way of handling messaging within applications. I could take the Spring Integration approach, but I feel this would be overkill for this particular implementation.

No further details from SPR-17251

@spring-projects-issues spring-projects-issues added status: waiting-for-triage type: enhancement in: core and removed type: enhancement labels Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: core status: waiting-for-triage
None yet

No branches or pull requests

1 participant