The xmpp: component implements an XMPP (Jabber) transport.
Maven users will need to add the following dependency to their pom.xml
for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-xmpp</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>xmpp://[login@]hostname[:port][/participant][?Options]
The component supports both room based and private person-person conversations. The component supports both producer and consumer (you can get messages from XMPP or send messages to XMPP). Consumer mode supports rooms starting.
You can append query options to the URI in the following format,
?option=value&option=value&…
The XMPP component has no options.
The XMPP component supports 21 endpoint options which are listed below:
{% raw %}
| Name | Group | Default | Java Type | Description |
|---|---|---|---|---|
host | common |
| Required Hostname for the chat server | |
port | common |
| Required Port number for the chat server | |
participant | common |
| JID (Jabber ID) of person to receive messages. room parameter has precedence over participant. | |
login | common |
|
| Whether to login the user. |
nickname | common |
| Use nickname when joining room. If room is specified and nickname is not user will be used for the nickname. | |
pubsub | common |
|
| Accept pubsub packets on input default is false |
room | common |
| If this option is specified the component will connect to MUC (Multi User Chat). Usually the domain name for MUC is different from the login domain. For example if you are supermanjabber.org and want to join the krypton room then the room URL is kryptonconference.jabber.org. Note the conference part. It is not a requirement to provide the full room JID. If the room parameter does not contain the symbol the domain part will be discovered and added by Camel | |
serviceName | common |
| The name of the service you are connecting to. For Google Talk this would be gmail.com. | |
testConnectionOnStartup | common |
|
| Specifies whether to test the connection on startup. This is used to ensure that the XMPP client has a valid connection to the XMPP server when the route starts. Camel throws an exception on startup if a connection cannot be established. When this option is set to false Camel will attempt to establish a lazy connection when needed by a producer and will poll for a consumer connection until the connection is established. Default is true. |
createAccount | common (advanced) |
|
| If true an attempt to create an account will be made. Default is false. |
resource | common (advanced) |
|
| XMPP resource. The default is Camel. |
bridgeErrorHandler | consumer |
|
| Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored. |
connectionPollDelay | consumer |
|
| The amount of time in seconds between polls (in seconds) to verify the health of the XMPP connection or between attempts to establish an initial consumer connection. Camel will try to re-establish a connection if it has become inactive. Default is 10 seconds. |
doc | consumer |
|
| Set a doc header on the IN message containing a Document form of the incoming packet; default is true if presence or pubsub are true otherwise false |
exceptionHandler | consumer (advanced) |
| To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored. | |
exchangePattern | consumer (advanced) |
| Sets the exchange pattern when the consumer creates an exchange. | |
connectionConfig | advanced |
| To use an existing connection configuration | |
synchronous | advanced |
|
| Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported). |
headerFilterStrategy | filter |
| To use a custom HeaderFilterStrategy to filter header to and from Camel message. | |
password | security |
| Password for login | |
user | security |
| User name (without server name). If not specified anonymous login will be attempted. |
{% endraw %}
Camel sets the message IN headers as properties on the XMPP message. You
can configure a HeaderFilterStategy if you need custom filtering of
headers.
The Subject and Language of the XMPP message are also set if they
are provided as IN headers.
User superman to join room krypton at jabber server with password,
secret:
xmpp://superman@jabber.org/?room=krypton@conference.jabber.org&password=secret
User superman to send messages to joker:
xmpp://superman@jabber.org/joker@jabber.org?password=secret
Routing example in Java:
from("timer://kickoff?period=10000").
setBody(constant("I will win!\n Your Superman.")).
to("xmpp://superman@jabber.org/joker@jabber.org?password=secret");Consumer configuration, which writes all messages from joker into the
queue, evil.talk.
from("xmpp://superman@jabber.org/joker@jabber.org?password=secret").
to("activemq:evil.talk");Consumer configuration, which listens to room messages:
from("xmpp://superman@jabber.org/?password=secret&room=krypton@conference.jabber.org").
to("activemq:krypton.talk");Room in short notation (no domain part):
from("xmpp://superman@jabber.org/?password=secret&room=krypton").
to("activemq:krypton.talk");When connecting to the Google Chat service, you’ll need to specify the
serviceName as well as your credentials:
from("direct:start").
to("xmpp://talk.google.com:5222/touser@gmail.com?serviceName=gmail.com&user=fromuser&password=secret").
to("mock:result");