红帽全球峰会Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.此内容没有您所选择的语言版本。
Chapter 105. Twitter
Twitter
复制链接链接已复制到粘贴板!
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:
URI format
复制链接链接已复制到粘贴板!
twitter://[endpoint]?[options]
twitter://[endpoint]?[options]
TwitterComponent:
复制链接链接已复制到粘贴板!
The twitter component can be configured with the Twitter account settings which is mandatory to configure before using. You can also configure these options directly in the endpoint.
| Option | Description |
|---|---|
| consumerKey | The consumer key |
| consumerSecret | The consumer secret |
| accessToken | The access token |
| accessTokenSecret | The access token secret |
Consumer Endpoints:
复制链接链接已复制到粘贴板!
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 |
|---|---|---|
| directmessage | direct, polling | twitter4j.DirectMessage |
| search | direct, polling | twitter4j.Tweet |
| streaming/filter | event, polling | twitter4j.Status |
| streaming/sample | event, polling | twitter4j.Status |
| timeline/home | direct, polling | twitter4j.Status |
| timeline/mentions | direct, polling | twitter4j.Status |
| timeline/public | direct, polling | twitter4j.Status |
| timeline/retweetsofme | direct, polling | twitter4j.Status |
| timeline/user | direct, polling | twitter4j.Status |
| trends/daily | *Camel 2.10.1:* direct, polling | twitter4j.Status |
| trends/weekly | *Camel 2.10.1:* direct, polling | twitter4j.Status |
Producer Endpoints:
复制链接链接已复制到粘贴板!
| Endpoint | Body Type |
|---|---|
| directmessage | String |
| search | List<twitter4j.Tweet> |
| timeline/user | String |
URI Options
复制链接链接已复制到粘贴板!
| Name | Default Value | Description |
|---|---|---|
| type |
direct
|
direct, event, or polling |
| delay |
60
|
in seconds |
| consumerKey |
null
|
Consumer Key. Can also be configured on the TwitterComponent level instead.
|
| consumerSecret |
null
|
Consumer Secret. Can also be configured on the TwitterComponent level instead.
|
| accessToken |
null
|
Access Token. Can also be configured on the TwitterComponent level instead.
|
| accessTokenSecret |
null
|
Access Token Secret. Can also be configured on the TwitterComponent level instead.
|
| user |
null
|
Username, used for user timeline consumption, direct message production, etc. |
| locations |
null
|
'lat,lon;lat,lon;...' Bounding boxes, created by pairs of lat/lons. Can be used for streaming/filter |
| keywords |
null
|
'foo1,foo2,foo3...' Can be used for search and streaming/filter |
| userIds |
null
|
'username,username...' Can be used for streaming/filter |
| filterOld |
true
|
Filter out old tweets, that has previously been polled. This state is stored in memory only, and based on last tweet id. |
Message body
复制链接链接已复制到粘贴板!
All message bodies utilize objects provided by the Twitter4J API.
Use cases
复制链接链接已复制到粘贴板!
from("direct:foo")
.to("twitter://timeline/user?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]);
from("direct:foo")
.to("twitter://timeline/user?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]);
from("twitter://timeline/home?type=polling&delay=5&consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]")
.to("bean:blah");
from("twitter://timeline/home?type=polling&delay=5&consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]")
.to("bean:blah");
To search for all statuses with the keyword 'camel':
复制链接链接已复制到粘贴板!
from("twitter://search?type=direct&keywords=camel&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");
Searching using a producer with static keywords
复制链接链接已复制到粘贴板!
from("direct:foo")
.to("twitter://search?keywords=camel&consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");
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]");
from("direct:foo")
.setHeader("CamelTwitterKeywords", header("bar"))
.to("twitter://search?consumerKey=[s]&consumerSecret=[s]&accessToken=[s]&accessTokenSecret=[s]");
Example
复制链接链接已复制到粘贴板!
See also the Twitter Websocket Example.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}