Twitter Direct Message
Send and receive Twitter direct messages.
What’s inside
-
Twitter Direct Message component, URI syntax:
twitter-directmessage:user -
Twitter Search component, URI syntax:
twitter-search:keywords -
Twitter Timeline component, URI syntax:
twitter-timeline:timelineType
Please refer to the above links for usage and configuration details.
Maven coordinates
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-twitter-starter</artifactId>
</dependency>Spring Boot Auto-Configuration
The starter supports 42 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
camel.component.twitter-directmessage.access-token | The access token | String | |
camel.component.twitter-directmessage.access-token-secret | The access token secret | String | |
camel.component.twitter-directmessage.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.twitter-directmessage.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean |
camel.component.twitter-directmessage.consumer-key | The consumer key | String | |
camel.component.twitter-directmessage.consumer-secret | The consumer secret | String | |
camel.component.twitter-directmessage.enabled | Whether to enable auto configuration of the twitter-directmessage component. This is enabled by default. | Boolean | |
camel.component.twitter-directmessage.health-check-consumer-enabled | Used for enabling or disabling all consumer based health checks from this component | true | Boolean |
camel.component.twitter-directmessage.health-check-producer-enabled | Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true. | true | Boolean |
camel.component.twitter-directmessage.http-proxy-host | The http proxy host which can be used for the camel-twitter. | String | |
camel.component.twitter-directmessage.http-proxy-password | The http proxy password which can be used for the camel-twitter. | String | |
camel.component.twitter-directmessage.http-proxy-port | The http proxy port which can be used for the camel-twitter. | Integer | |
camel.component.twitter-directmessage.http-proxy-user | The http proxy user which can be used for the camel-twitter. | String | |
camel.component.twitter-directmessage.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.twitter-search.access-token | The access token | String | |
camel.component.twitter-search.access-token-secret | The access token secret | String | |
camel.component.twitter-search.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.twitter-search.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean |
camel.component.twitter-search.consumer-key | The consumer key | String | |
camel.component.twitter-search.consumer-secret | The consumer secret | String | |
camel.component.twitter-search.enabled | Whether to enable auto configuration of the twitter-search component. This is enabled by default. | Boolean | |
camel.component.twitter-search.health-check-consumer-enabled | Used for enabling or disabling all consumer based health checks from this component | true | Boolean |
camel.component.twitter-search.health-check-producer-enabled | Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true. | true | Boolean |
camel.component.twitter-search.http-proxy-host | The http proxy host which can be used for the camel-twitter. | String | |
camel.component.twitter-search.http-proxy-password | The http proxy password which can be used for the camel-twitter. | String | |
camel.component.twitter-search.http-proxy-port | The http proxy port which can be used for the camel-twitter. | Integer | |
camel.component.twitter-search.http-proxy-user | The http proxy user which can be used for the camel-twitter. | String | |
camel.component.twitter-search.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.twitter-timeline.access-token | The access token | String | |
camel.component.twitter-timeline.access-token-secret | The access token secret | String | |
camel.component.twitter-timeline.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.twitter-timeline.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean |
camel.component.twitter-timeline.consumer-key | The consumer key | String | |
camel.component.twitter-timeline.consumer-secret | The consumer secret | String | |
camel.component.twitter-timeline.enabled | Whether to enable auto configuration of the twitter-timeline component. This is enabled by default. | Boolean | |
camel.component.twitter-timeline.health-check-consumer-enabled | Used for enabling or disabling all consumer based health checks from this component | true | Boolean |
camel.component.twitter-timeline.health-check-producer-enabled | Used for enabling or disabling all producer based health checks from this component. Notice: Camel has by default disabled all producer based health-checks. You can turn on producer checks globally by setting camel.health.producersEnabled=true. | true | Boolean |
camel.component.twitter-timeline.http-proxy-host | The http proxy host which can be used for the camel-twitter. | String | |
camel.component.twitter-timeline.http-proxy-password | The http proxy password which can be used for the camel-twitter. | String | |
camel.component.twitter-timeline.http-proxy-port | The http proxy port which can be used for the camel-twitter. | Integer | |
camel.component.twitter-timeline.http-proxy-user | The http proxy user which can be used for the camel-twitter. | String | |
camel.component.twitter-timeline.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |