paho:queueName[?options]

For example the following snippet reads messages from the MQTT broker installed on the same host as the Camel router:

from("paho:some/queue").
  to("mock:test");

While the snippet below sends message to the MQTT broker:

from("direct:test").
  to("paho:some/target/queue");

You can append query options to the URI in the following format: ?option=value&option=value&…​ . For example this is how to read messages from the remote MQTT broker: 

from("paho:some/queue?brokerUrl=tcp://iot.eclipse.org:1883").
  to("mock:test");

Maven users will need to add the following dependency to their pom.xml for this component:

<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-paho</artifactId>
    <version>x.y.z</version>
    <!-- use the same version as your Camel core version -->
</dependency>

Keep in mind that Paho artifacts are not hosted in the Maven Central, so you need to add Eclipse Paho repository to your POM xml file:

<repositories>
  <repository>
    <id>eclipse-paho</id>
    <url>https://repo.eclipse.org/content/repositories/paho-releases</url>
    <snapshots>
      <enabled>false</enabled>
    </snapshots>
  </repository>
</repositories>

By default Camel Paho component operates on the binary payloads extracted out of (or put into) the MQTT message:

// Receive payload
byte[] payload = (byte[]) consumerTemplate.receiveBody("paho:topic");
 
// Send payload
byte[] payload = "message".getBytes();
producerTemplate.sendBody("paho:topic", payload);

But of course Camel build-in type conversion API can perform the automatic data type transformations for you. In the example below Camel automatically converts binary payload into String (and conversely):

// Receive payload
String payload = consumerTemplate.receiveBody("paho:topic", String.class);
 
// Send payload
String payload = "message";
producerTemplate.sendBody("paho:topic", payload);

The Paho component supports 3 options which are listed below.

{% raw %}

{% endraw %}

The Paho component supports 12 endpoint options which are listed below:

{% raw %}

{% endraw %}

The following headers are recognized by the Paho component: