Configuración de STOMP con Spring
Configure el broker STOMP y los mecanismos de gestión de mensajes de Spring para una comunicación eficiente.
Configuración de STOMP con Spring es una lección gratuita de WebSockets & Real-Time Systems with Spring en CoddyKit. Esta es la lección 2 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de WebSockets & Real-Time Systems with Spring, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de WebSockets & Real-Time Systems with Spring incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
Spring & STOMP Configuration
Spring Boot makes building real-time applications with WebSockets and STOMP much easier. It provides powerful abstractions and auto-configuration to get you started quickly.
In this lesson, we'll learn how to set up Spring to handle STOMP messages. This involves configuring message brokers, defining endpoints, and establishing communication paths.
Activating STOMP with Spring
The first step is to enable Spring's WebSocket message broker capabilities. This is done with a single annotation: @EnableWebSocketMessageBroker.
- This annotation configures a message broker behind the scenes.
- It also sets up a Spring application context for handling STOMP messages.
- You'll typically place this on a configuration class.
Customizing Your STOMP Setup
To customize how Spring handles WebSocket and STOMP messages, you'll implement the WebSocketMessageBrokerConfigurer interface.
This interface provides methods that allow you to:
- Configure the message broker.
- Register STOMP endpoints.
- Add interceptors and customize message converters.
Setting Up the Message Broker
The message broker routes messages to their intended recipients. Spring provides a "simple" in-memory broker for basic needs.
You configure it in the configureMessageBroker method:
enableSimpleBroker(): Activates the in-memory broker.- Paths like
/topicare for public, publish-subscribe messages. - Paths like
/queueare for private, point-to-point messages.
Simple Broker Example
Here's how to set up the basic in-memory message broker with /topic and /queue destinations. This will allow clients to subscribe to public topics and send private messages.
package com.coddykit;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Configuration;
import org.springframework.messaging.simp.config.MessageBrokerRegistry;
import org.springframework.web.socket.config.annotation.EnableWebSocketMessageBroker;
import org.springframework.web.socket.config.annotation.WebSocketMessageBrokerConfigurer;
@SpringBootApplication
public class MainApplication {
public static void main(String[] args) {
SpringApplication.run(MainApplication.class, args);
}
}
@Configuration
@EnableWebSocketMessageBroker
class WebSocketConfig implements WebSocketMessageBrokerConfigurer {
@Override
public void configureMessageBroker(MessageBrokerRegistry config) {
config.enableSimpleBroker("/topic", "/queue");
}
// Endpoints will be added later
}Client-to-Server Paths
When a client sends a message to the server, it usually targets a specific server-side handler. We define a prefix for these messages using setApplicationDestinationPrefixes().
- For example, if the prefix is
/app, clients send messages to paths like/app/chat.sendMessage. - These messages are then routed to methods annotated with
@MessageMappingon the server.
App Destination Prefix Example
Let's update our configuration to include an application destination prefix. This tells Spring which messages are intended for server-side methods.
package com.coddykit;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Configuration;
import org.springframework.messaging.simp.config.MessageBrokerRegistry;
import org.springframework.web.socket.config.annotation.EnableWebSocketMessageBroker;
import org.springframework.web.socket.config.annotation.WebSocketMessageBrokerConfigurer;
@SpringBootApplication
public class MainApplication {
public static void main(String[] args) {
SpringApplication.run(MainApplication.class, args);
}
}
@Configuration
@EnableWebSocketMessageBroker
class WebSocketConfig implements WebSocketMessageBrokerConfigurer {
@Override
public void configureMessageBroker(MessageBrokerRegistry config) {
config.enableSimpleBroker("/topic", "/queue");
// Messages from clients for the server will start with /app
config.setApplicationDestinationPrefixes("/app");
}
// Endpoints will be added later
}Defining WebSocket Connection Point
Clients need a specific HTTP endpoint to initiate the WebSocket handshake. This is where they first connect before STOMP messaging begins.
You define this endpoint using registerStompEndpoints():
addEndpoint("/ws"): Makes the endpoint available athttp://localhost:8080/ws.withSockJS(): Enables SockJS fallback options for browsers that don't fully support WebSockets.
Complete STOMP Configuration
Here's the complete configuration class, combining the message broker setup, application destination prefix, and the STOMP endpoint registration. This is the foundation for your Spring STOMP application.
package com.coddykit;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Configuration;
import org.springframework.messaging.simp.config.MessageBrokerRegistry;
import org.springframework.web.socket.config.annotation.EnableWebSocketMessageBroker;
import org.springframework.web.socket.config.annotation.StompEndpointRegistry;
import org.springframework.web.socket.config.annotation.WebSocketMessageBrokerConfigurer;
@SpringBootApplication
public class MainApplication {
public static void main(String[] args) {
SpringApplication.run(MainApplication.class, args);
}
}
@Configuration
@EnableWebSocketMessageBroker
class WebSocketConfig implements WebSocketMessageBrokerConfigurer {
@Override
public void configureMessageBroker(MessageBrokerRegistry config) {
// Messages for client subscriptions (server to client)
config.enableSimpleBroker("/topic", "/queue");
// Messages from clients to server-side handlers
config.setApplicationDestinationPrefixes("/app");
}
@Override
public void registerStompEndpoints(StompEndpointRegistry registry) {
// The HTTP endpoint for WebSocket handshake
registry.addEndpoint("/ws").withSockJS();
}
}Configuration Check
You've learned about different prefixes in Spring STOMP configuration. It's crucial to understand their roles.
Summary of Configuration
You've successfully learned how to configure Spring for STOMP messaging! Here's a quick recap:
@EnableWebSocketMessageBroker: Activates WebSocket and STOMP support.WebSocketMessageBrokerConfigurer: Interface for customizing the setup.configureMessageBroker(): Sets up the message broker (e.g.,enableSimpleBroker("/topic", "/queue")) and application destination prefixes (e.g.,setApplicationDestinationPrefixes("/app")).registerStompEndpoints(): Defines the WebSocket handshake URL (e.g.,addEndpoint("/ws").withSockJS()).
These steps lay the foundation for building powerful real-time features with Spring and STOMP!
Preguntas frecuentes
¿La lección «Configuración de STOMP con Spring» es gratis?
Sí — el texto completo de «Configuración de STOMP con Spring» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de WebSockets & Real-Time Systems with Spring, actualiza a CoddyKit PRO. El curso de WebSockets & Real-Time Systems with Spring incluye 4 lecciones en total.
¿Qué aprenderé en «Configuración de STOMP con Spring»?
Configure el broker STOMP y los mecanismos de gestión de mensajes de Spring para una comunicación eficiente. Practicas WebSockets & Real-Time Systems with Spring con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar WebSockets & Real-Time Systems with Spring?
No se requiere experiencia previa. WebSockets & Real-Time Systems with Spring en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 2 de 4.
¿Cuánto tiempo toma la lección «Configuración de STOMP con Spring»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de WebSockets & Real-Time Systems with Spring?
Sí. Cada lección de WebSockets & Real-Time Systems with Spring incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Introducción al protocolo STOMP
- Configuración de STOMP con Spring
- Envío y recepción de mensajes STOMP
- Protección de endpoints STOMP con Spring Security