Table of Contents
The irc component implements an IRC (Internet Relay Chat) 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-irc</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>irc:nick@host[:port]/#room[?options]
irc:nick@host[:port]?channels=#channel1,#channel2,#channel3[?options]You can append query options to the URI in the following format,
?option=value&option=value&…
The IRC component has no options.
The IRC component supports 26 endpoint options which are listed below:
{% raw %}
| Name | Group | Default | Java Type | Description |
|---|---|---|---|---|
hostname | common |
| Required Hostname for the IRC chat server | |
port | common |
|
| Port number for the IRC chat server |
autoRejoin | common |
|
| Whether to auto re-join when being kicked |
namesOnJoin | common |
|
| Sends NAMES command to channel after joining it. link onReply has to be true in order to process the result which will have the header value irc.num = '353'. |
nickname | common |
| The nickname used in chat. | |
persistent | common |
|
| Use persistent messages. |
realname | common |
| The IRC user’s actual name. | |
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. |
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. | |
colors | advanced |
|
| Whether or not the server supports color codes. |
synchronous | advanced |
|
| Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported). |
onJoin | filter |
|
| Handle user join events. |
onKick | filter |
|
| Handle kick events. |
onMode | filter |
|
| Handle mode change events. |
onNick | filter |
|
| Handle nickname change events. |
onPart | filter |
|
| Handle user part events. |
onPrivmsg | filter |
|
| Handle private message events. |
onQuit | filter |
|
| Handle user quit events. |
onReply | filter |
|
| Whether or not to handle general responses to commands or informational messages. |
onTopic | filter |
|
| Handle topic change events. |
nickPassword | security |
| Your IRC server nickname password. | |
password | security |
| The IRC server password. | |
sslContextParameters | security |
| Used for configuring security using SSL. Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. Note that this setting overrides the trustManager option. | |
trustManager | security |
| The trust manager used to verify the SSL server’s certificate. | |
username | security |
| The IRC server user name. |
{% endraw %}
As of Camel 2.9, the IRC component supports SSL/TLS configuration through the Camel JSSE Configuration Utility. This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels. The following examples demonstrate how to use the utility with the IRC component.
Programmatic configuration of the endpoint
KeyStoreParameters ksp = new KeyStoreParameters();
ksp.setResource("/users/home/server/truststore.jks");
ksp.setPassword("keystorePassword");
TrustManagersParameters tmp = new TrustManagersParameters();
tmp.setKeyStore(ksp);
SSLContextParameters scp = new SSLContextParameters();
scp.setTrustManagers(tmp);
Registry registry = ...
registry.bind("sslContextParameters", scp);
...
from(...)
.to("ircs://camel-prd-user@server:6669/#camel-test?nickname=camel-prd&password=password&sslContextParameters=#sslContextParameters");Spring DSL based configuration of endpoint
...
<camel:sslContextParameters
id="sslContextParameters">
<camel:trustManagers>
<camel:keyStore
resource="/users/home/server/truststore.jks"
password="keystorePassword"/>
</camel:keyManagers>
</camel:sslContextParameters>...
...
<to uri="ircs://camel-prd-user@server:6669/#camel-test?nickname=camel-prd&password=password&sslContextParameters=#sslContextParameters"/>...You can also connect to an SSL enabled IRC server, as follows:
ircs:host[:port]/#room?username=user&password=pass
By default, the IRC transport uses
SSLDefaultTrustManager.
If you need to provide your own custom trust manager, use the
trustManager parameter as follows:
ircs:host[:port]/#room?username=user&password=pass&trustManager=#referenceToMyTrustManagerBean
Available as of Camel 2.2
Some irc rooms requires you to provide a key to be able to join that channel. The key is just a secret word.
For example we join 3 channels where as only channel 1 and 3 uses a key.
irc:nick@irc.server.org?channels=#chan1,#chan2,#chan3&keys=chan1Key,,chan3key
Using the namesOnJoin option one can invoke the IRC-NAMES command after the component has joined a channel.
The server will reply with irc.num = 353. So in order to process the result the property onReply has to be true.
Furthermore one has to filter the onReply exchanges in order to get the names.
For example we want to get all exchanges that contain the usernames of the channel:
from("ircs:nick@myserver:1234/#mychannelname?listOnJoin=true&onReply=true")
.choice()
.when(header("irc.messageType").isEqualToIgnoreCase("REPLY"))
.filter(header("irc.num").isEqualTo("353"))
.to("mock:result").stop();