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 sending messages through (full-featured) STOMP brokers [SPR-10748] #15374

spring-projects-issues opened this issue Jul 16, 2013 · 1 comment
in: messaging in: web type: task


Copy link

@spring-projects-issues spring-projects-issues commented Jul 16, 2013

Rossen Stoyanchev opened SPR-10748 and commented

While #15371 will enable STOMP over WebSocket support in Spring applications, including an annotation-based programming model (#15373), full-featured message brokers (e.g. RabbitMQ, ActiveMQ, etc) with STOMP support have a wide range of features and many advantages.

This ticket will make it possible to use such brokers so that messages can be easily sent through them to subscribed clients from anywhere within the application.

Affects: 4.0 M1

This issue is a sub-task of #13994

Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jul 18, 2013

Rossen Stoyanchev commented

This is done by plugging in a "STOMP relay" MessageHandler which can delegate STOMP messages to the message broker where messages are either coming from clients connected to the application server (over WebSocket) or from within the application when some service needs to broadcast a message. Reversely the "STOMP relay" also read messages from the STOMP broker and sends them downstream to connected WebSocket clients.

@spring-projects-issues spring-projects-issues added in: messaging in: web type: task labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 4.0 M2 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: messaging in: web type: task
None yet

No branches or pull requests

2 participants