Table of Contents
Available as of Camel 2.10
The Twitter component enables the most useful features of the Twitter API by encapsulating Twitter4J. It allows direct, polling, or event-driven consumption of timelines, users, trends, and direct messages. Also, it supports producing messages as status updates or direct messages.
Twitter now requires the use of OAuth for all client application authentication. In order to use camel-twitter with your account, you’ll need to create a new application within Twitter at https://dev.twitter.com/apps/new and grant the application access to your account. Finally, generate your access token and secret.
Maven users will need to add the following dependency to their pom.xml for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-twitter</artifactId>
<version>${camel-version}</version>
</dependency>The twitter component can be configured with the Twitter account settings which is mandatory to configure before using.
The Twitter component supports 8 options which are listed below.
{% raw %}
| Name | Java Type | Description |
|---|---|---|
accessToken |
| The access token |
accessTokenSecret |
| The access token secret |
consumerKey |
| The consumer key |
consumerSecret |
| The consumer secret |
httpProxyHost |
| The http proxy host which can be used for the camel-twitter. |
httpProxyUser |
| The http proxy user which can be used for the camel-twitter. |
httpProxyPassword |
| The http proxy password which can be used for the camel-twitter. |
httpProxyPort |
| The http proxy port which can be used for the camel-twitter. |
{% endraw %}
You can also configure these options directly in the endpoint.
Rather than the endpoints returning a List through one single route exchange, camel-twitter creates one route exchange per returned object. As an example, if "timeline/home" results in five statuses, the route will be executed five times (one for each Status).
| Endpoint | Context | Body Type | Notice |
|---|---|---|---|
directmessage | direct, polling | twitter4j.DirectMessage |
|
search | direct, polling | twitter4j.Status |
|
streaming/filter | event, polling | twitter4j.Status |
|
streaming/sample | event, polling | twitter4j.Status |
|
streaming/user | event, polling | twitter4j.Status | Camel 2.16: To receive tweets from protected users and accounts. |
timeline/home | direct, polling | twitter4j.Status |
|
timeline/mentions | direct, polling | twitter4j.Status |
|
timeline/public | direct, polling | twitter4j.Status | @deprecated. Use timeline/home or direct/home instead. Removed from *Camel 2.11 onwards.* |
timeline/retweetsofme | direct, polling | twitter4j.Status |
|
timeline/user | direct, polling | twitter4j.Status |
|
trends/daily | *Camel 2.10.1: direct, polling* | twitter4j.Status | @deprecated. Removed from Camel 2.11 onwards. |
trends/weekly | *Camel 2.10.1: direct, polling* | twitter4j.Status | @deprecated. Removed from Camel 2.11 onwards. |
| Endpoint | Body Type |
|---|---|
directmessage | String |
search | List<twitter4j.Status> |
timeline/user | String |
The Twitter component supports 43 endpoint options which are listed below:
{% raw %}
| Name | Group | Default | Java Type | Description |
|---|---|---|---|---|
kind | common |
| Required What polling mode to use direct polling or event based. The event mode is only supported when the endpoint kind is event based. | |
user | common |
| Username used for user timeline consumption direct message production etc. | |
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. |
sendEmptyMessageWhenIdle | consumer |
|
| If the polling consumer did not poll any files you can enable this option to send an empty message (no body) instead. |
type | consumer |
|
| Endpoint type to use. Only streaming supports event type. |
distanceMetric | consumer (advanced) |
|
| Used by the non-stream geography search to search by radius using the configured metrics. The unit can either be mi for miles or km for kilometers. You need to configure all the following options: longitude latitude radius and distanceMetric. |
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. | |
latitude | consumer (advanced) |
| Used by the non-stream geography search to search by latitude. You need to configure all the following options: longitude latitude radius and distanceMetric. | |
locations | consumer (advanced) |
| Bounding boxes created by pairs of lat/lons. Can be used for streaming/filter. A pair is defined as latlon. And multiple paris can be separated by semi colon. | |
longitude | consumer (advanced) |
| Used by the non-stream geography search to search by longitude. You need to configure all the following options: longitude latitude radius and distanceMetric. | |
pollStrategy | consumer (advanced) |
| A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. | |
radius | consumer (advanced) |
| Used by the non-stream geography search to search by radius. You need to configure all the following options: longitude latitude radius and distanceMetric. | |
twitterStream | consumer (advanced) |
| To use a custom instance of TwitterStream | |
synchronous | advanced |
|
| Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported). |
count | filter |
| Limiting number of results per page. | |
filterOld | filter |
|
| Filter out old tweets that has previously been polled. This state is stored in memory only and based on last tweet id. |
keywords | filter |
| Can be used for search and streaming/filter. Multiple values can be separated with comma. | |
lang | filter |
| The lang string ISO_639-1 which will be used for searching | |
numberOfPages | filter |
|
| The number of pages result which you want camel-twitter to consume. |
sinceId | filter |
|
| The last tweet id which will be used for pulling the tweets. It is useful when the camel route is restarted after a long running. |
userIds | filter |
| To filter by user ids for streaming/filter. Multiple values can be separated by comma. | |
backoffErrorThreshold | scheduler |
| The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | |
backoffIdleThreshold | scheduler |
| The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | |
backoffMultiplier | scheduler |
| To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. | |
delay | scheduler |
|
| Milliseconds before the next poll. |
greedy | scheduler |
|
| If greedy is enabled then the ScheduledPollConsumer will run immediately again if the previous run polled 1 or more messages. |
initialDelay | scheduler |
|
| Milliseconds before the first poll starts. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour). |
runLoggingLevel | scheduler |
|
| The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. |
scheduledExecutorService | scheduler |
| Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | |
scheduler | scheduler |
|
| To use a cron scheduler from either camel-spring or camel-quartz2 component |
schedulerProperties | scheduler |
| To configure additional properties when using a custom scheduler or any of the Quartz2 Spring based scheduler. | |
startScheduler | scheduler |
|
| Whether the scheduler should be auto started. |
timeUnit | scheduler |
|
| Time unit for initialDelay and delay options. |
useFixedDelay | scheduler |
|
| Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. |
httpProxyHost | proxy |
| The http proxy host which can be used for the camel-twitter. Can also be configured on the TwitterComponent level instead. | |
httpProxyPassword | proxy |
| The http proxy password which can be used for the camel-twitter. Can also be configured on the TwitterComponent level instead. | |
httpProxyPort | proxy |
| The http proxy port which can be used for the camel-twitter. Can also be configured on the TwitterComponent level instead. | |
httpProxyUser | proxy |
| The http proxy user which can be used for the camel-twitter. Can also be configured on the TwitterComponent level instead. | |
accessToken | security |
| The access token. Can also be configured on the TwitterComponent level instead. | |
accessTokenSecret | security |
| The access secret. Can also be configured on the TwitterComponent level instead. | |
consumerKey | security |
| The consumer key. Can also be configured on the TwitterComponent level instead. | |
consumerSecret | security |
| The consumer secret. Can also be configured on the TwitterComponent level instead. |
{% endraw %}
| Name | Description |
|---|---|
| This header is used by the search producer to change the search key words dynamically. |
| Camel 2.11.0: This header can override
the option of |
| Camel 2.11.0 This header can override the option
of |
| Camel 2.11.0 This header can override
the option of |
Table of Contents
- To create a status update within your Twitter profile, send this producer a String body:
- To poll, every 60 sec., all statuses on your home timeline:
- To search for all statuses with the keyword 'camel':
- Searching using a producer with static keywords:
- Searching using a producer with dynamic keywords from header:
![[Note]](imagesdb/note.png) | Note |
|---|---|
API Rate Limits: Twitter REST APIs encapsulated by Twitter4J are subjected to API Rate Limiting. You can find the per method limits in the API Rate Limits documentation. Note that endpoints/resources not listed in that page are default to 15 requests per allotted user per window. |
from("direct:foo")
.to("twitter://timeline/user?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]);from("twitter://timeline/home?type=polling&delay=60&consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]")
.to("bean:blah");from("twitter://search?type=direct&keywords=camel&consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]")
.to("bean:blah");from("direct:foo")
.to("twitter://search?keywords=camel&consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");In the bar header we have the keywords we want to search, so we can
assign this value to the CamelTwitterKeywords header:
from("direct:foo")
.setHeader("CamelTwitterKeywords", header("bar"))
.to("twitter://search?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");See also the Twitter Websocket Example.