anchor.diff:      </snapshots>
     </repository>
   </repositories>
  ---------------------------------------------------------------------------
  -
  -### Default payload type
  -
  - 
  -
  -By default Camel Paho component operates on the binary payloads
  -extracted out of (or put into) the MQTT message:
  -
  -[source,java]
  ----------------------------------------------------------------------
  -// 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 link:type-converter.html[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):
  -
  - 
  -
  -[source,java]
  ---------------------------------------------------------------------------
  -// Receive payload
  -String payload = consumerTemplate.receiveBody("paho:topic", String.class);
  - 
  -// Send payload
  -String payload = "message";
  -producerTemplate.sendBody("paho:topic", payload);
  ---------------------------------------------------------------------------
  -
  -### Paho Options
  +----
   
   
  +=== URI format
  +
  +[source]
  +----
  +paho:topic[?options]
  +----
  +
  +Where *topic* is the name of the topic.
  +
  +
  +=== Options
   
   // component options: START
   The Paho component supports 4 options which are listed below.
  
positive.code: most popular MQTT libraries, so if you would like to integrate it with
  your Java project - Camel Paho connector is a way to go.
  
  ### URI format
  
  [source,java]
  ------------------------
  paho:queueName[?options]
  ------------------------
  
  For example the following snippet reads messages from the MQTT broker
  installed on the same host as the Camel router:
  
  [source,java]
  ------------------------
  from("paho:some/queue").
    to("mock:test");
  ------------------------
  
  While the snippet below sends message to the MQTT broker:
  
  [source,java]
  -------------------------------
  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: 
  
   
  
  [source,java]
  -------------------------------------------------------------
  from("paho:some/queue?brokerUrl=tcp://iot.eclipse.org:1883").
    to("mock:test");
  -------------------------------------------------------------
  
   
  
  ### Adding the component to the project
  
  Maven users will need to add the following dependency to their `pom.xml`
  for this component:
  
  [source,xml]
  ------------------------------------------------------------
  <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:
  
  [source,xml]
  --------------------------------------------------------------------------
  <repositories>
    <repository>
      <id>eclipse-paho</id>
  
negative.code: // endpoint options: END
  
  
  === Headers
  
  The following headers are recognized by the Paho component:
  
  [width="100%",cols="10%,10%,10%,10%,60%",options="header",]
  |===
  |Header |Java constant |Endpoint type |Value type |Description
  
  |CamelMqttTopic |PahoConstants.MQTT_TOPIC |Consumer |String |The name of the topic
  |===
  
  
  === Default payload type
  
  By default Camel Paho component operates on the binary payloads
  extracted out of (or put into) the MQTT message:
  
  [source,java]
  ----
  // 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 link:type-converter.html[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):
  
  [source,java]
  ----
  // Receive payload
  String payload = consumerTemplate.receiveBody("paho:topic", String.class);
  
  // Send payload
  String payload = "message";
  producerTemplate.sendBody("paho:topic", payload);
  ----
  
  
  === Samples
  
  For example the following snippet reads messages from the MQTT broker
  installed on the same host as the Camel router:
  
  [source,java]
  ----
  from("paho:some/queue")
      .to("mock:test");
  ----
  
  While the snippet below sends message to the MQTT broker:
  
  [source,java]
  ----
  from("direct:test")
      .to("paho:some/target/queue");
  ----
  
  For example this is how to read messages from the remote MQTT broker: 
  
  [source]
  ----
  from("paho:some/queue?brokerUrl=tcp://iot.eclipse.org:1883")
      .to("mock:test");
  ----
  
  