The Spring Framework provides extensive support for integrating with messaging systems:
from simplified use of the JMS API using JmsTemplate to a complete infrastructure to
receive messages asynchronously. Spring AMQP provides a similar feature set for the
“Advanced Message Queuing Protocol” and Boot also provides auto-configuration options
for RabbitTemplate and RabbitMQ. There is also support for STOMP messaging natively
in Spring Websocket and Spring Boot has support for that through starters and a small
amount of auto configuration.
The javax.jms.ConnectionFactory interface provides a standard method of creating a
javax.jms.Connection for interacting with a JMS broker. Although Spring needs a
ConnectionFactory to work with JMS, you generally won’t need to use it directly yourself
and you can instead rely on higher level messaging abstractions (see the
relevant section of the Spring Framework reference
documentation for details).
Spring Boot can auto-configure a ConnectionFactory when it detects that HornetQ is
available on the classpath. If the broker is present, an embedded broker is started and
configured automatically (unless the mode property has been explicitly set). The supported
modes are: embedded (to make explicit that an embedded broker is required and should
lead to an error if the broker is not available in the classpath), and native to
connect to a broker using the the netty transport protocol. When the latter is
configured, Spring Boot configures a ConnectionFactory connecting to a broker running
on the local machine with the default settings.
![[Note]](images/note.png) | Note |
|---|---|
|
if you are using |
HornetQ configuration is controlled by external configuration properties in
spring.hornetq.*. For example, you might declare the following section in
application.properties:
spring.hornetq.mode=native spring.hornetq.host=192.168.1.210 spring.hornetq.port=9876
When embedding the broker, you can chose if you want to enable persistence, and the list
of destinations that should be made available. These can be specified as a comma separated
list to create them with the default options; or you can define bean(s) of type
org.hornetq.jms.server.config.JMSQueueConfiguration or
org.hornetq.jms.server.config.TopicConfiguration, for advanced queue and topic
configurations respectively.
See HornetQProperties
for more of the supported options.
No JNDI lookup is involved at all and destinations are resolved against their names, either using the “name” attribute in the HornetQ configuration or the names provided through configuration.
Spring Boot can also configure a ConnectionFactory when it detects that ActiveMQ is
available on the classpath. If the broker is present, an embedded broker is started and
configured automatically (as long as no broker URL is specified through configuration).
ActiveMQ configuration is controlled by external configuration properties in
spring.activemq.*. For example, you might declare the following section in
application.properties:
spring.activemq.broker-url=tcp://192.168.1.210:9876 spring.activemq.user=admin spring.activemq.password=secret
See ActiveMQProperties
for more of the supported options.
By default, ActiveMQ creates a destination if it does not exist yet, so destinations are resolved against their provided names.
Spring’s JmsTemplate is auto-configured and you can @Autowire it directly into your
own beans:
import org.springframework.beans.factory.annotation.Autowired; import org.springframework.jms.core.JmsTemplate; import org.springframework.stereotype.Component; @Component public class MyBean { private final JmsTemplate jmsTemplate; @Autowired public MyBean(JmsTemplate jmsTemplate) { this.jmsTemplate = jmsTemplate; } // ... }