# JMS Transport

CXF provides a transport plugin that enables endpoints to use Java Message Service (JMS) queues and topics. CXF's JMS transport plugin uses the Java Naming and Directory Interface (JNDI) to locate and obtain references to the JMS provider that brokers for the JMS destinations. Once CXF has established a connection to a JMS provider, CXF supports the passing of messages packaged as either a JMS ObjectMessage or a JMS TextMessage. The JMS transport also supports the SOAP over JMS specification, see [SOAP over JMS 1.0 support](https://help.qlik.com/talend/en-US/esb-service-developer-guide/8.0/soap-over-jms-1.0-support).

Standard JMS transport configuration in CXF is done by defining a JMSConduit or JMSDestination, discussed below. There is however an alternative configuration option more conformant to Spring dependency injection, see [Using the JMSConfigFeature](https://help.qlik.com/talend/en-US/esb-service-developer-guide/8.0/using-jmsconfigfeature).

### In this section

* [JMS Namespaces](https://help.qlik.com/talend/en-US/esb-service-developer-guide/8.0/jms-namespaces)
* [Basic Endpoint Configuration](https://help.qlik.com/talend/en-US/esb-service-developer-guide/8.0/basic-endpoint-configuration)
* [Service Endpoint Configuration](https://help.qlik.com/talend/en-US/esb-service-developer-guide/8.0/service-endpoint-configuration)
* [JMS Runtime Configuration](https://help.qlik.com/talend/en-US/esb-service-developer-guide/8.0/jms-runtime-configuration)
* [SOAP over JMS 1.0 support](https://help.qlik.com/talend/en-US/esb-service-developer-guide/8.0/soap-over-jms-1.0-support)
* [Using the JMSConfigFeature](https://help.qlik.com/talend/en-US/esb-service-developer-guide/8.0/using-jmsconfigfeature)