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

JmsListenerEndpointRegistry - expose @JmsListener ids [SPR-13633] #18211

Closed
spring-projects-issues opened this issue Nov 2, 2015 · 2 comments
Assignees
Labels
in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Nov 2, 2015

Gary Russell opened SPR-13633 and commented

The JmsListenerEndpointRegistry exposes a collection of containers as well as the ability to get a reference to each container by id, but there is no mechanism to get the id s.

Consider exposing (unmodifiable) the whole map, or the map's keySet.


Affects: 4.2.2

Reference URL: http://stackoverflow.com/questions/33475344/displaying-the-listeners-and-their-status-in-my-application

Issue Links:

  • AMQP-544 RabbitListenerEndpointRegistry - expose @RabbitListener ids ("is depended on by")
@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Nov 2, 2015

Stéphane Nicoll commented

Thanks for the feedback. I've added a getListenerContainerIds() on the registry. Gary, you may want to apply the same change to the Rabbit one.

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Nov 2, 2015

Gary Russell commented

Thanks, Stéphane Nicoll yes; I Iinked a JIRA issue dependent on this so we provide a solution there the same way.

@spring-projects-issues spring-projects-issues added in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 4.2.3 milestone Jan 11, 2019
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: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants