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.Ce contenu n'est pas disponible dans la langue sélectionnée.
EIP Component Reference
Quickly find the settings for all of the components
Copyright © 2013 Red Hat, Inc. and/or its affiliates.
Abstract
Chapter 1. Components Overview Copier lienLien copié sur presse-papiers!
Abstract
1.1. List of Components Copier lienLien copié sur presse-papiers!
Table of components Copier lienLien copié sur presse-papiers!
Component | Endpoint URI | Artifact ID | Description |
---|---|---|---|
ActiveMQ | activemq:[queue:|topic:]DestinationName | activemq-core | For JMS Messaging with Apache ActiveMQ. |
AHC | ahc:http[s]://Hostname[:Port][/ResourceUri] | camel-ahc | To call external HTTP services using Async Http Client |
AMQP | amqp:[queue:|topic:]DestinationName[?Options]] | camel-amqp | For messaging with the AMQP protocol. |
APNS |
apns:notify[?Options] apns:consumer[?Options]
| camel-apns | For sending notifications to Apple iOS devices. |
Atom | atom://AtomUri[?Options] | camel-atom | Working with Apache Abdera for atom integration, such as consuming an atom feed. |
Avro | avro:http://Hostname[:Port][?Options] | camel-avro | Working with Apache Avro for data serialization. |
AWS-DDB | aws-ddb://TableName[?Options] | camel-aws | For working with Amazon's DynamoDB (DDB). |
AWS-SDB | aws-sdb://DomainName[?Options] | camel-aws | For working with Amazon's SimpleDB (SDB). |
AWS-SES | aws-ses://From[?Options] | camel-aws | For working with Amazon's Simple Email Service (SES). |
AWS-S3 | aws-s3://BucketName[?Options] | camel-aws | For working with Amazon's Simple Storage Service (S3). |
AWS-SNS | aws-sns://TopicName[?Options] | camel-aws | For Messaging with Amazon's Simple Notification Service (SNS). |
AWS-SQS | aws-sqs://QueueName[?Options] | camel-aws | For Messaging with Amazon's Simple Queue Service (SQS). |
Bean | bean:BeanID[?methodName=Method] | camel-core | Uses the Bean Binding to bind message exchanges to beans in the Registry. Is also used for exposing and invoking POJO (Plain Old Java Objects). |
Bean Validation |
bean-validator:Something[?Options]
| camel-bean-validator | Validates the payload of a message using the Java Validation API (JSR 303 and JAXP Validation) and its reference implementation Hibernate Validator. |
Browse | browse: Name | camel-core | Provdes a simple BrowsableEndpoint which can be useful for testing, visualisation tools or debugging. The exchanges sent to the endpoint are all available to be browsed. |
Cache | cache://CacheName[?Options] | camel-cache | The cache component enables you to perform caching operations using EHCache as the Cache Implementation. |
Class | class:ClassName[?method=MethodName] | camel-core | Uses the Bean binding to bind message exchanges to beans in the registry. Is also used for exposing and invoking POJOs (Plain Old Java Objects). |
Cometd | cometd://Hostname[:Port]/ChannelName[?Options] | camel-cometd | A transport for working with the jetty implementation of the cometd/bayeux protocol. |
Context | context:CamelContextId:LocalEndpointName | camel-context | Refers to an endpoint in a different CamelContext . |
Crypto |
crypto:sign:Name[?Options] crypto:verify:Name[?Options]
| camel-crypto | Sign and verify exchanges using the Signature Service of the Java Cryptographic Extension. |
CXF | cxf://Address[?Options] | camel-cxf | Working with Apache CXF for web services integration. |
CXF Bean | cxf:BeanName | camel-cxf | Proceess the exchange using a JAX WS or JAX RS annotated bean from the registry. |
CXFRS | cxfrs:bean:RsEndpoint[?Options] | camel-cxf | Provides integration with Apache CXF for connecting to JAX-RS services hosted in CXF. |
DataSet | dataset:Name[?Options] | camel-core | For load & soak testing the DataSet provides a way to create huge numbers of messages for sending to Components or asserting that they are consumed correctly. |
Direct | direct:EndpointID[?Options] | camel-core | Synchronous call (single-threaded) to another endpoint from same CamelContext. |
Direct-VM | direct-vm:EndpointID[?Options] | camel-core | Synchronous call (single-threaded) to another endpoint in another CamelContext running in the same JVM. |
DNS | dns:Operation | camel-dns | Look up domain information and run DNS queries using DNSJava |
EJB | ejb:EjbName[?method=MethodName] | camel-ejb | Uses the Bean binding to bind message exchanges to EJBs. It works like the Bean component, but just for accessing EJBs. Supports EJB 3.0 onwards. |
Event | event://dummy | camel-spring | Working with Spring ApplicationEvents. |
EventAdmin | eventadmin:topic | camel-eventadmin | |
Exec | exec://Executable[?Options] | camel-exec | Execute system command. |
Fabric | fabric:ClusterID[:PublishedURI][?Options] | fabric-camel | Look up or publish a fabric endpoint. |
File2 | file://DirectoryName[?Options] | camel-core | Sending messages to a file or polling a file or directory. |
Flatpack | flatpack:[fixed|delim]: ConfigFile | camel-flatpack | Processing fixed width or delimited files or messages using the FlatPack library |
FOP | fop:OutputFormat | camel-fop | Renders the message into different output formats using Apache FOP. |
FTP2 | ftp://[Username@]Hostname[:Port]/Directoryname[?Options] | camel-ftp | Sending and receiving files over FTP. |
GAuth | gauth://Name[?Options] | camel-gae | Used by web applications to implement a Google-specific OAuth consumer |
GHTTP |
ghttp:///Path[?Options] ghttp://Hostname[:Port]/Path[?Options] ghttps://Hostname[:Port]/Path[?Options]
| camel-gae | Provides connectivity to the GAE URL fetch service and can also be used to receive messages from servlets. |
GLogin | glogin://Hostname[:Port][?Options] | camel-gae | Used by Camel applications outside Google App Engine (GAE) for programmatic login to GAE applications. |
GMail |
gmail://Username@gmail.com[?Options] gmail://Username@googlemail.com[?Options]
| camel-gae | Supports sending of emails via the GAE mail service. |
Guava EventBus | guava-eventbus:BusName[?EventClass=ClassName] | camel-guava-eventbus | The Google Guava EventBus allows publish-subscribe-style communication between components without requiring the components to explicitly register with one another (and thus be aware of each other). This component provides integration bridge between Camel and Google Guava EventBus infrastructure. |
GTask | gtask://QueueName | camel-gae | Supports asynchronous message processing on GAE using the task queueing service as a message queue. |
Hazelcast | hazelcast://StoreType:CacheName[?Options] | camel-hazelcast | Hazelcast is a data grid entirely implemented in Java (single JAR). This component supports map, multimap, seda, queue, set, atomic number and simple cluster. |
HBase | hbase://Table[?Options] | camel-hbase | For reading/writing from/to an HBase store (Hadoop database). |
HDFS | hdfs://Path[?Options] | camel-hdfs | For reading/writing from/to an HDFS filesystem. |
HL7 | mina:tcp://Host[:Port] | camel-hl7 | For working with the HL7 MLLP protocol and the HL7 model using the HAPI library. |
HTTP | http://Hostname[:Port][/ResourceUri] | camel-http | For calling out to external HTTP servers, using Apache HTTP Client 3.x. |
HTTP4 | http://Hostname[:Port][/ResourceUri] | camel-http4 | For calling out to external HTTP servers, using Apache HTTP Client 4.x. |
iBATIS | ibatis:OperationName[?Options] | camel-ibatis | Performs a query, poll, insert, update or delete in a relational database using Apache iBATIS. |
IMap | imap://[UserName@]Host[:Port][?Options] | camel-mail | Receiving email using IMap. |
IRC | irc:Host[:Port]/#Room | camel-irc | For IRC communication. |
JavaSpace | javaspace:jini://Host[?Options] | camel-javaspace | Sending and receiving messages through JavaSpace. |
JBI |
jbi:service:serviceNamespace[sep]serviceName jbi:endpoint:serviceNamespace[sep]serviceName[sep]endpointName jbi:name:endpointName
| camel-jbi | For JBI integration such as working with Apache ServiceMix. |
JClouds | jclouds:[Blobstore|ComputService]:Provider | camel-jclouds | For interacting with cloud compute & blobstore service via JClouds. |
JCR | jcr://UserName:Password@Repository/path/to/node | camel-jcr | Storing a message in a JCR (JSR-170) compliant repository like Apache Jackrabbit. |
JDBC | jdbc:DataSourceName[?Options] | camel-jdbc | For performing JDBC queries and operations. |
Jetty | jetty:http://Host[:Port][/ResourceUri] | camel-jetty | For exposing services over HTTP. |
Jing |
rng:LocalOrRemoteResource rnc:LocalOrRemoteResource
| camel-jing | Validates the payload of a message using RelaxNG or RelaxNG compact syntax. |
JMS | jms:[temp:][queue:|topic:]DestinationName[?Options] | camel-jms | Working with JMS providers. |
JMX | jmx://Platform[?Options] | camel-jmx | For working with JMX notification listeners. |
JPA | jpa:[EntityClassName][?Options] | camel-jpa | For using a database as a queue via the JPA specification for working with OpenJPA, Hibernate or TopLink. |
Jsch | scp://Hostname/Destination | camel-jsch | Support for the scp protocol. |
JT400 | jt400://User:Pwd@System/PathToDTAQ | camel-jt400 | For integrating with data queues on an AS/400 (aka System i, IBM i, i5, ...) system. |
Kestrel | kestrel://[AddressList/]Queuename[?Options] | camel-kestrel | For producing to or consuming from Kestrel queues. |
Krati | krati://[PathToDatastore/][?Options] | camel-krati | For producing to or consuming to Krati datastores. |
Language | language://LanguageName[:Script][?Options] | camel-core | Executes language scripts. |
LDAP | ldap:Host[:Port]?base=...[&scope=Scope] | camel-ldap | Performing searches on LDAP servers (Scope must be one of object|onelevel|subtree ). |
List | list:ListID | camel-core | Provides a simple BrowsableEndpoint which can be useful for testing, visualisation tools or debugging. The exchanges sent to the endpoint are all available to be browsed. |
Log | log:LoggingCategory[?level=LoggingLevel] | camel-core | Uses Jakarta Commons Logging to log the message exchange to some underlying logging system like log4j. |
Lucene |
lucene:SearcherName:insert[?analyzer=Analyzer] lucene:SearcherName:query[?analyzer=Analyzer]
| camel-lucene | Uses Apache Lucene to perform Java-based indexing and full text based searches using advanced analysis/tokenization capabilities. |
Master | REVISIT | ||
MINA |
mina:tcp://Hostname[:Port][?Options] mina:udp://Hostname[:Port][?Options] mina:multicast://Hostname[:Port][?Options] mina:vm://Hostname[:Port][?Options]
| camel-mina | Working with Apache MINA. |
Mock | mock:EndpointID | camel-core | For testing routes and mediation rules using mocks. |
MongoDB | mongodb:Connection[?Options] | camel-mongodb | Interacts with MongoDB databases and collections. Offers producer endpoints to perform CRUD-style operations and more against databases and collections, as well as consumer endpoints to listen on collections and dispatch objects to Camel routes. |
MQTT | mqtt:Name | camel-mqtt | Component for communicating with MQTT M2M message brokers |
MSV | msv:LocalOrRemoteResource | camel-msv | Validates the payload of a message using the MSV Library. |
MyBatis | mybatis:StatementName | camel-mybatis | Performs a query, poll, insert, update or delete in a relational database using MyBatis. |
Nagios | nagios://Host[:Port][?Options] | camel-nagios | Sending passive checks to Nagios using JSendNSCA. |
Netty |
netty:tcp://localhost:99999[?Options] netty:udp://Remotehost:99999/[?Options]
| camel-netty | Working with TCP and UDP protocols using Java NIO based capabilities offered by the JBoss Netty community project. |
NMR | nmr:serviceMixURI | servicemix-camel | For OSGi integration when working with Red Hat JBoss Fuse. Enables you to specify the URI of a ServiceMix endpoint. |
Pax-Logging | paxlogging:Appender | camel-paxlogging | |
POP | pop3://[UserName@]Host[:Port][?Options] | camel-mail | Receiving email using POP3 and JavaMail. |
Printer |
lpr://localhost[:Port]/default[?Options] lpr://RemoteHost[:Port]/path/to/printer[?Options]
| camel-printer | Provides a way to direct payloads on a route to a printer. |
Properties | properties://Key[?Options] | camel-properties | Facilitates using property placeholders directly in endpoint URI definitions. |
Quartz |
quartz://[GroupName/]TimerName[?Options] quartz://GroupName/TimerName/CronExpression
| camel-quartz | Provides a scheduled delivery of messages using the Quartz scheduler. |
Quickfix |
quickfix-server:ConfigFile quickfix-client:ConfigFile
| camel-quickfix | Implementation of the QuickFix for Java engine which allow to send/receive FIX messages. |
Ref | ref:EndpointID | camel-core | Component for lookup of existing endpoints bound in the Registry. |
Restlet | restlet:RestletUrl[?Options] | camel-restlet | Component for consuming and producing Restful resources using Restlet. |
RMI | rmi://RmiRegistryHost:RmiRegistryPort/RegistryPath | camel-rmi | Working with RMI. |
Routebox | routebox:routeboxName[?Options] | camel-routebox | |
RSS | rss:Uri | camel-rss | Working with ROME for RSS integration, such as consuming an RSS feed. |
RNC | rnc:LocalOrRemoteResource | camel-jing | Validates the payload of a message using RelaxNG Compact Syntax. |
RNG | rng:LocalOrRemoteResource | camel-jing | Validates the payload of a message using RelaxNG. |
Scalate | scalate:TemplateName[?Options] | org.fusesource.scalate/scalate-camel | Uses the given Scalate template to transform the message. |
SEDA | seda:EndpointID | camel-core | Used to deliver messages to a java.util.concurrent.BlockingQueue, useful when creating SEDA style processing pipelines within the same CamelContext. |
SERVLET | servlet://RelativePath[?Options] | camel-servlet | Provides HTTP based endpoints for consuming HTTP requests that arrive at a HTTP endpoint and this endpoint is bound to a published Servlet. |
SFTP | sftp://[Username@]Hostname[:Port]/Directoryname[?Options] | camel-ftp | Sending and receiving files over SFTP. |
Sip |
sip://User@Hostname[:Port][?Options] sips://User@Hostname[:Port][?Options]
| camel-sip | Publish/subscribe communication capability using the telecom SIP protocol. RFC3903 - Session Initiation Protocol (SIP) Extension for Event |
SMPP | smpp://UserInfo@Host[:Port][?Options] | camel-smpp | To send and receive SMS using Short Messaging Service Center using the JSMPP library. |
SMTP | smtp://[UserName@]Host[:Port][?Options] | camel-mail | Sending email using SMTP and JavaMail. |
SNMP | snmp://Hostname[:Port][?Options] | camel-snmp | Gives you the ability to poll SNMP capable devices or receive traps. |
Solr | solr://Hostname[:Port]/Solr[?Options] | camel-solr | Uses the Solrj client API to interface with an Apache Lucene Solr server. |
SpringBatch | spring-batch:Job[?Options] | camel-spring-batch | To bridge Camel and Spring Batch. |
Spring Integration | spring-integration:DefaultChannelName[?Options] | camel-spring-integration | The bridge component of Camel and Spring Integration. |
Spring Web Services | spring-ws:[MappingType:]Address[?Options] | camel-spring-ws | Client-side support for accessing web services, and server-side support for creating your own contract-first web services using Spring Web Services. |
SQL | sql:SqlQueryString[?Options] | camel-sql | Performing SQL queries using JDBC. |
SSH | ssh:[Username[:Password]@]Host[:Port][?Options] | camel-ssh | For sending commands to a SSH server. |
StAX | stax:ContentHandlerClassName | camel-stax | Process messages through a SAX ContentHandler. |
Stream | stream:[in|out|err|header][?Options] | camel-stream | Read or write to an input/output/error/file stream rather like Unix pipes. |
String Template | string-template:TemplateURI[?Options] | camel-stringtemplate | Generates a response using a String Template. |
Stub | stub:SomeOtherCamelUri | camel-core | Allows you to stub out some physical middleware endpoint for easier testing or debugging. |
Test | test:RouterEndpointUri | camel-spring | Creates a Mock endpoint which expects to receive all the message bodies that could be polled from the given underlying endpoint. |
Timer | timer:EndpointID[?Options] | camel-core | A timer endpoint. |
twitter://[Endpoint][?Options] | camel-twitter | A Twitter endpoint. | |
Validation | validator:LocalOrRemoteResource | camel-spring | Validates the payload of a message using XML Schema and JAXP Validation. |
Velocity | velocity:TemplateURI[?Options] | camel-velocity | Generates a response using an Apache Velocity template. |
VM | vm:EndpointID | camel-core | Used to deliver messages to a java.util.concurrent.BlockingQueue, useful when creating SEDA style processing pipelines within the same JVM. |
Websocket | websocket://Hostname[:Port]/Path | camel-websocket | Communicating with Websocket clients. |
XMPP | xmpp:Hostname[:Port][/Room] | camel-xmpp | Working with XMPP and Jabber. |
XQuery | xquery:TemplateURI | camel-saxon | Generates a response using an XQuery template. |
XSLT | xslt:TemplateURI[?Options] | camel-spring | xquery:someXQueryResource. |
Zookeeper | zookeeper://Hostname[:Port]/Path | camel-zookeeper | Working with ZooKeeper cluster(s). |
Chapter 2. ActiveMQ Copier lienLien copié sur presse-papiers!
ActiveMQ Component Copier lienLien copié sur presse-papiers!
JmsTemplate
for sending and a MessageListenerContainer
for consuming. All the options from the JMS component also apply for this component.
activemq.jar
or activemq-core.jar
on your classpath along with any Apache Camel dependencies such as camel-core.jar
, camel-spring.jar
and camel-jms.jar
.
URI format Copier lienLien copié sur presse-papiers!
activemq:[queue:|topic:]destinationName
activemq:[queue:|topic:]destinationName
FOO.BAR
, use:
activemq:FOO.BAR
activemq:FOO.BAR
queue:
prefix, if you prefer:
activemq:queue:FOO.BAR
activemq:queue:FOO.BAR
topic:
prefix. For example, to connect to the topic, Stocks.Prices
, use:
activemq:topic:Stocks.Prices
activemq:topic:Stocks.Prices
Options Copier lienLien copié sur presse-papiers!
Configuring the Connection Factory Copier lienLien copié sur presse-papiers!
activeMQComponent()
method while specifying the brokerURL used to connect to ActiveMQ.
camelContext.addComponent("activemq", activeMQComponent("vm://localhost?broker.persistent=false"));
camelContext.addComponent("activemq", activeMQComponent("vm://localhost?broker.persistent=false"));
Configuring the Connection Factory using Spring XML Copier lienLien copié sur presse-papiers!
Using connection pooling Copier lienLien copié sur presse-papiers!
<dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-pool</artifactId> <version>5.3.2</version> </dependency>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-pool</artifactId>
<version>5.3.2</version>
</dependency>
PooledConnectionFactory
will then create a connection pool with up to 8 connections in use at the same time. Each connection can be shared by many sessions. There is an option named maxActive
you can use to configure the maximum number of sessions per connection; the default value is 500
. From ActiveMQ 5.7 onwards the option has been renamed to better reflect its purpose, being named as maxActiveSessionPerConnection
. Notice the concurrentConsumers
is set to a higher value than maxConnections
is. This is okay, as each consumer is using a session, and as a session can share the same connection, we are in the safe. In this example we can have 8 * 500 = 4000 active sessions at the same time.
Invoking MessageListener POJOs in a route Copier lienLien copié sur presse-papiers!
public class MyListener implements MessageListener { public void onMessage(Message jmsMessage) { // ... } }
public class MyListener implements MessageListener {
public void onMessage(Message jmsMessage) {
// ...
}
}
from("file://foo/bar"). bean(MyListener.class);
from("file://foo/bar").
bean(MyListener.class);
MessageListener
POJO\!
Using ActiveMQ Destination Options Copier lienLien copié sur presse-papiers!
Consuming Advisory Messages Copier lienLien copié sur presse-papiers!
Getting Component JAR Copier lienLien copié sur presse-papiers!
activemq-camel
<dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-camel</artifactId> <version>5.6.0</version> </dependency>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-camel</artifactId>
<version>5.6.0</version>
</dependency>
Chapter 3. AHC Copier lienLien copié sur presse-papiers!
Async Http Client (AHC) Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
ahc:http://hostname[:port][/resourceUri][?options] ahc:https://hostname[:port][/resourceUri][?options]
ahc:http://hostname[:port][/resourceUri][?options]
ahc:https://hostname[:port][/resourceUri][?options]
?option=value&option=value&...
AhcEndpoint Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
throwExceptionOnFailure
|
true
|
Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code.
|
bridgeEndpoint
|
false
|
If the option is true, then the Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the AhcProducer send all the fault response back. |
transferException
|
false
|
If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the AhcOperationFailedException . The caused exception is required to be serialized.
|
client
|
null
|
To use a custom com.ning.http.client.AsyncHttpClient .
|
clientConfig
|
null
|
To configure the AsyncHttpClient s use a custom com.ning.http.client.AsyncHttpClientConfig .
|
clientConfig.x
|
null
|
To configure additional properties of the com.ning.http.client.AsyncHttpClientConfig instance used by the endpoint. Note that configuration options set using this parameter will be merged with those set using the clientConfig parameter or the instance set at the component level with properties set using this parameter taking priority.
|
binding
|
null
|
To use a custom org.apache.camel.component.ahc.AhcBinding .
|
sslContextParameters
|
null
|
Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the CAMEL:Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level.
|
AhcComponent Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
client
|
null
|
To use a custom com.ning.http.client.AsyncHttpClient .
|
clientConfig
|
null
|
To configure the AsyncHttpClient s use a custom com.ning.http.client.AsyncHttpClientConfig .
|
binding
|
null
|
To use a custom org.apache.camel.component.ahc.AhcBinding .
|
sslContextParameters
|
null
|
Camel 2.9: To configure custom SSL/TLS configuration options at the component level. See Using the JSSE Configuration Utility for more details. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level. |
AhcComponent
will propagate those options to AhcEndpoint
s being created. However the AhcEndpoint
can also configure/override a custom option. Options set on endpoints will always take precedence over options from the AhcComponent
.
Message Headers Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
Exchange.HTTP_URI
|
String
|
URI to call. Will override existing URI set directly on the endpoint. |
Exchange.HTTP_PATH
|
String
|
Request URI's path, the header will be used to build the request URI with the HTTP_URI. If the path is start with "/", http producer will try to find the relative path based on the Exchange.HTTP_BASE_URI header or the exchange.getFromEndpoint().getEndpointUri();
|
Exchange.HTTP_QUERY
|
String
|
URI parameters. Will override existing URI parameters set directly on the endpoint. |
Exchange.HTTP_RESPONSE_CODE
|
int
|
The HTTP response code from the external server. Is 200 for OK. |
Exchange.HTTP_CHARACTER_ENCODING
|
String
|
Character encoding. |
Exchange.CONTENT_TYPE
|
String
|
The HTTP content type. Is set on both the IN and OUT message to provide a content type, such as text/html .
|
Exchange.CONTENT_ENCODING
|
String
|
The HTTP content encoding. Is set on both the IN and OUT message to provide a content encoding, such as gzip .
|
Message Body Copier lienLien copié sur presse-papiers!
Response code Copier lienLien copié sur presse-papiers!
- Response code is in the range 100..299, Camel regards it as a success response.
- Response code is in the range 300..399, Camel regards it as a redirection response and will throw a
AhcOperationFailedException
with the information. - Response code is 400+, Camel regards it as an external server failure and will throw a
AhcOperationFailedException
with the information. The option,throwExceptionOnFailure
, can be set tofalse
to prevent theAhcOperationFailedException
from being thrown for failed response codes. This allows you to get any response from the remote server.
AhcOperationFailedException Copier lienLien copié sur presse-papiers!
- The HTTP status code
- The HTTP status line (text of the status code)
- Redirect location, if server returned a redirect
- Response body as a
java.lang.String
, if server provided a body as response
Calling using GET or POST Copier lienLien copié sur presse-papiers!
GET
or POST
HTTP method should be used: 1. Use method provided in header. 2. GET
if query string is provided in header. 3. GET
if endpoint is configured with a query string. 4. POST
if there is data to send (body is not null). 5. GET
otherwise.
Configuring URI to call Copier lienLien copié sur presse-papiers!
oldhost
, using HTTP.
from("direct:start") .to("ahc:http://oldhost");
from("direct:start")
.to("ahc:http://oldhost");
Exchange.HTTP_URI
, on the message.
from("direct:start") .setHeader(Exchange.HTTP_URI, constant("http://newhost")) .to("ahc:http://oldhost");
from("direct:start")
.setHeader(Exchange.HTTP_URI, constant("http://newhost"))
.to("ahc:http://oldhost");
Configuring URI Parameters Copier lienLien copié sur presse-papiers!
Exchange.HTTP_QUERY
on the message.
from("direct:start") .to("ahc:http://oldhost?order=123&detail=short");
from("direct:start")
.to("ahc:http://oldhost?order=123&detail=short");
from("direct:start") .setHeader(Exchange.HTTP_QUERY, constant("order=123&detail=short")) .to("ahc:http://oldhost");
from("direct:start")
.setHeader(Exchange.HTTP_QUERY, constant("order=123&detail=short"))
.to("ahc:http://oldhost");
How to set the http method (GET/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) to the HTTP producer Copier lienLien copié sur presse-papiers!
from("direct:start") .setHeader(Exchange.HTTP_METHOD, constant("POST")) .to("ahc:http://www.google.com") .to("mock:results");
from("direct:start")
.setHeader(Exchange.HTTP_METHOD, constant("POST"))
.to("ahc:http://www.google.com")
.to("mock:results");
Configuring charset Copier lienLien copié sur presse-papiers!
POST
to send data you can configure the charset
using the Exchange
property:
exchange.setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
exchange.setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
URI Parameters from the endpoint URI Copier lienLien copié sur presse-papiers!
&
character as separator, just as you would in the web browser. Camel does no tricks here.
// we query for Camel at the Google page template.sendBody("ahc:http://www.google.com/search?q=Camel", null);
// we query for Camel at the Google page
template.sendBody("ahc:http://www.google.com/search?q=Camel", null);
URI Parameters from the Message Copier lienLien copié sur presse-papiers!
Map headers = new HashMap(); headers.put(Exchange.HTTP_QUERY, "q=Camel&lr=lang_en"); // we query for Camel and English language at Google template.sendBody("ahc:http://www.google.com/search", null, headers);
Map headers = new HashMap();
headers.put(Exchange.HTTP_QUERY, "q=Camel&lr=lang_en");
// we query for Camel and English language at Google
template.sendBody("ahc:http://www.google.com/search", null, headers);
?
and you can separate parameters as usual with the &
char.
Getting the Response Code Copier lienLien copié sur presse-papiers!
Exchange.HTTP_RESPONSE_CODE
.
Configuring AsyncHttpClient Copier lienLien copié sur presse-papiers!
AsyncHttpClient
client uses a AsyncHttpClientConfig
to configure the client. See the documentation at Async Http Client for more details.
AsyncHttpClientConfig
which we configure on the AhcComponent
.
AsyncHttpClientConfigBean
class provides getters and setters for the configuration options available in AsyncHttpClientConfig
. An instance of AsyncHttpClientConfigBean
may be passed directly to the AHC component or referenced in an endpoint URI using the clientConfig
URI parameter.
AsyncHttpClientConfig
. The properties specified in the endpoint URI are merged with those specified in the configuration referenced by the "clientConfig" URI parameter with those being set using the "clientConfig." parameter taking priority. The AsyncHttpClientConfig
instance referenced is always copied for each endpoint such that settings on one endpoint will remain independent of settings on any previously created endpoints. The example below shows how to configure the AHC component using the "clientConfig." type URI parameters.
from("direct:start") .to("ahc:http://localhost:8080/foo?clientConfig.maxRequestRetry=3&clientConfig.followRedirects=true")
from("direct:start")
.to("ahc:http://localhost:8080/foo?clientConfig.maxRequestRetry=3&clientConfig.followRedirects=true")
SSL Support (HTTPS) Copier lienLien copié sur presse-papiers!
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
Programmatic configuration of the component Copier lienLien copié sur presse-papiers!
Spring DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
Chapter 4. AMQP Copier lienLien copié sur presse-papiers!
AMQP Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
amqp:[queue:|topic:]destinationName[?options]
amqp:[queue:|topic:]destinationName[?options]
Chapter 5. APNS Copier lienLien copié sur presse-papiers!
Apns Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
apns:notify[?options]
apns:notify[?options]
apns:consumer[?options]
apns:consumer[?options]
Options Copier lienLien copié sur presse-papiers!
Producer Copier lienLien copié sur presse-papiers!
Property | Default | Description |
---|---|---|
tokens
|
Empty by default. Configure this property in case you want to statically declare tokens related to devices you want to notify. Tokens are separated by comma. |
Consumer Copier lienLien copié sur presse-papiers!
Property | Default | Description |
---|---|---|
delay
|
3600
|
Delay in seconds between each poll. |
initialDelay
|
10
|
Seconds before polling starts. |
timeUnit
|
SECONDS
|
Time Unit for polling. |
userFixedDelay
|
true
|
If true , use fixed delay between pools, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
|
?option=value&option=value&...
Exchange data format Copier lienLien copié sur presse-papiers!
Message Headers Copier lienLien copié sur presse-papiers!
Property | Default | Description |
---|---|---|
CamelApnsTokens
|
Empty by default. | |
CamelApnsMessageType
|
STRING, PAYLOAD
|
In case you choose PAYLOAD for the message type, then the message will be considered as a APNS payload and sent as is. In case you choose STRING, message will be converted as a APNS payload |
Samples Copier lienLien copié sur presse-papiers!
Camel Xml route Copier lienLien copié sur presse-papiers!
Camel Java route Copier lienLien copié sur presse-papiers!
Create camel context and declare apns component programmatically Copier lienLien copié sur presse-papiers!
ApnsProducer - iOS target device dynamically configured via header: "CamelApnsTokens" Copier lienLien copié sur presse-papiers!
ApnsProducer - iOS target device statically configured via uri Copier lienLien copié sur presse-papiers!
ApnsConsumer Copier lienLien copié sur presse-papiers!
from("apns:consumer?initialDelay=10&delay=3600&timeUnit=SECONDS") .to("log:com.apache.camel.component.apns?showAll=true&multiline=true") .to("mock:result");
from("apns:consumer?initialDelay=10&delay=3600&timeUnit=SECONDS")
.to("log:com.apache.camel.component.apns?showAll=true&multiline=true")
.to("mock:result");
See Also Copier lienLien copié sur presse-papiers!
Chapter 6. Atom Copier lienLien copié sur presse-papiers!
Atom Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
atom://atomUri[?options]
atom://atomUri[?options]
Options Copier lienLien copié sur presse-papiers!
Property | Default | Description |
---|---|---|
splitEntries
|
true
|
If true Apache Camel will poll the feed and for the subsequent polls return each entry poll by poll. If the feed contains 7 entries then Apache Camel will return the first entry on the first poll, the 2nd entry on the next poll, until no more entries where as Apache Camel will do a new update on the feed. If false then Apache Camel will poll a fresh feed on every invocation.
|
filter
|
true
|
Is only used by the split entries to filter the entries to return. Apache Camel will default use the UpdateDateFilter that only return new entries from the feed. So the client consuming from the feed never receives the same entry more than once. The filter will return the entries ordered by the newest last.
|
lastUpdate
|
null
|
Is only used by the filter, as the starting timestamp for selection never entries (uses the entry.updated timestamp). Syntax format is: yyyy-MM-ddTHH:MM:ss . Example: 2007-12-24T17:45:59 .
|
throttleEntries
|
true
|
Camel 2.5: Sets whether all entries identified in a single feed poll should be delivered immediately. If true , only one entry is processed per consumer.delay . Only applicable when splitEntries is set to true .
|
feedHeader
|
true
|
Sets whether to add the Abdera Feed object as a header. |
sortEntries
|
false
|
If splitEntries is true , this sets whether to sort those entries by updated date.
|
consumer.delay
|
60000
|
Delay in millis between each poll. |
consumer.initialDelay
|
1000
|
Millis before polling starts. |
consumer.userFixedDelay
|
false
|
If true , use fixed delay between pools, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
|
?option=value&option=value&...
Exchange data format Copier lienLien copié sur presse-papiers!
Exchange
with the entries. Depending on the splitEntries
flag Apache Camel will either return one Entry
or a List<Entry>
.
Option | Value | Behavior |
---|---|---|
splitEntries
|
true
|
Only a single entry from the currently being processed feed is set: exchange.in.body(Entry)
|
splitEntries
|
false
|
The entire list of entries from the feed is set: exchange.in.body(List<Entry>)
|
Feed
object on the in header (see feedHeader
option to disable this):
Message Headers Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelAtomFeed
|
Apache Camel 2.0: When consuming the org.apache.abdera.model.Feed object is set to this header.
|
Samples Copier lienLien copié sur presse-papiers!
from("atom://http://macstrac.blogspot.com/feeds/posts/default").to("seda:feeds");
from("atom://http://macstrac.blogspot.com/feeds/posts/default").to("seda:feeds");
Chapter 7. avro Copier lienLien copié sur presse-papiers!
Avro Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
Apache Avro Overview Copier lienLien copié sur presse-papiers!
Using the Avro data format Copier lienLien copié sur presse-papiers!
Using Avro IPC in Camel Copier lienLien copié sur presse-papiers!
avro:[transport]:[host]:[port]
avro:[transport]:[host]:[port]
Avro IPC URI Options Copier lienLien copié sur presse-papiers!
Name | Description |
---|---|
protocolClassName
|
The class name of the avro protocol. |
Avro IPC Headers Copier lienLien copié sur presse-papiers!
Name | Description |
---|---|
CamelAvroMessageName
|
The name of the message to send. |
Examples Copier lienLien copié sur presse-papiers!
Chapter 8. AWS Copier lienLien copié sur presse-papiers!
8.1. Introduction to the AWS Components Copier lienLien copié sur presse-papiers!
Camel Components for Amazon Web Services Copier lienLien copié sur presse-papiers!
AWS service | Camel component | Camel Version | Component description |
---|---|---|---|
Simple Queue Service (SQS) | AWS-SQS | 2.6 | Supports sending and receiving messages using SQS |
Simple Notification Service (SNS) | AWS-SNS | 2.8 | Supports sending messages using SNS |
Simple Storage Service (S3) | AWS-S3 | 2.8 | Supports storing and retrieving of objects using S3 |
Simple Email Service (SES) | AWS-SES | 2.8.4 | Supports sending emails using SES |
SimpleDB | AWS-SDB | 2.8.4 | Supports storing retrieving data to/from SDB |
DynamoDB | AWS-DDB | 2.10.0 | Supports storing retrieving data to/from DDB |
8.2. AWS-DDB Copier lienLien copié sur presse-papiers!
DDB Component Copier lienLien copié sur presse-papiers!
URI Format Copier lienLien copié sur presse-papiers!
aws-ddb://domainName[?options]
aws-ddb://domainName[?options]
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
amazonDDBClient |
null
|
Producer |
Reference to a com.amazonaws.services.dynamodb.AmazonDynamoDB in the Registry.
|
accessKey |
null
|
Producer | Amazon AWS Access Key |
secretKey |
null
|
Producer | Amazon AWS Secret Key |
amazonDdbEndpoint |
null
|
Producer | The region with which the AWS-DDB client wants to work with. |
tableName |
null
|
Producer | The name of the table currently worked with. |
readCapacity |
0
|
Producer | The provisioned throughput to reserve for reading resources from your table |
writeCapacity |
0
|
Producer | The provisioned throughput to reserved for writing resources to your table |
consistentRead |
false
|
Producer | Determines whether or not strong consistency should be enforced when data is read. |
operation |
PutAttributes
|
Producer | Valid values are BatchGetItems, DeleteItem, DeleteTable, DescribeTable, GetItem, PutItem, Query, Scan, UpdateItem, UpdateTable. |
Usage Copier lienLien copié sur presse-papiers!
Message headers evaluated by the DDB producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbBatchItems
|
Map<String, KeysAndAttributes>
|
A map of the table name and corresponding items to get by primary key. |
CamelAwsDdbTableName
|
String
|
Table Name for this operation. |
CamelAwsDdbKey
|
Key
|
The primary key that uniquely identifies each item in a table. |
CamelAwsDdbReturnValues
|
String
|
Use this parameter if you want to get the attribute name-value pairs before or after they are modified(NONE, ALL_OLD, UPDATED_OLD, ALL_NEW, UPDATED_NEW). |
CamelAwsDdbUpdateCondition
|
Map<String, ExpectedAttributeValue>
|
Designates an attribute for a conditional modification. |
CamelAwsDdbAttributeNames
|
Collection<String>
|
If attribute names are not specified then all attributes will be returned. |
CamelAwsDdbConsistentRead
|
Boolean
|
If set to true, then a consistent read is issued, otherwise eventually consistent is used. |
CamelAwsDdbItem
|
Map<String, AttributeValue>
|
A map of the attributes for the item, and must include the primary key values that define the item. |
CamelAwsDdbExactCount
|
Boolean
|
If set to true, Amazon DynamoDB returns a total number of items that match the query parameters, instead of a list of the matching items and their attributes. |
CamelAwsDdbStartKey
|
Key
|
Primary key of the item from which to continue an earlier query. |
CamelAwsDdbHashKeyValue
|
AttributeValue
|
Value of the hash component of the composite primary key. |
CamelAwsDdbLimit
|
Integer
|
The maximum number of items to return. |
CamelAwsDdbScanRangeKeyCondition
|
Condition
|
A container for the attribute values and comparison operators to use for the query. |
CamelAwsDdbScanIndexForward
|
Boolean
|
Specifies forward or backward traversal of the index. |
CamelAwsDdbScanFilter
|
Map<String, Condition>
|
Evaluates the scan results and returns only the desired values. |
CamelAwsDdbUpdateValues
|
Map<String, AttributeValueUpdate>
|
Map of attribute name to the new value and action for the update. |
Message headers set during BatchGetItems operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbBatchResponse
|
Map<String,BatchResponse>
|
Table names and the respective item attributes from the tables. |
CamelAwsDdbUnprocessedKeys
|
Map<String,KeysAndAttributes>
|
Contains a map of tables and their respective keys that were not processed with the current response. |
Message headers set during DeleteItem operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbAttributes
|
Map<String, AttributeValue>
|
The list of attributes returned by the operation. |
Message headers set during DeleteTable operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbProvisionedThroughput
|
ProvisionedThroughputDescription
|
The value of the ProvisionedThroughput property for this table |
CamelAwsDdbCreationDate
|
Date
|
Creation DateTime of this table. |
CamelAwsDdbTableItemCount
|
Long
|
Item count for this table. |
CamelAwsDdbKeySchema
|
KeySchema
|
The KeySchema that identifies the primary key for this table. |
CamelAwsDdbTableName
|
String
|
The table name. |
CamelAwsDdbTableSize
|
Long
|
The table size in bytes. |
CamelAwsDdbTableStatus
|
String
|
The status of the table: CREATING, UPDATING, DELETING, ACTIVE |
Message headers set during DescribeTable operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbProvisionedThroughput
|
{{ProvisionedThroughputDescription} | The value of the ProvisionedThroughput property for this table |
CamelAwsDdbCreationDate
|
Date
|
Creation DateTime of this table. |
CamelAwsDdbTableItemCount
|
Long
|
Item count for this table. |
CamelAwsDdbKeySchema
|
{{KeySchema | The KeySchema that identifies the primary key for this table. |
CamelAwsDdbTableName
|
String
|
The table name. |
CamelAwsDdbTableSize
|
Long
|
The table size in bytes. |
CamelAwsDdbTableStatus
|
String
|
The status of the table: CREATING, UPDATING, DELETING, ACTIVE |
CamelAwsDdbReadCapacity
|
Long
|
ReadCapacityUnits property of this table. |
CamelAwsDdbWriteCapacity
|
Long
|
WriteCapacityUnits property of this table. |
Message headers set during GetItem operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbAttributes
|
Map<String, AttributeValue>
|
The list of attributes returned by the operation. |
Message headers set during PutItem operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbAttributes
|
Map<String, AttributeValue>
|
The list of attributes returned by the operation. |
Message headers set during Query operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbItems
|
List<java.util.Map<String,AttributeValue>>
|
The list of attributes returned by the operation. |
CamelAwsDdbLastEvaluatedKey
|
Key
|
Primary key of the item where the query operation stopped, inclusive of the previous result set. |
CamelAwsDdbConsumedCapacity
|
Double
|
The number of Capacity Units of the provisioned throughput of the table consumed during the operation. |
CamelAwsDdbCount
|
Integer
|
Number of items in the response. |
Message headers set during Scan operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbItems
|
List<java.util.Map<String,AttributeValue>>
|
The list of attributes returned by the operation. |
CamelAwsDdbLastEvaluatedKey
|
Key
|
Primary key of the item where the query operation stopped, inclusive of the previous result set. |
CamelAwsDdbConsumedCapacity
|
Double
|
The number of Capacity Units of the provisioned throughput of the table consumed during the operation. |
CamelAwsDdbCount
|
Integer
|
Number of items in the response. |
CamelAwsDdbScannedCount
|
Integer
|
Number of items in the complete scan before any filters are applied. |
Message headers set during UpdateItem operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsDdbAttributes
|
Map<String, AttributeValue>
|
The list of attributes returned by the operation. |
Advanced AmazonDynamoDB configuration Copier lienLien copié sur presse-papiers!
AmazonDynamoDBClient
configuration you can create your own instance and refer to it from the URI:
from("direct:start") .to("aws-ddb://domainName?amazonDDBClient=#amazonDDBClient");
from("direct:start")
.to("aws-ddb://domainName?amazonDDBClient=#amazonDDBClient");
Dependencies Copier lienLien copié sur presse-papiers!
${camel-version}
must be replaced by the actual version of Camel (2.10 or higher).
8.3. AWS-S3 Copier lienLien copié sur presse-papiers!
S3 Component Copier lienLien copié sur presse-papiers!
URI Format Copier lienLien copié sur presse-papiers!
aws-s3://bucket-name[?options]
aws-s3://bucket-name[?options]
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
amazonS3Client |
null
|
Shared |
Reference to a com.amazonaws.services.sqs.AmazonS3Client in the Registry.
|
accessKey |
null
|
Shared | Amazon AWS Access Key |
secretKey |
null
|
Shared | Amazon AWS Secret Key |
amazonS3Endpoint |
null
|
Shared | The region with which the AWS-S3 client wants to work with. |
region |
null
|
Producer |
The region who the bucket is located. This option is used in the com.amazonaws.services.s3.model.CreateBucketRequest .
|
deleteAfterRead |
true
|
Consumer | Delete objects from S3 after it has been retrieved. |
maxMessagesPerPoll | 10 | Consumer |
The maximum number of objects which can be retrieved in one poll. Used in in the com.amazonaws.services.s3.model.ListObjectsRequest .
|
policy |
null
|
Shared |
*Camel 2.8.4*: The policy for this queue to set in the com.amazonaws.services.s3.AmazonS3#setBucketPolicy() method.
|
storageClass |
null
|
Producer |
*Camel 2.8.4*: The storage class to set in the com.amazonaws.services.s3.model.PutObjectRequest request.
|
prefix |
null
|
Consumer |
*Camel 2.10.1*: The prefix which is used in the com.amazonaws.services.s3.model.ListObjectsRequest to only consume objects we are interested in.
|
Batch Consumer Copier lienLien copié sur presse-papiers!
Usage Copier lienLien copié sur presse-papiers!
Message headers evaluated by the S3 producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsS3Key
|
String
|
The key under which this object will be stored. |
CamelAwsS3ContentLength
|
Long
|
The content length of this object. |
CamelAwsS3ContentType
|
String
|
The content type of this object. |
CamelAwsS3ContentControl
|
String
|
*Camel 2.8.2:* The content control of this object. |
CamelAwsS3ContentDisposition
|
String
|
*Camel 2.8.2:* The content disposition of this object. |
CamelAwsS3ContentEncoding
|
String
|
*Camel 2.8.2:* The content encoding of this object. |
CamelAwsS3ContentMD5
|
String
|
*Camel 2.8.2:* The md5 checksum of this object. |
CamelAwsS3LastModified
|
java.util.Date
|
*Camel 2.8.2:* The last modified timestamp of this object. |
CamelAwsS3StorageClass
|
String
|
*Camel 2.8.4:* The storage class of this object. |
Message headers set by the S3 producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsS3ETag
|
String
|
The ETag value for the newly uploaded object. |
CamelAwsS3VersionId
|
String
|
The optional version ID of the newly uploaded object. |
Message headers set by the S3 consumer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsS3Key
|
String
|
The key under which this object is stored. |
CamelAwsS3BucketName
|
String
|
The name of the bucket in which this object is contained. |
CamelAwsS3ETag
|
String
|
The hex encoded 128-bit MD5 digest of the associated object according to RFC 1864. This data is used as an integrity check to verify that the data received by the caller is the same data that was sent by Amazon S3. |
CamelAwsS3LastModified
|
Date
|
The value of the Last-Modified header, indicating the date and time at which Amazon S3 last recorded a modification to the associated object. |
CamelAwsS3VersionId
|
String
|
The version ID of the associated Amazon S3 object if available. Version IDs are only assigned to objects when an object is uploaded to an Amazon S3 bucket that has object versioning enabled. |
CamelAwsS3ContentType
|
String
|
The Content-Type HTTP header, which indicates the type of content stored in the associated object. The value of this header is a standard MIME type. |
CamelAwsS3ContentMD5
|
String
|
The base64 encoded 128-bit MD5 digest of the associated object (content - not including headers) according to RFC 1864. This data is used as a message integrity check to verify that the data received by Amazon S3 is the same data that the caller sent. |
CamelAwsS3ContentLength
|
Long
|
The Content-Length HTTP header indicating the size of the associated object in bytes. |
CamelAwsS3ContentEncoding
|
String
|
The optional Content-Encoding HTTP header specifying what content encodings have been applied to the object and what decoding mechanisms must be applied in order to obtain the media-type referenced by the Content-Type field. |
CamelAwsS3ContentDisposition
|
String
|
The optional Content-Disposition HTTP header, which specifies presentational information such as the recommended filename for the object to be saved as. |
CamelAwsS3ContentControl
|
String
|
The optional Cache-Control HTTP header which allows the user to specify caching behavior along the HTTP request/reply chain. |
Advanced AmazonS3Client configuration Copier lienLien copié sur presse-papiers!
from("aws-s3://MyBucket?amazonS3Client=#amazonS3Client&delay=5000&maxMessagesPerPoll=5") .to("mock:result");
from("aws-s3://MyBucket?amazonS3Client=#amazonS3Client&delay=5000&maxMessagesPerPoll=5")
.to("mock:result");
Dependencies Copier lienLien copié sur presse-papiers!
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-aws</artifactId> <version>${camel-version}</version> </dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-aws</artifactId>
<version>${camel-version}</version>
</dependency>
$\{camel-version\}
must be replaced by the actual version of Camel (2.8 or higher).
8.4. AWS-SDB Copier lienLien copié sur presse-papiers!
SDB Component Copier lienLien copié sur presse-papiers!
URI Format Copier lienLien copié sur presse-papiers!
aws-sdb://domainName[?options]
aws-sdb://domainName[?options]
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
amazonSDBClient |
null
|
Producer |
Reference to a com.amazonaws.services.simpledb.AmazonSimpleDB in the Registry.
|
accessKey |
null
|
Producer | Amazon AWS Access Key |
secretKey |
null
|
Producer | Amazon AWS Secret Key |
amazonSdbEndpoint |
null
|
Producer | The region with which the AWS-SDB client wants to work with. |
domainName |
null
|
Producer | The name of the domain currently worked with. |
maxNumberOfDomains |
100
|
Producer | The maximum number of domain names you want returned. The range is 1 * to 100. |
consistentRead |
false
|
Producer | Determines whether or not strong consistency should be enforced when data is read. |
operation |
PutAttributes
|
Producer | Valid values are BatchDeleteAttributes, BatchPutAttributes, DeleteAttributes, DeleteDomain, DomainMetadata, GetAttributes, ListDomains, PutAttributes, Select. |
Usage Copier lienLien copié sur presse-papiers!
Message headers evaluated by the SDB producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSdbAttributes
|
Collection<Attribute>
|
List of attributes to be acted upon. |
CamelAwsSdbAttributeNames
|
Collection<String>
|
The names of the attributes to be retrieved. |
CamelAwsSdbConsistentRead
|
Boolean
|
Determines whether or not strong consistency should be enforced when data is read. |
CamelAwsSdbDeletableItems
|
Collection<DeletableItem>
|
A list of items on which to perform the delete operation in a batch. |
CamelAwsSdbDomainName
|
String
|
The name of the domain currently worked with. |
CamelAwsSdbItemName
|
String
|
The unique key for this item |
CamelAwsSdbMaxNumberOfDomains
|
Integer
|
The maximum number of domain names you want returned. The range is 1 * to 100. |
CamelAwsSdbNextToken
|
String
|
A string specifying where to start the next list of domain/item names. |
CamelAwsSdbOperation
|
String
|
To override the operation from the URI options. |
CamelAwsSdbReplaceableAttributes
|
Collection<ReplaceableAttribute>
|
List of attributes to put in an Item. |
CamelAwsSdbReplaceableItems
|
Collection<ReplaceableItem>
|
A list of items to put in a Domain. |
CamelAwsSdbSelectExpression
|
String
|
The expression used to query the domain. |
CamelAwsSdbUpdateCondition
|
String
|
The update condition which, if specified, determines whether the specified attributes will be updated/deleted or not. |
Message headers set during DomainMetadata operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSdbTimestamp
|
Integer
|
The data and time when metadata was calculated, in Epoch (UNIX) seconds. |
CamelAwsSdbItemCount
|
Integer
|
The number of all items in the domain. |
CamelAwsSdbAttributeNameCount
|
Integer
|
The number of unique attribute names in the domain. |
CamelAwsSdbAttributeValueCount
|
Integer
|
The number of all attribute name/value pairs in the domain. |
CamelAwsSdbAttributeNameSize
|
Long
|
The total size of all unique attribute names in the domain, in bytes. |
CamelAwsSdbAttributeValueSize
|
Long
|
The total size of all attribute values in the domain, in bytes. |
CamelAwsSdbItemNameSize
|
Long
|
The total size of all item names in the domain, in bytes. |
Message headers set during GetAttributes operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSdbAttributes
|
List<Attribute>
|
The list of attributes returned by the operation. |
Message headers set during ListDomains operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSdbDomainNames
|
List<String>
|
A list of domain names that match the expression. |
CamelAwsSdbNextToken
|
String
|
An opaque token indicating that there are more domains than the specified MaxNumberOfDomains still available. |
Message headers set during Select operation Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSdbItems
|
List<Item>
|
A list of items that match the select expression. |
CamelAwsSdbNextToken
|
String
|
An opaque token indicating that more items than MaxNumberOfItems were matched, the response size exceeded 1 megabyte, or the execution time exceeded 5 seconds. |
Advanced AmazonSimpleDBClient configuration Copier lienLien copié sur presse-papiers!
AmazonSimpleDBClient
configuration you can create your own instance and refer to it from the URI:
from("direct:start") .to("aws-sdb://domainName?amazonSDBClient=#amazonSDBClient");
from("direct:start")
.to("aws-sdb://domainName?amazonSDBClient=#amazonSDBClient");
Dependencies Copier lienLien copié sur presse-papiers!
${camel-version}
must be replaced by the actual version of Camel (2.8.4 or higher).
8.5. AWS-SES Copier lienLien copié sur presse-papiers!
SES Component Copier lienLien copié sur presse-papiers!
URI Format Copier lienLien copié sur presse-papiers!
aws-ses://from[?options]
aws-ses://from[?options]
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
amazonSESClient |
null
|
Producer |
Reference to a com.amazonaws.services.simpleemail.AmazonSimpleEmailServiceClient in the Registry.
|
accessKey |
null
|
Producer | Amazon AWS Access Key |
secretKey |
null
|
Producer | Amazon AWS Secret Key |
amazonSESEndpoint |
null
|
Producer | The region with which the AWS-SES client wants to work with. |
subject |
null
|
Producer | The subject which is used if the message header 'CamelAwsSesSubject' is not present. |
to |
null
|
Producer | List of destination email address. Can be overriden with 'CamelAwsSesTo' header. |
returnPath |
null
|
Producer | The email address to which bounce notifications are to be forwarded, override it using 'CamelAwsSesReturnPath' header. |
replyToAddresses |
null
|
Producer | List of reply-to email address(es) for the message, override it using 'CamelAwsSesReplyToAddresses' header. |
Usage Copier lienLien copié sur presse-papiers!
Message headers evaluated by the SES producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSesFrom
|
String
|
The sender's email address. |
CamelAwsSesTo
|
List<String>
|
The destination(s) for this email. |
CamelAwsSesSubject
|
String
|
The subject of the message. |
CamelAwsSesReplyToAddresses
|
List<String>
|
The reply-to email address(es) for the message. |
CamelAwsSesReturnPath
|
String
|
The email address to which bounce notifications are to be forwarded. |
Message headers set by the SES producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSesMessageId
|
String
|
The Amazon SES message ID. |
Advanced AmazonSimpleEmailServiceClient configuration Copier lienLien copié sur presse-papiers!
AmazonSimpleEmailServiceClient
configuration you can create your own instance and refer to it from the URI:
from("direct:start") .to("aws-ses://example@example.com?amazonSESClient=#amazonSESClient");
from("direct:start")
.to("aws-ses://example@example.com?amazonSESClient=#amazonSESClient");
Dependencies Copier lienLien copié sur presse-papiers!
${camel-version}
must be replaced by the actual version of Camel (2.8.4 or higher).
8.6. AWS-SNS Copier lienLien copié sur presse-papiers!
SNS Component Copier lienLien copié sur presse-papiers!
URI Format Copier lienLien copié sur presse-papiers!
aws-sns://topicName[?options]
aws-sns://topicName[?options]
?options=value&option2=value&...
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
amazonSNSClient |
null
|
Producer |
Reference to a com.amazonaws.services.sqs.AmazonSNSClient in the Registry.
|
accessKey |
null
|
Producer | Amazon AWS Access Key |
secretKey |
null
|
Producer | Amazon AWS Secret Key |
subject |
null
|
Producer | The subject which is used if the message header 'CamelAwsSnsSubject' is not present. |
amazonSNSEndpoint |
null
|
Producer | The region with which the AWS-SNS client wants to work with. |
policy |
null
|
Producer |
*Camel 2.8.4*: The policy for this queue to set in the com.amazonaws.services.sns.model.SetTopicAttributesRequest .
|
Usage Copier lienLien copié sur presse-papiers!
Message headers evaluated by the SNS producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSnsSubject
|
String
|
The Amazon SNS message subject. If not set, the subject from the SnsConfiguration is used.
|
Message headers set by the SNS producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSnsMessageId
|
String
|
The Amazon SNS message ID. |
Advanced AmazonSNSClient configuration Copier lienLien copié sur presse-papiers!
AmazonSNSClient
configuration you can create your own instance and refer to it from the URI:
from("direct:start") .to("aws-sns://MyTopic?amazonSNSClient=#amazonSNSClient");
from("direct:start")
.to("aws-sns://MyTopic?amazonSNSClient=#amazonSNSClient");
Dependencies Copier lienLien copié sur presse-papiers!
$\{camel-version\}
must be replaced by the actual version of Camel (2.8 or higher).
8.7. AWS-SQS Copier lienLien copié sur presse-papiers!
SQS Component Copier lienLien copié sur presse-papiers!
URI Format Copier lienLien copié sur presse-papiers!
aws-sqs://queue-name[?options]
aws-sqs://queue-name[?options]
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
amazonSQSClient |
null
|
Shared |
Reference to a com.amazonaws.services.sqs.AmazonSQSClient in the Registry.
|
accessKey |
null
|
Shared | Amazon AWS Access Key |
secretKey |
null
|
Shared | Amazon AWS Secret Key |
amazonSQSEndpoint |
null
|
Shared | The region with which the AWS-SQS client wants to work with. |
attributeNames |
null
|
Consumer |
A list of attributes to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest .
|
defaultVisibilityTimeout |
null
|
Shared |
The visibility timeout (in seconds) to set in the com.amazonaws.services.sqs.model.CreateQueueRequest .
|
deleteAfterRead |
true
|
Consumer | Delete message from SQS after it has been read |
maxMessagesPerPoll |
null
|
Consumer |
The maximum number of messages which can be received in one poll to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest .
|
visibilityTimeout |
null
|
Shared |
The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest . This only make sense if its different from defaultVisibilityTimeout . It changes the queue visibility timeout attribute permanently.
|
messageVisibilityTimeout |
null
|
Consumer |
Camel 2.8: The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest . It does NOT change the queue visibility timeout attribute permanently.
|
extendMessageVisibility |
false
|
Consumer | *Camel 2.10:* If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it taks a long time to process the message. See details at Amazon docs. |
maximumMessageSize |
null
|
Shared |
Camel 2.8: The maximumMessageSize (in bytes) an SQS message can contain for this queue, to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest .
|
messageRetentionPeriod |
null
|
Shared |
Camel 2.8: The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue, to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest .
|
policy |
null
|
Shared |
Camel 2.8: The policy for this queue to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest .
|
delaySeconds |
null
|
Producer | *Camel 2.9.3:* Delay sending messages for a number of seconds. |
Batch Consumer Copier lienLien copié sur presse-papiers!
Usage Copier lienLien copié sur presse-papiers!
Message headers set by the SQS producer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSqsMD5OfBody
|
String
|
The MD5 checksum of the Amazon SQS message. |
CamelAwsSqsMessageId
|
String
|
The Amazon SQS message ID. |
Message headers set by the SQS consumer Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelAwsSqsMD5OfBody
|
String
|
The MD5 checksum of the Amazon SQS message. |
CamelAwsSqsMessageId
|
String
|
The Amazon SQS message ID. |
CamelAwsSqsReceiptHandle
|
String
|
The Amazon SQS message receipt handle. |
CamelAwsSqsAttributes
|
Map<String, String>
|
The Amazon SQS message attributes. |
Advanced AmazonSQSClient configuration Copier lienLien copié sur presse-papiers!
from("aws-sqs://MyQueue?amazonSQSClient=#amazonSQSClient&delay=5000&maxMessagesPerPoll=5") .to("mock:result");
from("aws-sqs://MyQueue?amazonSQSClient=#amazonSQSClient&delay=5000&maxMessagesPerPoll=5")
.to("mock:result");
Dependencies Copier lienLien copié sur presse-papiers!
$\{camel-version\}
must be replaced by the actual version of Camel (2.6 or higher).
Chapter 9. Bean Copier lienLien copié sur presse-papiers!
Bean Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
bean:beanID[?options]
bean:beanID[?options]
Options Copier lienLien copié sur presse-papiers!
Name | Type | Default | Description |
---|---|---|---|
method
|
String
|
null
|
The method name from the bean that will be invoked. If not provided, Camel will try to determine the method itself. In case of ambiguity an exception will be thrown. See Bean Binding for more details. |
cache
|
boolean
|
false
|
If enabled, Apache Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope. |
?option=value&option=value&...
Using Copier lienLien copié sur presse-papiers!
spring.xml
; or if you don't use Spring, put the bean in JNDI.
createProxy()
methods on ProxyHelper to create a proxy that will generate BeanExchanges and send them to any endpoint:
Endpoint endpoint = camelContext.getEndpoint("direct:hello"); ISay proxy = ProxyHelper.createProxy(endpoint, ISay.class); String rc = proxy.say(); assertEquals("Good Bye!", rc);
Endpoint endpoint = camelContext.getEndpoint("direct:hello");
ISay proxy = ProxyHelper.createProxy(endpoint, ISay.class);
String rc = proxy.say();
assertEquals("Good Bye!", rc);
<route> <from uri="direct:hello"> <to uri="bean:bye"/> </route>
<route>
<from uri="direct:hello">
<to uri="bean:bye"/>
</route>
Bean as endpoint Copier lienLien copié sur presse-papiers!
myBean
, Apache Camel will use the Bean Binding to invoke the bean. The source for the bean is just a plain POJO:
sayHello
method, by converting the Exchange's In body to the String
type and storing the output of the method on the Exchange Out body.
Java DSL bean syntax Copier lienLien copié sur presse-papiers!
to("bean:beanName")
) you can use the following syntax:
Bean Binding Copier lienLien copié sur presse-papiers!
- Class component
Chapter 10. Bean Validation Copier lienLien copié sur presse-papiers!
Bean Validation Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
bean-validator:something[?options]
bean-validator:something[?options]
bean-validator://something[?options]
bean-validator://something[?options]
?option=value&option=value&...
URI Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
group
|
javax.validation.groups.Default
|
The custom validation group to use. |
messageInterpolator
|
org.hibernate.validator.engine. ResourceBundleMessageInterpolator
|
Reference to a custom javax.validation.MessageInterpolator in the Registry.
|
traversableResolver
|
org.hibernate.validator.engine.resolver. DefaultTraversableResolver
|
Reference to a custom javax.validation.TraversableResolver in the Registry.
|
constraintValidatorFactory
|
org.hibernate.validator.engine. ConstraintValidatorFactoryImpl
|
Reference to a custom javax.validation.ConstraintValidatorFactory in the Registry.
|
Example Copier lienLien copié sur presse-papiers!
public interface OptionalChecks { }
public interface OptionalChecks {
}
javax.validation.groups.Default
).
from("direct:start") .to("bean-validator://x") .to("mock:end")
from("direct:start")
.to("bean-validator://x")
.to("mock:end")
OptionalChecks
, you have to define the route like this
from("direct:start") .to("bean-validator://x?group=OptionalChecks") .to("mock:end")
from("direct:start")
.to("bean-validator://x?group=OptionalChecks")
.to("mock:end")
@GroupSequence({Default.class, OptionalChecks.class}) public interface AllChecks { }
@GroupSequence({Default.class, OptionalChecks.class})
public interface AllChecks {
}
from("direct:start") .to("bean-validator://x?group=AllChecks") .to("mock:end")
from("direct:start")
.to("bean-validator://x?group=AllChecks")
.to("mock:end")
META-INF/validation.xml
which could looks like this
constraints-car.xml
file
Chapter 11. Browse Copier lienLien copié sur presse-papiers!
Browse Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
browse:someName
browse:someName
Sample Copier lienLien copié sur presse-papiers!
browse:
component to be able to browse the Exchanges that are passing through:
from("activemq:order.in").to("browse:orderReceived").to("bean:processOrder");
from("activemq:order.in").to("browse:orderReceived").to("bean:processOrder");
Chapter 12. Cache Copier lienLien copié sur presse-papiers!
12.1. Cache Component Copier lienLien copié sur presse-papiers!
Available as of Camel 2.1 Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
cache://cacheName[?options]
cache://cacheName[?options]
?option=value&option=#beanRef&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
maxElementsInMemory
|
1000
|
The number of elements that may be stored in the defined cache |
memoryStoreEvictionPolicy
|
MemoryStoreEvictionPolicy.LFU
|
The number of elements that may be stored in the defined cache. Options include
|
overflowToDisk
|
true
|
Specifies whether cache may overflow to disk |
eternal
|
false
|
Sets whether elements are eternal. If eternal, timeouts are ignored and the element never expires.
|
timeToLiveSeconds
|
300
|
The maximum time between creation time and when an element expires. Is used only if the element is not eternal
|
timeToIdleSeconds
|
300
|
The maximum amount of time between accesses before an element expires |
diskPersistent
|
false
|
Whether the disk store persists between restarts of the Virtual Machine. |
diskExpiryThreadIntervalSeconds
|
120
|
The number of seconds between runs of the disk expiry thread. |
cacheManagerFactory
|
null
|
*Camel 2.8:* If you want to use a custom factory which instantiates and creates the EHCache net.sf.ehcache.CacheManager . Type: abstract org.apache.camel.component.cache.CacheManagerFactory
|
eventListenerRegistry
|
null
|
*Camel 2.8:* Sets a list of EHCache net.sf.ehcache.event.CacheEventListener for all new caches\- no need to define it per cache in EHCache xml config anymore. Type: org.apache.camel.component.cache.CacheEventListenerRegistry
|
cacheLoaderRegistry
|
null
|
*Camel 2.8:* Sets a list of org.apache.camel.component.cache.CacheLoaderWrapper that extends EHCache net.sf.ehcache.loader.CacheLoader for all new caches\- no need to define it per cache in EHCache xml config anymore. Type: org.apache.camel.component.cache.CacheLoaderRegistry
|
key
|
null
|
*Camel 2.10:* To configure using a cache key by default. If a key is provided in the message header, then the key from the header takes precedence. |
operation
|
null
|
*Camel 2.10:* To configure using an cache operation by default. If an operation in the message header, then the operation from the header takes precedence. |
Message Headers Camel 2.8\+ Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelCacheOperation
|
The operation to be performed on the cache. The valid options are
|
CamelCacheKey
|
The cache key used to store the Message in the cache. The cache key is optional if the CamelCacheOperation is CamelCacheDeleteAll
|
CamelCacheAdd
and CamelCacheUpdate
operations support additional headers:
Header | Type | Description |
---|---|---|
CamelCacheTimeToLive
|
Integer
|
*Camel 2.11:* Time to live in seconds. |
CamelCacheTimeToIdle
|
Integer
|
*Camel 2.11:* Time to idle in seconds. |
CamelCacheEternal
|
Boolean
|
*Camel 2.11:* Whether the content is eternal. |
Cache Producer Copier lienLien copié sur presse-papiers!
- setting the Message Exchange Headers shown above.
- ensuring that the Message Exchange Body contains the message directed to the cache
Cache Consumer Copier lienLien copié sur presse-papiers!
- an exchange containing Message Exchange Headers and a Message Exchange Body containing the just added/updated payload is placed and sent.
- in case of a CamelCacheDeleteAll operation, the Message Exchange Header CamelCacheKey and the Message Exchange Body are not populated.
Cache Processors Copier lienLien copié sur presse-papiers!
- body
- token
- xpath level
Example 1: Configuring the cache Copier lienLien copié sur presse-papiers!
Example 2: Adding keys to the cache Copier lienLien copié sur presse-papiers!
Example 2: Updating existing keys in a cache Copier lienLien copié sur presse-papiers!
Example 3: Deleting existing keys in a cache Copier lienLien copié sur presse-papiers!
Example 4: Deleting all existing keys in a cache Copier lienLien copié sur presse-papiers!
Example 5: Notifying any changes registering in a Cache to Processors and other Producers Copier lienLien copié sur presse-papiers!
Example 6: Using Processors to selectively replace payload with cache values Copier lienLien copié sur presse-papiers!
Example 7: Getting an entry from the Cache Copier lienLien copié sur presse-papiers!
Example 8: Checking for an entry in the Cache Copier lienLien copié sur presse-papiers!
Management of EHCache Copier lienLien copié sur presse-papiers!
ManagementService.registerMBeans(CacheManager.getInstance(), mbeanServer, true, true, true, true);
ManagementService.registerMBeans(CacheManager.getInstance(), mbeanServer, true, true, true, true);
Cache replication Camel 2.8\+ Copier lienLien copié sur presse-papiers!
- You can configure
ehcache.xml
manually, or - You can configure these three options:
- cacheManagerFactory
- eventListenerRegistry
- cacheLoaderRegistry
ehcache.xml
is not a good idea.
CacheManager
and per CacheEndpoint
. Also it is the only way when cache names are not know at the development phase.
Example: JMS cache replication Copier lienLien copié sur presse-papiers!
12.2. cacheReplicationJMSExample Copier lienLien copié sur presse-papiers!
Example: JMS cache replication Copier lienLien copié sur presse-papiers!
CacheManagerFactory
.
CacheLoaderWrapper
, the easiest one is:
- cacheManagerFactory
- eventListenerRegistry
- cacheLoaderRegistry
Chapter 13. CDI Copier lienLien copié sur presse-papiers!
Camel CDI Copier lienLien copié sur presse-papiers!
Dependency Injecting Camel with CDI Copier lienLien copié sur presse-papiers!
Bootstrapping Camel with CDI container Copier lienLien copié sur presse-papiers!
@Singleton @Startup public class BootStrap { ...
@Singleton
@Startup
public class BootStrap {
...
See Also Copier lienLien copié sur presse-papiers!
- Simple Camel CDI BootStrap project
- Apache DeltaSpike project - CDI extensions and JavaSE BootStrap
- Apache implementation of the specs JSR299, 330 - OpenWebbeans and Apache OpenEJB which provide the container to deploy CDI projects
- Apache Karaf featured with OpenEJB and CDI - Apache KarafEE
Chapter 14. Class Copier lienLien copié sur presse-papiers!
Class Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
class:className[?options]
class:className[?options]
Options Copier lienLien copié sur presse-papiers!
Name | Type | Default | Description |
---|---|---|---|
method
|
String
|
null
|
The method name that bean will be invoked. If not provided, Apache Camel will try to pick the method itself. In case of ambiguity an exception is thrown. See Bean Binding for more details. |
multiParameterArray
|
boolean
|
false
|
How to treat the parameters which are passed from the message body; if it is true , the In message body should be an array of parameters.
|
?option=value&option=value&...
Using Copier lienLien copié sur presse-papiers!
MyFooBean
you have to do as follows:
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
MyFooBean
, for example hello
:
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean?method=hello").to("mock:result");
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean?method=hello").to("mock:result");
Setting properties on the created instance Copier lienLien copié sur presse-papiers!
setPrefix
method:
from("direct:start") .to("class:org.apache.camel.component.bean.MyPrefixBean?prefix=Bye") .to("mock:result");
from("direct:start")
.to("class:org.apache.camel.component.bean.MyPrefixBean?prefix=Bye")
.to("mock:result");
#
syntax to refer to properties to be looked up in the Registry.
from("direct:start") .to("class:org.apache.camel.component.bean.MyPrefixBean?cool=#foo") .to("mock:result");
from("direct:start")
.to("class:org.apache.camel.component.bean.MyPrefixBean?cool=#foo")
.to("mock:result");
foo
and invoke the setCool
method on the created instance of the MyPrefixBean
class.
Chapter 15. Cometd Copier lienLien copié sur presse-papiers!
Cometd Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
cometd://host:port/channelName[?options]
cometd://host:port/channelName[?options]
Examples Copier lienLien copié sur presse-papiers!
cometd://localhost:8080/service/mychannel cometds://localhost:8443/service/mychannel
cometd://localhost:8080/service/mychannel
cometds://localhost:8443/service/mychannel
cometds:
represents an SSL configured endpoint.
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
resourceBase
|
The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | |
baseResource
|
*Camel 2.7:* The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar | |
timeout
|
240000
|
The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding. |
interval
|
0
|
The client side poll timeout in milliseconds. How long a client will wait between reconnects |
maxInterval
|
30000
|
The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time. |
multiFrameInterval
|
1500
|
The client side poll timeout, if multiple connections are detected from the same browser. |
jsonCommented
|
true
|
If true , the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.
|
logLevel
|
1
|
0 =none, 1 =info, 2 =debug.
|
sslContextParameters |
*Camel 2.9:* Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
|
|
crossOriginFilterOn
|
false
|
*Camel 2.10:* If true , the server will support for cross-domain filtering
|
allowedOrigins
|
*
|
*Camel 2.10:* The origins domain that support to cross, if the crosssOriginFilterOn is true
|
filterPath
|
*Camel 2.10:* The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true
|
?option=value&option=value&...
cometd://localhost:8080?resourceBase=file./webapp
. For classpath (when the web resources are packaged inside the Webapp folder) cometd://localhost:8080?resourceBase=classpath:webapp
.
Authentication Copier lienLien copié sur presse-papiers!
SecurityPolicy
and Extension
's to the CometdComponent
which allows you to use authentication as documented here
Setting up SSL for Cometd Component Copier lienLien copié sur presse-papiers!
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
Programmatic configuration of the component Copier lienLien copié sur presse-papiers!
Spring DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
Chapter 16. Context Copier lienLien copié sur presse-papiers!
Context Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
context:camelContextId:localEndpointName[?options]
context:camelContextId:localEndpointName[?options]
camelContextId:localEndpointName[?options]
camelContextId:localEndpointName[?options]
- camelContextId is the ID you used to register the CamelContext into the Registry.
- localEndpointName can be a valid Camel URI evaluated within the black box CamelContext. Or it can be a logical name which is mapped to any local endpoints. For example if you locally have endpoints like direct:invoices and seda:purchaseOrders inside a CamelContext of id supplyChain, then you can just use the URIs supplyChain:invoices or supplyChain:purchaseOrders to omit the physical endpoint kind and use pure logical URIs.
?option=value&option=value&...
Example Copier lienLien copié sur presse-papiers!
Defining the context component Copier lienLien copié sur presse-papiers!
Using the context component Copier lienLien copié sur presse-papiers!
Naming endpoints Copier lienLien copié sur presse-papiers!
Chapter 17. Crypto (Digital Signatures) Copier lienLien copié sur presse-papiers!
Crypto component for Digital Signatures Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
Introduction Copier lienLien copié sur presse-papiers!
- Bruce Schneier's Applied Cryptography
- Beginning Cryptography with Java by David Hook
- The ever insightful, Wikipedia Digital_signatures
URI format Copier lienLien copié sur presse-papiers!
crypto:sign:name[?options] crypto:verify:name[?options]
crypto:sign:name[?options]
crypto:verify:name[?options]
crypto:sign
creates the signature and stores it in the Header keyed by the constantExchange.SIGNATURE
, i.e."CamelDigitalSignature"
.crypto:verify
will read in the contents of this header and do the verification calculation.
PrivateKey
and verify a PublicKey
(or a Certificate
containing one). Using the JCE is is very simple to generate these key pairs but it is usually most secure to use a KeyStore to house and share your keys. The DSL is very flexible about how keys are supplied and provides a number of mechanisms.
crypto:sign
endpoint is typically defined in one route and the complimentary crypto:verify
in another, though for simplicity in the examples they appear one after the other. It goes without saying that both sign and verify should be configured identically.
Options Copier lienLien copié sur presse-papiers!
Name | Type | Default | Description |
---|---|---|---|
algorithm
|
String
|
DSA
|
The name of the JCE Signature algorithm that will be used. |
alias
|
String
|
null
|
An alias name that will be used to select a key from the keystore. |
bufferSize
|
Integer
|
2048
|
the size of the buffer used in the signature process. |
certificate
|
Certificate
|
null
|
A Certificate used to verify the signature of the exchange's payload. Either this or a Public Key is required. |
keystore
|
KeyStore
|
null
|
A reference to a JCE Keystore that stores keys and certificates used to sign and verify. |
provider
|
String
|
null
|
The name of the JCE Security Provider that should be used. |
privateKey
|
PrivatKey
|
null
|
The private key used to sign the exchange's payload. |
publicKey
|
PublicKey
|
null
|
The public key used to verify the signature of the exchange's payload. |
secureRandom
|
secureRandom
|
null
|
A reference to a SecureRandom object that wil lbe used to initialize the Signature service.
|
password
|
char[]
|
null
|
The password for the keystore. |
clearHeaders
|
String
|
true
|
Remove camel crypto headers from Message after a verify operation (value can be "true" /{{"false"}}).
|
1) Raw keys Copier lienLien copié sur presse-papiers!
from("direct:keypair").to("crypto:sign://basic?privateKey=#myPrivateKey", "crypto:verify://basic?publicKey=#myPublicKey", "mock:result");
from("direct:keypair").to("crypto:sign://basic?privateKey=#myPrivateKey", "crypto:verify://basic?publicKey=#myPublicKey", "mock:result");
2) KeyStores and Aliases. Copier lienLien copié sur presse-papiers!
from("direct:keystore").to("crypto:sign://keystore?keystore=#keystore&alias=bob&password=letmein", "crypto:verify://keystore?keystore=#keystore&alias=bob", "mock:result");
from("direct:keystore").to("crypto:sign://keystore?keystore=#keystore&alias=bob&password=letmein", "crypto:verify://keystore?keystore=#keystore&alias=bob", "mock:result");
3) Changing JCE Provider and Algorithm Copier lienLien copié sur presse-papiers!
from("direct:provider").to("crypto:sign://provider?privateKey=#myPrivateKey&provider=SUN", "crypto:verify://provider?publicKey=#myPublicKey&provider=SUN", "mock:result");
from("direct:provider").to("crypto:sign://provider?privateKey=#myPrivateKey&provider=SUN", "crypto:verify://provider?publicKey=#myPublicKey&provider=SUN", "mock:result");
4) Changing the Signature Mesasge Header Copier lienLien copié sur presse-papiers!
from("direct:signature-header").to("crypto:sign://another?privateKey=#myPrivateKey&signatureHeader=AnotherDigitalSignature", "crypto:verify://another?publicKey=#myPublicKey&signatureHeader=AnotherDigitalSignature", "mock:result");
from("direct:signature-header").to("crypto:sign://another?privateKey=#myPrivateKey&signatureHeader=AnotherDigitalSignature",
"crypto:verify://another?publicKey=#myPublicKey&signatureHeader=AnotherDigitalSignature", "mock:result");
5) Changing the buffersize Copier lienLien copié sur presse-papiers!
from("direct:buffersize").to("crypto:sign://buffer?privateKey=#myPrivateKey&buffersize=1024", "crypto:verify://buffer?publicKey=#myPublicKey&buffersize=1024", "mock:result");
from("direct:buffersize").to("crypto:sign://buffer?privateKey=#myPrivateKey&buffersize=1024", "crypto:verify://buffer?publicKey=#myPublicKey&buffersize=1024", "mock:result");
6) Supplying Keys dynamically. Copier lienLien copié sur presse-papiers!
Exchange.SIGNATURE_PRIVATE_KEY
,"CamelSignaturePrivateKey"
Exchange.SIGNATURE_PUBLIC_KEY_OR_CERT
,"CamelSignaturePublicKeyOrCert"
from("direct:headerkey-sign").to("crypto:sign://alias"); from("direct:headerkey-verify").to("crypto:verify://alias", "mock:result");
from("direct:headerkey-sign").to("crypto:sign://alias");
from("direct:headerkey-verify").to("crypto:verify://alias", "mock:result");
Exchange.KEYSTORE_ALIAS
,"CamelSignatureKeyStoreAlias"
from("direct:alias-sign").to("crypto:sign://alias?keystore=#keystore"); from("direct:alias-verify").to("crypto:verify://alias?keystore=#keystore", "mock:result");
from("direct:alias-sign").to("crypto:sign://alias?keystore=#keystore");
from("direct:alias-verify").to("crypto:verify://alias?keystore=#keystore", "mock:result");
- Crypto Crypto is also available as a Data Format
Chapter 18. CXF Copier lienLien copié sur presse-papiers!
CXF Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
WHICH-JARS
text file.
URI format Copier lienLien copié sur presse-papiers!
cxf:bean:cxfEndpoint[?options]
cxf:bean:cxfEndpoint[?options]
cxf://someAddress[?options]
cxf://someAddress[?options]
cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_world.wsdl&dataFormat=PAYLOAD
cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_world.wsdl&dataFormat=PAYLOAD
Options Copier lienLien copié sur presse-papiers!
Name | Required | Description |
---|---|---|
wsdlURL
|
No |
The location of the WSDL. WSDL is obtained from endpoint address by default. For example:
file://local/wsdl/hello.wsdl or wsdl/hello.wsdl
|
serviceClass
|
Yes |
The name of the SEI (Service Endpoint Interface) class. This class can have, but does not require, JSR181 annotations. Since 2.0, this option is only required by POJO mode. If the wsdlURL option is provided, serviceClass is not required for PAYLOAD and MESSAGE mode. When wsdlURL option is used without serviceClass, the serviceName and portName (endpointName for Spring configuration) options MUST be provided.
Since 2.0, it is possible to use
# notation to reference a serviceClass object instance from the registry..
Please be advised that the referenced object cannot be a Proxy (Spring AOP Proxy is OK) as it relies on
Object.getClass().getName() method for non Spring AOP Proxy.
Since 2.8, it is possible to omit both wsdlURL and serviceClass options for PAYLOAD and MESSAGE mode. When they are omitted, arbitrary XML elements can be put in CxfPayload's body in PAYLOAD mode to facilitate CXF Dispatch Mode.
For example:
org.apache.camel.Hello
|
serviceName
|
Only if more than one serviceName present in WSDL
|
The service name this service is implementing, it maps to the
wsdl:service@name . For example:
{http://org.apache.camel}ServiceName
|
portName
|
Only if more than one portName under the serviceName is present, and it is required for camel-cxf consumer since camel 2.2
|
The port name this service is implementing, it maps to the
wsdl:port@name . For example:
{http://org.apache.camel}PortName
|
dataFormat
|
No |
Which message data format the CXF endpoint supports. Possible values are: POJO (default), PAYLOAD , MESSAGE .
|
relayHeaders
|
No |
Please see the Description ofrelayHeaders *option* section for this option. Should a CXF endpoint relay headers along the route. Currently only available when dataFormat=POJO Default: true Example: true , false
|
wrapped
|
No |
Which kind of operation the CXF endpoint producer will invoke. Possible values are: true , false (default).
|
wrappedStyle
|
No |
Since 2.5.0 The WSDL style that describes how parameters are represented in the SOAP body. If the value is false , CXF will chose the document-literal unwrapped style, If the value is true , CXF will chose the document-literal wrapped style
|
setDefaultBus
|
No |
Specifies whether or not to use the default CXF bus for this endpoint. Possible values are: true , false (default).
|
bus
|
No |
Use
# notation to reference a bus object from the registry—for example, bus=#busName . The referenced object must be an instance of org.apache.cxf.Bus .
By default, uses the default bus created by CXF Bus Factory.
|
cxfBinding
|
No |
Use
# notation to reference a CXF binding object from the registry—for example, cxfBinding=#bindingName . The referenced object must be an instance of org.apache.camel.component.cxf.CxfBinding .
|
headerFilterStrategy
|
No |
Use # notation to reference a header filter strategy object from the registry—for example, headerFilterStrategy=#strategyName . The referenced object must be an instance of org.apache.camel.spi.HeaderFilterStrategy .
|
loggingFeatureEnabled
|
No |
New in 2.3, this option enables CXF Logging Feature which writes inbound and outbound SOAP messages to log. Possible values are: true , false (default).
|
defaultOperationName
|
No |
New in 2.4, this option will set the default
operationName that will be used by the CxfProducer that invokes the remote service. For example:
defaultOperationName =greetMe
|
defaultOperationNamespace
|
No |
New in 2.4, this option will set the default operationNamespace that will be used by the CxfProducer which invokes the remote service. For example:
defaultOperationNamespace = http://apache.org/hello_world_soap_http
|
synchronous
|
No |
New in 2.5, this option will let CXF endpoint decide to use sync or async API to do the underlying work. The default value is false , which means camel-cxf endpoint will try to use async API by default.
|
publishedEndpointUrl
|
No |
New in 2.5, this option overrides the endpoint URL that appears in the published WSDL that is accessed using the service address URL plus
?wsdl . For example:
publshedEndpointUrl=http://example.com/service
|
properties.propName
|
No |
Camel 2.8: Allows you to set custom CXF properties in the endpoint URI. For example, setting properties.mtom-enabled=true to enable MTOM.
|
allowStreaming
|
No | New in 2.8.2. This option controls whether the CXF component, when running in PAYLOAD mode (see below), will DOM parse the incoming messages into DOM Elements or keep the payload as a javax.xml.transform.Source object that would allow streaming in some cases. |
skipFaultLogging
|
No | New in 2.11. This option controls whether the PhaseInterceptorChain skips logging the Fault that it catches. |
serviceName
and portName
are QNames, so if you provide them be sure to prefix them with their {namespace}
as shown in the examples above.
The descriptions of the dataformats Copier lienLien copié sur presse-papiers!
DataFormat | Description |
---|---|
POJO
|
POJOs (plain old Java objects) are the Java parameters to the method being invoked on the target server. Both Protocol and Logical JAX-WS handlers are supported. |
PAYLOAD
|
PAYLOAD is the message payload (the contents of the soap:body ) after message configuration in the CXF endpoint is applied. Only Protocol JAX-WS handler is supported. Logical JAX-WS handler is not supported.
|
MESSAGE
|
MESSAGE is the raw message that is received from the transport layer. JAX-WS handler is not supported.
|
CamelCXFDataFormat
. The exchange key constant is defined in org.apache.camel.component.cxf.CxfConstants.DATA_FORMAT_PROPERTY
.
Configuring the CXF Endpoints with Apache Aries Blueprint. Copier lienLien copié sur presse-papiers!
How to enable CXF's LoggingOutInterceptor in MESSAGE mode Copier lienLien copié sur presse-papiers!
LoggingOutInterceptor
outputs outbound message that goes on the wire to logging system (java.util.logging
). Since the LoggingOutInterceptor
is in PRE_STREAM
phase (but PRE_STREAM
phase is removed in MESSAGE
mode), you have to configure LoggingOutInterceptor
to be run during the WRITE
phase. The following is an example.
Description of relayHeaders option Copier lienLien copié sur presse-papiers!
relayHeaders
should be set to true
, which is the default value.
Available only in POJO mode Copier lienLien copié sur presse-papiers!
relayHeaders=true
setting expresses an intent to relay the headers. The actual decision on whether a given header is relayed is delegated to a pluggable instance that implements the MessageHeadersRelay
interface. A concrete implementation of MessageHeadersRelay
will be consulted to decide if a header needs to be relayed or not. There is already an implementation of SoapMessageHeadersRelay
which binds itself to well-known SOAP name spaces. Currently only out-of-band headers are filtered, and in-band headers will always be relayed when relayHeaders=true
. If there is a header on the wire, whose name space is unknown to the runtime, then a fall back DefaultMessageHeadersRelay
will be used, which simply allows all headers to be relayed.
relayHeaders=false
setting asserts that all headers, in-band and out-of-band, will be dropped.
MessageHeadersRelay
implementations overriding or adding additional ones to the list of relays. In order to override a preloaded relay instance just make sure that your MessageHeadersRelay
implementation services the same name spaces as the one you looking to override. Also note, that the overriding relay has to service all of the name spaces as the one you looking to override, or else a runtime exception on route start up will be thrown as this would introduce an ambiguity in name spaces to relay instance mappings.
Changes since Release 2.0 Copier lienLien copié sur presse-papiers!
POJO
andPAYLOAD
modes are supported. InPOJO
mode, only out-of-band message headers are available for filtering as the in-band headers have been processed and removed from the header list by CXF. The in-band headers are incorporated into theMessageContentList
inPOJO
mode. Thecamel-cxf
component does make any attempt to remove the in-band headers from theMessageContentList
If filtering of in-band headers is required, please usePAYLOAD
mode or plug in a (pretty straightforward) CXF interceptor/JAXWS Handler to the CXF endpoint.- The Message Header Relay mechanism has been merged into
CxfHeaderFilterStrategy
. TherelayHeaders
option, its semantics, and default value remain the same, but it is a property ofCxfHeaderFilterStrategy
. Here is an example of configuring it.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Then, your endpoint can reference theCxfHeaderFilterStrategy
.<route> <from uri="cxf:bean:routerNoRelayEndpoint?headerFilterStrategy=#dropAllMessageHeadersStrategy"/> <to uri="cxf:bean:serviceNoRelayEndpoint?headerFilterStrategy=#dropAllMessageHeadersStrategy"/> </route>
<route> <from uri="cxf:bean:routerNoRelayEndpoint?headerFilterStrategy=#dropAllMessageHeadersStrategy"/> <to uri="cxf:bean:serviceNoRelayEndpoint?headerFilterStrategy=#dropAllMessageHeadersStrategy"/> </route>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - The
MessageHeadersRelay
interface has changed slightly and has been renamed toMessageHeaderFilter
. It is a property ofCxfHeaderFilterStrategy
. Here is an example of configuring user defined Message Header Filters:Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Other than
relayHeaders
, there are new properties that can be configured inCxfHeaderFilterStrategy
.
Name | Description | type | Required? | Default value |
---|---|---|---|---|
relayHeaders
|
All message headers will be processed by Message Header Filters |
boolean
|
No |
true (1.6.1 behavior)
|
relayAllMessageHeaders
|
All message headers will be propagated (without processing by Message Header Filters) |
boolean
|
No |
false (1.6.1 behavior)
|
allowFilterNamespaceClash
|
If two filters overlap in activation namespace, the property control how it should be handled. If the value is true , last one wins. If the value is false , it will throw an exception
|
boolean
|
No |
false (1.6.1 behavior)
|
Configure the CXF endpoints with Spring Copier lienLien copié sur presse-papiers!
camelContext
tags. When you are invoking the service endpoint, you can set the operationName
and operationNamespace
headers to explicitly state which operation you are calling.
http://camel.apache.org/schema/cxf
as the CXF endpoint's target namespace.
http://activemq.apache.org/camel/schema/cxfEndpoint
namespace was changed to http://camel.apache.org/schema/cxf
.
schemaLocation
attribute specified on the root beans element. This allows CXF to validate the file and is required. Also note the namespace declarations at the end of the <cxf:cxfEndpoint/>
tag--these are required because the combined {namespace}localName
syntax is presently not supported for this tag's attribute values.
cxf:cxfEndpoint
element supports many additional attributes:
Name | Value |
---|---|
PortName
|
The endpoint name this service is implementing, it maps to the wsdl:port@name . In the format of ns:PORT_NAME where ns is a namespace prefix valid at this scope.
|
serviceName
|
The service name this service is implementing, it maps to the wsdl:service@name . In the format of ns:SERVICE_NAME where ns is a namespace prefix valid at this scope.
|
wsdlURL
|
The location of the WSDL. Can be on the classpath, file system, or be hosted remotely. |
bindingId
|
The bindingId for the service model to use.
|
address
|
The service publish address. |
bus
|
The bus name that will be used in the JAX-WS endpoint. |
serviceClass
|
The class name of the SEI (Service Endpoint Interface) class which could have JSR181 annotation or not. |
Name | Value |
---|---|
cxf:inInterceptors
|
The incoming interceptors for this endpoint. A list of <bean> or <ref> .
|
cxf:inFaultInterceptors
|
The incoming fault interceptors for this endpoint. A list of <bean> or <ref> .
|
cxf:outInterceptors
|
The outgoing interceptors for this endpoint. A list of <bean> or <ref> .
|
cxf:outFaultInterceptors
|
The outgoing fault interceptors for this endpoint. A list of <bean> or <ref> .
|
cxf:properties
|
A properties map which should be supplied to the JAX-WS endpoint. See below. |
cxf:handlers
|
A JAX-WS handler list which should be supplied to the JAX-WS endpoint. See below. |
cxf:dataBinding
|
You can specify the which DataBinding will be use in the endpoint. This can be supplied using the Spring <bean class="MyDataBinding"/> syntax.
|
cxf:binding
|
You can specify the BindingFactory for this endpoint to use. This can be supplied using the Spring <bean class="MyBindingFactory"/> syntax.
|
cxf:features
|
The features that hold the interceptors for this endpoint. A list of <bean> s or <ref> s
|
cxf:schemaLocations
|
The schema locations for endpoint to use. A list of <schemaLocation> s
|
cxf:serviceFactory
|
The service factory for this endpoint to use. This can be supplied using the Spring <bean class="MyServiceFactory"/> syntax
|
dataFormat
and setDefaultBus
properties from a Spring configuration file, as follows:
How to make the camel-cxf component use log4j instead of java.util.logging Copier lienLien copié sur presse-papiers!
java.util.logging
. If you want to change it to log4j
, proceed as follows. Create a file, in the classpath, named META-INF/cxf/org.apache.cxf.logger
. This file should contain the fully-qualified name of the class, org.apache.cxf.common.logging.Log4jLogger
, with no comments, on a single line.
How to let camel-cxf response message with xml start document Copier lienLien copié sur presse-papiers!
Error:sendSms: SoapFault exception: [Client] looks like we got no XML document in [...]
Error:sendSms: SoapFault exception: [Client] looks like we got no XML document in [...]
camel-cxf
endpont
// set up the response context which force start document Map<String, Object> map = new HashMap<String, Object>(); map.put("org.apache.cxf.stax.force-start-document", Boolean.TRUE); exchange.getOut().setHeader(Client.RESPONSE_CONTEXT, map);
// set up the response context which force start document
Map<String, Object> map = new HashMap<String, Object>();
map.put("org.apache.cxf.stax.force-start-document", Boolean.TRUE);
exchange.getOut().setHeader(Client.RESPONSE_CONTEXT, map);
How to consume a message from a camel-cxf endpoint in POJO data format Copier lienLien copié sur presse-papiers!
camel-cxf
endpoint consumer POJO
data format is based on the cxf invoker, so the message header has a property with the name of CxfConstants.OPERATION_NAME
and the message body is a list of the SEI method parameters.
How to prepare the message for the camel-cxf endpoint in POJO data format Copier lienLien copié sur presse-papiers!
camel-cxf
endpoint producer is based on the cxf client API. First you need to specify the operation name in the message header, then add the method parameters to a list, and initialize the message with this parameter list. The response message's body is a messageContentsList
, you can get the result from that list.
message.getbody(Object[].class)
, as follows:
How to deal with the message for a camel-cxf endpoint in PAYLOAD data format Copier lienLien copié sur presse-papiers!
CxfMessage.getBody()
will return an org.apache.camel.component.cxf.CxfPayload
object, which has getters for SOAP message headers and Body elements. This change enables decoupling the native CXF message from the Apache Camel message.
How to get and set SOAP headers in POJO mode Copier lienLien copié sur presse-papiers!
POJO
means that the data format is a list of Java objects when the CXF endpoint produces or consumes Camel exchanges. Even though Apache Camel exposes the message body as POJOs in this mode, the CXF component still provides access to read and write SOAP headers. However, since CXF interceptors remove in-band SOAP headers from the header list after they have been processed, only out-of-band SOAP headers are available in POJO mode.
org.apache.cxf.headers.Header.list
, which is a constant defined in CXF (org.apache.cxf.headers.Header.HEADER_LIST
). The header value is a List<>
of CXF SoapHeader
objects (org.apache.cxf.binding.soap.SoapHeader
). The following snippet is the InsertResponseOutHeaderProcessor
(that inserts a new SOAP header in the response message). The way to access SOAP headers in both InsertResponseOutHeaderProcessor
and InsertRequestOutHeaderProcessor
are actually the same. The only difference between the two processors is setting the direction of the inserted SOAP header.
How to get and set SOAP headers in PAYLOAD mode Copier lienLien copié sur presse-papiers!
CxfPayload
object) in PAYLOAD
mode (see the section called “How to deal with the message for a camel-cxf endpoint in PAYLOAD data format”).
CxfPayload
object, you can invoke the CxfPayload.getHeaders()
method that returns a List
of DOM Elements (SOAP headers).
SOAP headers are not available in MESSAGE mode Copier lienLien copié sur presse-papiers!
MESSAGE
mode as SOAP processing is skipped.
How to throw a SOAP Fault from Apache Camel Copier lienLien copié sur presse-papiers!
Fault
from the camel context. Basically, you can use the throwFault
DSL to do that; it works for POJO
, PAYLOAD
and MESSAGE
data format. You can define the soap fault like this:
SOAP_FAULT = new SoapFault(EXCEPTION_MESSAGE, SoapFault.FAULT_CODE_CLIENT); Element detail = SOAP_FAULT.getOrCreateDetail(); Document doc = detail.getOwnerDocument(); Text tn = doc.createTextNode(DETAIL_TEXT); detail.appendChild(tn);
SOAP_FAULT = new SoapFault(EXCEPTION_MESSAGE, SoapFault.FAULT_CODE_CLIENT);
Element detail = SOAP_FAULT.getOrCreateDetail();
Document doc = detail.getOwnerDocument();
Text tn = doc.createTextNode(DETAIL_TEXT);
detail.appendChild(tn);
from(routerEndpointURI).setFaultBody(constant(SOAP_FAULT));
from(routerEndpointURI).setFaultBody(constant(SOAP_FAULT));
MESSAGE
data format, you could set the the SOAP Fault message in the message body and set the response code in the message header.
Message.setFault(true)
, as follows:
How to propagate a CXF endpoint's request and response context Copier lienLien copié sur presse-papiers!
Attachment Support Copier lienLien copié sur presse-papiers!
DataHandler Message.getAttachment(String id)
DataHandler Message.getAttachment(String id)
How to propagate stack trace information Copier lienLien copié sur presse-papiers!
dataFormat
to PAYLOAD
and set the faultStackTraceEnabled
property to true
in the cxfEndpoint
element, as follows:
Caused by
). If you want to include the causing exception in the stack trace, set the exceptionMessageCauseEnabled
property to true
in the cxfEndpoint
element, as follows:
exceptionMessageCauseEnabled
flag for testing and diagnostic purposes. It is normal practice for servers to conceal the original cause of an exception to make it harder for hostile users to probe the server.
Streaming Support in PAYLOAD mode Copier lienLien copié sur presse-papiers!
- Endpoint property: you can add "allowStreaming=false" as an endpoint property to turn the streaming on/off.
- Component property: the CxfComponent object also has an allowStreaming property that can set the default for endpoints created from that component.
- Global system property: you can add a system property of "org.apache.camel.component.cxf.streaming" to "false" to turn if off. That sets the global default, but setting the endpoint property above will override this value for that endpoint.
Chapter 19. CXF Bean Component Copier lienLien copié sur presse-papiers!
CXF Bean Component (2.0 or later) Copier lienLien copié sur presse-papiers!
CxfBeanEndpoint
is a ProcessorEndpoint
so it has no consumers. It works similarly to a Bean component.
URI format Copier lienLien copié sur presse-papiers!
cxfbean:serviceBeanRef
cxfbean:serviceBeanRef
serviceBeanRef
references a List
object, elements of the List
are the service bean objects accepted by the endpoint.
Options Copier lienLien copié sur presse-papiers!
Name | Description | Example | Required? | Default Value |
---|---|---|---|---|
cxfBeanBinding
|
CXF bean binding specified by the \# notation. The referenced object must be an instance of org.apache.camel.component.cxf.cxfbean.CxfBeanBinding .
|
cxfBinding=#bindingName
|
No |
DefaultCxfBeanBinding
|
bus
|
CXF bus reference specified by the \# notation. The referenced object must be an instance of org.apache.cxf.Bus .
|
bus=#busName
|
No | Default bus created by CXF Bus Factory |
headerFilterStrategy
|
Header filter strategy specified by the \# notation. The referenced object must be an instance of org.apache.camel.spi.HeaderFilterStrategy .
|
headerFilterStrategy=#strategyName
|
No |
CxfHeaderFilterStrategy
|
setDefaultBus
|
Will set the default bus when CXF endpoint create a bus by itself. |
true , false
|
No |
false
|
populateFromClass
|
Since 2.3, the wsdlLocation annotated in the POJO is ignored (by default) unless this option is set to false. Prior to 2.3, the wsdlLocation annotated in the POJO is always honored and it is not possible to ignore.
|
true , false
|
No |
true
|
providers
|
Since 2.5, setting the providers for the CXFRS endpoint. |
providers=#providerRef1,#providerRef2
|
No |
null
|
Headers Copier lienLien copié sur presse-papiers!
Name | Description | Type | Required? | Default Value | In/Out | Examples |
---|---|---|---|---|---|---|
CamelHttpCharacterEncoding (before 2.0-m2: CamelCxfBeanCharacterEncoding )
|
Character encoding |
String
|
No | None | In | ISO-8859-1 |
CamelContentType (before 2.0-m2: CamelCxfBeanContentType )
|
Content type |
String
|
No | \**/*\* | In |
text/xml
|
CamelHttpBaseUri (2.0-m3 and before:
CamelCxfBeanRequestBasePath )
|
The value of this header will be set in the CXF message as the Message.BASE_PATH property. It is needed by CXF JAX-RS processing. Basically, it is the scheme, host and port portion of the request URI.
|
String
|
Yes | The Endpoint URI of the source endpoint in the Camel exchange | In | http://localhost:9000 |
CamelHttpPath (before 2.0-m2: CamelCxfBeanRequestPat{} h)
|
Request URI's path |
String
|
Yes | None | In |
consumer/123
|
CamelHttpMethod (before 2.0-m2: CamelCxfBeanVerb )
|
RESTful request verb |
String
|
Yes | None | In |
GET , PUT , POST , DELETE
|
CamelHttpResponseCode
|
HTTP response code |
Integer
|
No | None | Out | 200 |
A Working Sample Copier lienLien copié sur presse-papiers!
from
endpoint is a Jetty HTTP endpoint that is listening on port 9000. Notice that the matchOnUriPrefix
option must be set to true
because RESTful request URI will not match the endpoint's URI http://localhost:9000
exactly.
<route> <from uri="jetty:http://localhost:9000?matchOnUriPrefix=true" /> <to uri="cxfbean:customerServiceBean" /> <to uri="mock:endpointA" /> </route>
<route>
<from uri="jetty:http://localhost:9000?matchOnUriPrefix=true" />
<to uri="cxfbean:customerServiceBean" />
<to uri="mock:endpointA" />
</route>
to
endpoint is a CXF Bean with bean name customerServiceBean
. The name will be looked up from the registry. Next, we make sure our service bean is available in Spring registry. We create a bean definition in the Spring configuration. In this example, we create a List of service beans (of one element). We could have created just a single bean without a List.
<util:list id="customerServiceBean"> <bean class="org.apache.camel.component.cxf.jaxrs.testbean.CustomerService" /> </util:list> <bean class="org.apache.camel.wsdl_first.PersonImpl" id="jaxwsBean" />
<util:list id="customerServiceBean">
<bean class="org.apache.camel.component.cxf.jaxrs.testbean.CustomerService" />
</util:list>
<bean class="org.apache.camel.wsdl_first.PersonImpl" id="jaxwsBean" />
url = new URL("http://localhost:9000/customerservice/orders/223/products/323"); in = url.openStream(); assertEquals("{\"Product\":{\"description\":\"product 323\",\"id\":323}}", CxfUtils.getStringFromInputStream(in));
url = new URL("http://localhost:9000/customerservice/orders/223/products/323");
in = url.openStream();
assertEquals("{\"Product\":{\"description\":\"product 323\",\"id\":323}}", CxfUtils.getStringFromInputStream(in));
Chapter 20. CXFRS Copier lienLien copié sur presse-papiers!
CXFRS Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-cxf</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-cxf</artifactId>
<version>x.x.x</version> <!-- use the same version as your Camel core version -->
</dependency>
URI format Copier lienLien copié sur presse-papiers!
cxfrs://address?options
cxfrs://address?options
cxfrs:bean:rsEndpoint
cxfrs:bean:rsEndpoint
cxfrs:bean:cxfEndpoint?resourceClasses=org.apache.camel.rs.Example
cxfrs:bean:cxfEndpoint?resourceClasses=org.apache.camel.rs.Example
Options Copier lienLien copié sur presse-papiers!
Name | Description | Example | Required? | default value |
---|---|---|---|---|
resourceClasses
|
The resource classes which you want to export as REST service. Multiple classes can be separated by a comma. |
resourceClasses=org.apache.camel.rs.Example1, org.apache.camel.rs.Exchange2
|
No | None |
httpClientAPI
|
New to Apache Camel 2.1 If it is true, the CxfRsProducer will use the HttpClientAPI to invoke the service |
httpClientAPI=true
|
No |
true
|
synchronous
|
New in 2.5, this option will let CxfRsConsumer decide to use sync or async API to do the underlying work. The default value is false which means it will try to use async API by default. |
synchronous=true
|
No |
false
|
throwExceptionOnFailure
|
New in 2.6, this option tells the CxfRsProducer to inspect return codes and will generate an Exception if the return code is larger than 207. |
throwExceptionOnFailure=true
|
No |
true
|
maxClientCacheSize
|
New in 2.6, you can set the In message header, CamelDestinationOverrideUrl , to dynamically override the target destination Web Service or REST Service defined in your routes. The implementation caches CXF clients or ClientFactoryBean in CxfProvider and CxfRsProvider . This option allows you to configure the maximum size of the cache.
|
maxClientCacheSize=5
|
No | 10 |
setDefaultBus
|
New in 2.9.0. Will set the default bus when CXF endpoint create a bus by itself |
setDefaultBus=true
|
No |
false
|
bus
|
New in 2.9.0. A default bus created by CXF Bus Factory. Use \# notation to reference a bus object from the registry. The referenced object must be an instance of org.apache.cxf.Bus .
|
bus=#busName
|
No | _None_ |
How to configure the REST endpoint in Apache Camel Copier lienLien copié sur presse-papiers!
How to consume the REST request in Apache Camel Copier lienLien copié sur presse-papiers!
camel-restlet
, you don't need to specify the URI template within your restlet endpoint, CXF take care of the REST request URI to resource class method mapping according to the JSR311 specification. All you need to do in Apache Camel is delegate this method request to a right processor or endpoint.
How to invoke the REST service through camel-cxfrs producer ? Copier lienLien copié sur presse-papiers!
camel-cxfrs
producer is based on this proxy API. So, you just need to specify the operation name in the message header and prepare the parameter in the message body, camel-cxfrs
producer will generate right REST request for you.
camel-cxfrs
producer. You need to specify the HTTP_PATH and Http method and let the the producer know to use the HTTP centric client by using the URI option httpClientAPI or set the message header with CxfConstants.CAMEL_CXF_RS_USING_HTTP_API
. You can turn the response object to the type class that you specify with CxfConstants.CAMEL_CXF_RS_RESPONSE_CLASS
.
Exchange exchange = template.send("cxfrs://http://localhost:" + getPort2() + "/" + getClass().getSimpleName() + "/testQuery?httpClientAPI=true&q1=12&q2=13"
Exchange exchange = template.send("cxfrs://http://localhost:" + getPort2() + "/" + getClass().getSimpleName() + "/testQuery?httpClientAPI=true&q1=12&q2=13"
CxfConstants.CAMEL_CXF_RS_QUERY_MAP
header to set the parameter map for it.
Map<String, String> queryMap = new LinkedHashMap<String, String>(); queryMap.put("q1", "new"); queryMap.put("q2", "world"); inMessage.setHeader(CxfConstants.CAMEL_CXF_RS_QUERY_MAP, queryMap);
Map<String, String> queryMap = new LinkedHashMap<String, String>();
queryMap.put("q1", "new");
queryMap.put("q2", "world");
inMessage.setHeader(CxfConstants.CAMEL_CXF_RS_QUERY_MAP, queryMap);
Chapter 21. DataSet Copier lienLien copié sur presse-papiers!
DataSet Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
dataset:name[?options]
dataset:name[?options]
org.apache.camel.component.dataset.DataSet
, the org.apache.camel.component.dataset.DataSetSupport
class, that can be used as a base for implementing your own DataSet. Apache Camel also ships with a default implementation, the org.apache.camel.component.dataset.SimpleDataSet
that can be used for testing.
Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
produceDelay
|
3 | Allows a delay in ms to be specified, which causes producers to pause in order to simulate slow producers. Uses a minimum of 3 ms delay unless you set this option to -1 to force no delay at all. |
consumeDelay
|
0 | Allows a delay in ms to be specified, which causes consumers to pause in order to simulate slow consumers. |
preloadSize
|
0 | Sets how many messages should be preloaded (sent) before the route completes its initialization. |
initialDelay
|
1000 | Camel 2.1: Time period in millis to wait before starting sending messages. |
minRate
|
0 | Wait until the DataSet contains at least this number of messages |
?option=value&option=value&...
Configuring DataSet Copier lienLien copié sur presse-papiers!
<bean id="myDataSet" class="com.mycompany.MyDataSet"> <property name="size" value="100"/> </bean>
<bean id="myDataSet" class="com.mycompany.MyDataSet">
<property name="size" value="100"/>
</bean>
Example Copier lienLien copié sur presse-papiers!
// send the dataset to a queue from("dataset:foo").to("activemq:SomeQueue"); // now lets test that the messages are consumed correctly from("activemq:SomeQueue").to("dataset:foo");
// send the dataset to a queue
from("dataset:foo").to("activemq:SomeQueue");
// now lets test that the messages are consumed correctly
from("activemq:SomeQueue").to("dataset:foo");
SimpleDataSet
as described below, configuring things like how big the data set is and what the messages look like etc.
Properties on SimpleDataSet Copier lienLien copié sur presse-papiers!
Property | Type | Description |
---|---|---|
defaultBody
|
Object
|
Specifies the default message body. For SimpleDataSet it is a constant payload; though if you want to create custom payloads per message, create your own derivation of DataSetSupport .
|
reportGroup
|
long
|
Specifies the number of messages to be received before reporting progress. Useful for showing progress of a large load test. |
size
|
long
|
Specifies how many messages to send/consume. |
Chapter 22. Direct Copier lienLien copié sur presse-papiers!
Direct Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
direct:someName[?options]
direct:someName[?options]
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|
?option=value&option=value&...
Samples Copier lienLien copié sur presse-papiers!
from("activemq:queue:order.in").to("bean:orderServer?method=validate").to("direct:processOrder"); from("direct:processOrder").to("bean:orderService?method=process").to("activemq:queue:order.out");
from("activemq:queue:order.in").to("bean:orderServer?method=validate").to("direct:processOrder");
from("direct:processOrder").to("bean:orderService?method=process").to("activemq:queue:order.out");
Chapter 23. Direct-VM Copier lienLien copié sur presse-papiers!
Direct VM Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
direct-vm:someName
direct-vm:someName
Samples Copier lienLien copié sur presse-papiers!
from("activemq:queue:order.in") .to("bean:orderServer?method=validate") .to("direct-vm:processOrder");
from("activemq:queue:order.in")
.to("bean:orderServer?method=validate")
.to("direct-vm:processOrder");
from("direct-vm:processOrder") .to("bean:orderService?method=process") .to("activemq:queue:order.out");
from("direct-vm:processOrder")
.to("bean:orderService?method=process")
.to("activemq:queue:order.out");
Chapter 24. DNS Copier lienLien copié sur presse-papiers!
DNS Copier lienLien copié sur presse-papiers!
ip
- To resolve a domain by its IP address.
lookup
- To look up information about the domain.
dig
- To run DNS queries.
etc/jre.properties
file, to add sun.net.spi.nameservice
to the list of Java platform packages exported. The server will need restarting before this change takes effect.
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
dns://operation
dns://operation
Options Copier lienLien copié sur presse-papiers!
Headers Copier lienLien copié sur presse-papiers!
Header | Type | Operations | Description |
---|---|---|---|
dns.domain
|
String
|
ip
|
The domain name. Mandatory. |
dns.name
|
String
|
lookup
|
The name to lookup. Mandatory. |
dns.type
|
- |
lookup , dig
|
The type of the lookup. Should match the values of org.xbill.dns.Type . Optional.
|
dns.class
|
- |
lookup , dig
|
he DNS class of the lookup. Should match the values of org.xbill.dns.DClass . Optional.
|
dns.query
|
String
|
dig
|
The query itself. Mandatory. |
dns.server
|
String
|
dig
|
The server in particular for the query. If none is given, the default one specified by the OS will be used. Optional. |
Examples Copier lienLien copié sur presse-papiers!
IP lookup Copier lienLien copié sur presse-papiers!
<route id="IPCheck"> <from uri="direct:start"/> <to uri="dns:ip"/> </route>
<route id="IPCheck">
<from uri="direct:start"/>
<to uri="dns:ip"/>
</route>
"dns.domain"
.
DNS lookup Copier lienLien copié sur presse-papiers!
<route id="IPCheck"> <from uri="direct:start"/> <to uri="dns:lookup"/> </route>
<route id="IPCheck">
<from uri="direct:start"/>
<to uri="dns:lookup"/>
</route>
"dns.name"
.
DNS Dig Copier lienLien copié sur presse-papiers!
<route id="IPCheck"> <from uri="direct:start"/> <to uri="dns:dig"/> </route>
<route id="IPCheck">
<from uri="direct:start"/>
<to uri="dns:dig"/>
</route>
"dns.query"
.
Chapter 25. EJB Copier lienLien copié sur presse-papiers!
EJB Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
ejb:ejbName[?options]
ejb:ejbName[?options]
Options Copier lienLien copié sur presse-papiers!
Name | Type | Default | Description |
---|---|---|---|
method
|
String
|
null
|
The method name that bean will be invoked. If not provided, Apache Camel will try to pick the method itself. In case of ambiguity an exception is thrown. See Bean Binding for more details. |
multiParameterArray
|
boolean
|
false
|
How to treat the parameters which are passed from the message body; if it is true , the In message body should be an array of parameters.
|
?option=value&option=value&...
Bean Binding Copier lienLien copié sur presse-papiers!
Examples Copier lienLien copié sur presse-papiers!
Using Java DSL Copier lienLien copié sur presse-papiers!
hello
method on the EJB. Since this example is based on an unit test using Apache OpenEJB we have to set a JndiContext
on the EJB component with the OpenEJB settings.
from("direct:start") // invoke the greeter EJB using the local interface and invoke the hello method .to("ejb:GreaterImplLocal?method=hello") .to("mock:result");
from("direct:start")
// invoke the greeter EJB using the local interface and invoke the hello method
.to("ejb:GreaterImplLocal?method=hello")
.to("mock:result");
JndiContext
on the EJB component as it will create a default JndiContext
on the same JVM as the application server, which usually allows it to access the JNDI registry and lookup the EJBs. However if you need to access a application server on a remote JVM or the likes, you have to prepare the properties beforehand.
Using Spring XML Copier lienLien copié sur presse-papiers!
Chapter 26. Event Copier lienLien copié sur presse-papiers!
Event Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
Chapter 27. EventAdmin Copier lienLien copié sur presse-papiers!
EventAdmin component Copier lienLien copié sur presse-papiers!
eventadmin
component can be used in an OSGi environment to receive OSGi EventAdmin events and process them.
Dependencies Copier lienLien copié sur presse-papiers!
pom.xml
$\{camel-version\}
must be replaced by the actual version of Camel (2.6.0 or higher).
URI format Copier lienLien copié sur presse-papiers!
eventadmin:topic
eventadmin:topic
topic
is the name of the topic to listen too.
URI options Copier lienLien copié sur presse-papiers!
Name | Default value | Description |
---|
Message headers Copier lienLien copié sur presse-papiers!
Name | Type | Message | Description |
---|
Message body Copier lienLien copié sur presse-papiers!
in
message body will be set to the received Event.
Example usage Copier lienLien copié sur presse-papiers!
Chapter 28. Exec Copier lienLien copié sur presse-papiers!
Exec component Copier lienLien copié sur presse-papiers!
exec
component can be used to execute system commands.
Dependencies Copier lienLien copié sur presse-papiers!
pom.xml
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-exec</artifactId> <version>${camel-version}</version> </dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-exec</artifactId>
<version>${camel-version}</version>
</dependency>
${camel-version}
must be replaced by the actual version of Apache Camel (2.3.0 or higher).
URI format Copier lienLien copié sur presse-papiers!
exec://executable[?options]
exec://executable[?options]
executable
is the name, or file path, of the system command that will be executed. If executable name is used (e.g. exec:java
), the executable must in the system path.
URI options Copier lienLien copié sur presse-papiers!
Name | Default value | Description |
---|---|---|
args
|
null
|
The arguments of the executable. The arguments may be one or many whitespace-separated tokens, that can be quoted with
" , e.g. args="arg 1" arg2 will use two arguments arg 1 and arg2 . To include the quotes use "" , e.g. args=""arg 1"" arg2 will use the arguments "arg 1" and arg2 .
|
workingDir
|
null
|
The directory in which the command should be executed. If null , the working directory of the current process will be used.
|
timeout
|
Long.MAX_VALUE
|
The timeout, in milliseconds, after which the executable should be terminated. If execution has has not finished within the timeout, the component will send a termination request. |
outFile
|
null
|
The name of a file, created by the executable, that should be considered as its output. If no outFile is set, the standard output (stdout) of the executable will be considered as output.
|
binding
|
a DefaultExecBinding instance
|
A reference to a org.apache.commons.exec.ExecBinding in the Registry.
|
commandExecutor
|
a DefaultCommandExecutor instance
|
A reference to a org.apache.commons.exec.ExecCommandExecutor in the Registry, that customizes the command execution. The default command executor utilizes the commons-exec library. It adds a shutdown hook for every executed command.
|
useStderrOnEmptyStdout
|
false
|
A boolean indicating that when stdout is empty, this component will populate the Camel Message Body with stderr . This behavior is disabled (false ) by default.
|
Message headers Copier lienLien copié sur presse-papiers!
org.apache.camel.component.exec.ExecBinding
.
Name | Type | Message | Description |
---|---|---|---|
ExecBinding.EXEC_COMMAND_EXECUTABLE
|
String
|
in
|
The name of the system command that will be executed. Overrides the executable in the URI.
|
ExecBinding.EXEC_COMMAND_ARGS
|
java.util.List<String>
|
in
|
The arguments of the executable. The arguments are used literally, no quoting is applied. Overrides existing args in the URI.
|
ExecBinding.EXEC_COMMAND_ARGS
|
String
|
in
|
Camel 2.5: The arguments of the executable as a Single string where each argument is whitespace separated (see args in URI option). The arguments are used literally, no quoting is applied. Overrides existing args in the URI.
|
ExecBinding.EXEC_COMMAND_OUT_FILE
|
String
|
in
|
The name of a file, created by the executable, that should be considered as output of the executable. Overrides existing outFile in the URI.
|
ExecBinding.EXEC_COMMAND_TIMEOUT
|
long
|
in
|
The timeout, in milliseconds, after which the executable should be terminated. Overrides any existing timeout in the URI.
|
ExecBinding.EXEC_COMMAND_WORKING_DIR
|
String
|
in
|
The directory in which the command should be executed. Overrides any existing workingDir in the URI.
|
ExecBinding.EXEC_EXIT_VALUE
|
int
|
out
|
The value of this header is the exit value of the executable. Non-zero exit values typically indicate abnormal termination. Note that the exit value is OS-dependent. |
ExecBinding.EXEC_STDERR
|
java.io.InputStream
|
out
|
The value of this header points to the standard error stream (stderr) of the executable. If no stderr is written, the value is null .
|
ExecBinding.EXEC_USE_STDERR_ON_EMPTY_STDOUT
|
boolean
|
in
|
Indicates that when stdout is empty, this component will populate the Camel Message Body with stderr . This behavior is disabled (false ) by default.
|
Message body Copier lienLien copié sur presse-papiers!
Exec
component receives an in
message body that is convertible to java.io.InputStream
, it is used to feed input to the executable via its stdin. After execution, the message body is the result of the execution, that is, an org.apache.camel.components.exec.ExecResult
instance containing the stdout, stderr, exit value, and out file. This component supports the following ExecResult
type converters for convenience:
From | To |
---|---|
ExecResult
|
java.io.InputStream
|
ExecResult
|
String
|
ExecResult
|
byte []
|
ExecResult
|
org.w3c.dom.Document
|
Executing word count (Linux) Copier lienLien copié sur presse-papiers!
wc
(word count, Linux) to count the words in file /usr/share/dict/words
. The word count (output) is written in the standart output stream of wc
.
Executing java Copier lienLien copié sur presse-papiers!
java
with 2 arguments: -server
and -version
, provided that java
is in the system path.
from("direct:exec") .to("exec:java?args=-server -version")
from("direct:exec")
.to("exec:java?args=-server -version")
java
in c:/temp
with 3 arguments: -server
, -version
and the sytem property user.name
.
from("direct:exec") .to("exec:c:/program files/jdk/bin/java?args=-server -version -Duser.name=Camel&workingDir=c:/temp")
from("direct:exec")
.to("exec:c:/program files/jdk/bin/java?args=-server -version -Duser.name=Camel&workingDir=c:/temp")
Executing Ant scripts Copier lienLien copié sur presse-papiers!
CamelExecBuildFile.xml
, provided that ant.bat
is in the system path, and that CamelExecBuildFile.xml
is in the current directory.
from("direct:exec") .to("exec:ant.bat?args=-f CamelExecBuildFile.xml")
from("direct:exec")
.to("exec:ant.bat?args=-f CamelExecBuildFile.xml")
ant.bat
command redirects its output to CamelExecOutFile.txt
with -l
. The file CamelExecOutFile.txt
is used as the out file with outFile=CamelExecOutFile.txt
. The example assumes that ant.bat
is in the system path, and that CamelExecBuildFile.xml
is in the current directory.
Executing echo (Windows) Copier lienLien copié sur presse-papiers!
echo
and dir
can be executed only with the command interpreter of the operating system. This example shows how to execute such a command - echo
- in Windows.
from("direct:exec").to("exec:cmd?args=/C echo echoString")
from("direct:exec").to("exec:cmd?args=/C echo echoString")
Chapter 29. Fabric Component Copier lienLien copié sur presse-papiers!
Abstract
Dependencies Copier lienLien copié sur presse-papiers!
fabric-camel
feature is installed. If necessary, you can install it using the following console command:
karaf@root> features:install fabric-camel
karaf@root> features:install fabric-camel
fabric-camel
feature is installed by including it in your feature definition. For example:
URI format Copier lienLien copié sur presse-papiers!
fabric:ClusterID[:PublishedURI[?Options]]
fabric:ClusterID[:PublishedURI[?Options]]
fabric:ClusterID:PublishedURI[?Options]
fabric:ClusterID:PublishedURI[?Options]
PublishedURI
, is published in the fabric registry and associated with the ClusterId
cluster. The options, Options
, are used when creating the producer endpoint instance, but the options are not published with the PublishedURI
in the fabric registry.
fabric:ClusterID
fabric:ClusterID
ClusterId
, in the fabric registry to discover the URI to connect to.
URI options Copier lienLien copié sur presse-papiers!
- Server-only options—options that are applicable only to the server are applied to the server endpoint (consumer endpoint) at run time.
- Client-only options—options that are applicable only to the client are applied to the client endpoint (producer endpoint) at run time.
- Common options—options common to the client and the server are applied to both.
Use cases for fabric endpoints Copier lienLien copié sur presse-papiers!
Location discovery Copier lienLien copié sur presse-papiers!
Figure 29.1. Location Discovery through Fabric
jetty:http://0.0.0.0:9090
. When this route is started, it automatically registers the Jetty URI in the fabric registry, under the cluster ID, foo
.
fabric:foo
. Now, when the client route starts, it automatically looks up the ID, foo
, in the fabric registry and retrieves the associated Jetty endpoint URI. The client then creates a producer endpoint using the discovered Jetty URI and connects to the corresponding server port.
Load-balancing cluster Copier lienLien copié sur presse-papiers!
Figure 29.2. Load Balancing through Fabric
jetty:http://0.0.0.0:9090
and jetty:http://0.0.0.0:9191
. Because these published URIs are both prefixed by fabric:foo:
, both of the Jetty URIs are registered under the same cluster ID, foo
, in the fabric registry.
foo
, in the fabric registry. Because the foo
ID is associated with multiple endpoint URIs, fabric implements a random load balancing algorithm to choose one of the available URIs. The client then creates a producer endpoint, using the chosen URI.
Auto-reconnect feature Copier lienLien copié sur presse-papiers!
Publishing an endpoint URI Copier lienLien copié sur presse-papiers!
PublishedURI
, in the fabric registry, define a fabric endpoint with the publisher syntax, fabric:ClusterID:PublishedURI
. Note that this syntax can only be used in a consumer endpoint (that is, an endpoint that appears in a from
DSL command).
cheese
. The route is a simply HTTP server that returns the constant message, Response from Zookeeper agent
, in the body of the HTTP response.
Example 29.1. Publishing a URI
- A reference to the
org.fusesource.fabric.zookeeper.IZKClient
OSGi service is created using thereference
element. This reference is needed, because the Fabric component implicitly looks for anIZKClient
object in the bean registry and uses this object to connect to the underlying fabric.NoteTheIZKClient
OSGi service is provided by the fabric agent. Hence, a fabric agent must already be installed and running in the container where the route is deployed. - The
from
DSL command defines the fabric URI,fabric:cheese:jetty:http://0.0.0.0:9090/fabric
. At run time, this causes two things to happen:- The specified
jetty
URI is published to the fabric registry under the cluster ID,cheese
. - The Jetty endpoint is activated and used as the consumer endpoint of the route (just as if it had been specified without the
fabric:cheese:
prefix).
src/main/resources/OSGI-INF/blueprint
directory of a Maven project.
Looking up an endpoint URI Copier lienLien copié sur presse-papiers!
fabric:ClusterID
. This syntax is used in a producer endpoint (for example, an endpoint that appears in a to
DSL command).
cheese
, in the fabric registry.
Example 29.2. Looking up a URI
org.fusesource.fabric.zookeeper.IZKClient
OSGi service, which the Fabric component uses to connect to the underlying fabric.
src/main/resources/OSGI-INF/blueprint
directory of a Maven project.
Load-balancing example Copier lienLien copié sur presse-papiers!
Example 29.3. Server Template for a Load-Balancing Cluster
fabricCamel
persistent ID. A persistent ID in the OSGi Config Admin service identifies a collection of related property settings. After initializing the property placeholder, you can access any property values from the fabricCamel
persistent ID using the syntax, {{PropName}}
.
{{portNumber}}
, at run time. At deploy time, you can specify the value of the portName
property. For example, if using a custom feature, you could specify the property in the feature definition (see Add OSGi configurations to the feature). Alternatively, you can specify configuration properties when defining deployment profiles in the Fuse Management Console.
OSGi bundle plug-in configuration Copier lienLien copié sur presse-papiers!
Import-Package
bundle header must be configured to import the following Java packages:
org.fusesource.fabric.zookeeper.spring org.fusesource.fabric.zookeeper
org.fusesource.fabric.zookeeper.spring
org.fusesource.fabric.zookeeper
Example 29.4. Maven Bundle Plug-In Configuration
Chapter 30. File2 Copier lienLien copié sur presse-papiers!
File Component - Apache Camel 2.0 onwards Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
file:directoryName[?options]
file:directoryName[?options]
file://directoryName[?options]
file://directoryName[?options]
?option=value&option=value&...
fileName=thefilename
. Also, the starting directory must not contain dynamic expressions with ${ } placeholders. Again use the fileName
option to specify the dynamic part of the filename.
readLock
options and the doneFileOption
option that you can use. See also the section the section called “Consuming files from folders where others drop files directly”.
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
autoCreate
|
true
|
Automatically create missing directories in the file's pathname. For the file consumer, that means creating the starting directory. For the file producer, it means the directory where the files should be written. |
bufferSize
|
128kb | Write buffer sized in bytes. |
fileName
|
null
|
Use Expression such as File Language to dynamically set the filename. For consumers, it's used as a filename filter. For producers, it's used to evaluate the filename to write. If an expression is set, it take precedence over the CamelFileName header. (Note: The header itself can also be an Expression). The expression options support both String and Expression types. If the expression is a String type, it is always evaluated using the File Language. If the expression is an Expression type, the specified Expression type is used - this allows you, for instance, to use OGNL expressions. For the consumer, you can use it to filter filenames, so you can for instance consume today's file using the File Language syntax: mydata-${date:now:yyyyMMdd}.txt .
|
flatten
|
false
|
Flatten is used to flatten the file name path to strip any leading paths, so it's just the file name. This allows you to consume recursively into sub-directories, but when you eg write the files to another directory they will be written in a single directory. Setting this to true on the producer enforces that any file name recived in CamelFileName header will be stripped for any leading paths.
|
charset
|
null
|
Camel 2.5: this option is used to specify the encoding of the file, and camel will set the Exchange property with Exchange.CHARSET_NAME with the value of this option. |
Consumer only Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
initialDelay
|
1000
|
Milliseconds before polling the file/directory starts. |
delay
|
500
|
Milliseconds before the next poll of the file/directory. |
useFixedDelay
|
true
|
Set to true to use fixed delay between pools, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
|
runLoggingLevel
|
TRACE
|
Camel 2.8: The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. |
recursive
|
false
|
If a directory, will look for files in all the sub-directories as well. |
delete
|
false
|
If true , the file will be deleted after it is processed
|
noop
|
false
|
If true , the file is not moved or deleted in any way. This option is good for readonly data, or for ETL type requirements. If noop=true , Apache Camel will set idempotent=true as well, to avoid consuming the same files over and over again.
|
preMove
|
null
|
Use Expression such as File Language to dynamically set the filename when moving it before processing. For example to move in-progress files into the order directory set this value to order .
|
move
|
.camel
|
Use Expression such as File Language to dynamically set the filename when moving it after processing. To move files into a .done subdirectory just enter .done .
|
moveFailed
|
null
|
Use Expression such as File Language to dynamically set the filename when moving failed files after processing. To move files into a error subdirectory just enter error . Note: When moving the files to another location it can/will handle the error when you move it to another location so Apache Camel cannot pick up the file again.
|
include
|
null
|
Is used to include files, if filename matches the regex pattern. |
exclude
|
null
|
Is used to exclude files, if filename matches the regex pattern. |
idempotent
|
false
|
Option to use the Idempotent Consumer EIP pattern to let Apache Camel skip already processed files. Will by default use a memory based LRUCache that holds 1000 entries. If noop=true then idempotent will be enabled as well to avoid consuming the same files over and over again.
|
idempotentRepository
|
null
|
Pluggable repository as a org.apache.camel.processor.idempotent.MessageIdRepository class. Will by default use MemoryMessageIdRepository if none is specified and idempotent is true .
|
inProgressRepository
|
memory
|
Pluggable in-progress repository as a org.apache.camel.processor.idempotent.MessageIdRepository class. The in-progress repository is used to account the current in progress files being consumed. By default a memory based repository is used. |
filter
|
null
|
Pluggable filter as a org.apache.camel.component.file.GenericFileFilter class. Will skip files if filter returns false in its accept() method. Apache Camel also ships with an ANT path matcher filter in the camel-spring component. More details in section below.
|
sorter
|
null
|
Pluggable sorter as a java.util.Comparator<org.apache.camel.component.file.GenericFile> class. |
sortBy
|
null
|
Built-in sort using the File Language. Supports nested sorts, so you can have a sort by file name and as a 2nd group sort by modified date. See sorting section below for details. |
readLock
|
markerFile
|
Used by consumer, to only poll the files if it has exclusive read-lock on the file (i.e. the file is not in-progress or being written). Apache Camel will wait until the file lock is granted.
The
readLock option supports the following built-in strategies:
|
readLockTimeout
|
0 (for FTP, 2000 )
|
Optional timeout in milliseconds for the read-lock, if supported by the read-lock. If the read-lock could not be granted and the timeout triggered, then Apache Camel will skip the file. At next poll Apache Camel, will try the file again, and this time maybe the read-lock could be granted. Currently fileLock , changed and rename support the timeout.
|
readLockCheckInterval
|
1000 (for FTP, 5000 )
|
Camel 2.6: Interval in millis for the read-lock, if supported by the read lock. This interval is used for sleeping between attempts to acquire the read lock. For example when using the changed read lock, you can set a higher interval period to cater for slow writes. The default of 1 sec. may be too fast if the producer is very slow writing the file.
|
exclusiveReadLockStrategy
|
null
|
Pluggable read-lock as a org.apache.camel.component.file.GenericFileExclusiveReadLockStrategy implementation.
|
minDepth
|
0 |
Camel 2.8: The minimum depth to start processing when recursively processing a directory. Using minDepth=1 means the base directory. Using minDepth=2 means the first sub directory. This option is not supported by FTP consumer.
|
maxDepth
|
Integer.MAX_VALUE
|
Camel 2.8: The maximum depth to traverse when recursively processing a directory. This option is not supported by FTP consumer. |
doneFileName
|
null
|
Camel 2.6: If provided, Camel will only consume files if a done file exists. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders. The done file is always expected in the same folder as the original file. See using done file and writing done file sections for examples. |
processStrategy
|
null
|
A pluggable org.apache.camel.component.file.GenericFileProcessStrategy allowing you to implement your own readLock option or similar. Can also be used when special conditions must be met before a file can be consumed, such as a special ready file exists. If this option is set then the readLock option does not apply.
|
maxMessagesPerPoll
|
0
|
An integer that defines the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid having the server read thousands of files as it starts up. Set a value of 0 or negative to disabled it. |
startingDirectoryMustExist
|
false
|
Whether the starting directory must exist. Mind that the autoCreate option is default enabled, which means the starting directory is normally auto-created if it doesn't exist. You can disable autoCreate and enable this to ensure the starting directory must exist. Will throw an exception, if the directory doesn't exist.
|
directoryMustExist
|
false
|
Similar to startingDirectoryMustExist but this applies during polling recursive sub-directories.
|
Default behavior for file consumer Copier lienLien copié sur presse-papiers!
- By default the file is locked for the duration of the processing.
- After the route has completed, files are moved into the
.camel
subdirectory, so that they appear to be deleted. - The File Consumer will always skip any file whose name starts with a dot, such as
.
,.camel
,.m2
or.groovy
. - Only files (not directories) are matched for valid filename, if options such as:
includeNamePrefix
,includeNamePostfix
,excludeNamePrefix
,excludeNamePostfix
,regexPattern
are used.
Producer only Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
fileExist
|
Override
|
What to do if a file already exists with the same name. The following values can be specified: Override, Append, Fail and Ignore. Override , which is the default, replaces the existing file. Append adds content to the existing file. Fail throws a GenericFileOperationException , indicating that there is already an existing file. Ignore silently ignores the problem and does not override the existing file, but assumes everything is okay.
|
tempPrefix
|
null
|
This option is used to write the file using a temporary name and then, after the write is complete, rename it to the real name. Can be used to identify files being written and also avoid consumers (not using exclusive read locks) reading in progress files. Is often used by FTP when uploading big files. |
tempFileName
|
null
|
Camel 2.1: The same as tempPrefix option but offering a more fine grained control on the naming of the temporary filename as it uses the File Language.
|
keepLastModified
|
false
|
Camel 2.2: Will keep the last modified timestamp from the source file (if any). Will use the Exchange.FILE_LAST_MODIFIED header to located the timestamp. This header can contain either a java.util.Date or long with the timestamp. If the timestamp exists and the option is enabled it will set this timestamp on the written file. Note: This option only applies to the file producer. You cannot use this option with any of the ftp producers.
|
eagerDeleteTargetFile
|
true
|
Camel 2.3: Whether or not to eagerly delete any existing target file. This option only applies when you use fileExists=Override and the tempFileName option as well. You can use this to disable (set it to false) deleting the target file before the temp file is written. For example you may write big files and want the target file to exists during the temp file is being written. This ensure the target file is only deleted until the very last moment, just before the temp file is being renamed to the target filename.
|
doneFileName
|
null
|
Camel 2.6: If provided, then Camel will write a 2nd done file when the original file has been written. The done file will be empty. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders. The done file will always be written in the same folder as the original file. See writing done file section for examples. |
Default behavior for file producer Copier lienLien copié sur presse-papiers!
- By default it will override any existing file, if one exist with the same name. In Apache Camel 1.x the
Append
is the default for the file producer. We have changed this toOverride
in Apache Camel 2.0 as this is also the default file operation usingjava.io.File
. And also the default for the FTP library we use in the camel-ftp component.
Move and Delete operations Copier lienLien copié sur presse-papiers!
Exchange
the file is still located in the inbox folder.
from("file://inbox?move=.done").to("bean:handleOrder");
from("file://inbox?move=.done").to("bean:handleOrder");
inbox
folder, the file consumer notices this and creates a new FileExchange
that is routed to the handleOrder
bean. The bean then processes the File
object. At this point in time the file is still located in the inbox
folder. After the bean completes, and thus the route is completed, the file consumer will perform the move operation and move the file to the .done
sub-folder.
.camel
sub-folder relative to the directory where the file was consumed.
from("file://inobox?delete=true").to("bean:handleOrder");
from("file://inobox?delete=true").to("bean:handleOrder");
from("file://inbox?preMove=inprogress").to("bean:handleOrder");
from("file://inbox?preMove=inprogress").to("bean:handleOrder");
from("file://inbox?preMove=inprogress&move=.done").to("bean:handleOrder");
from("file://inbox?preMove=inprogress&move=.done").to("bean:handleOrder");
inprogress
folder when being processed and after it's processed, it's moved to the .done
folder.
Fine grained control over Move and PreMove option Copier lienLien copié sur presse-papiers!
move=.done
Apache Camel will convert this into: ${file:parent}/.done/${file:onlyname}
. This is only done if Apache Camel detects that you have not provided a ${ }
in the option value yourself. So when you enter an expression containing ${ }
, the expression is interpreted as a File Language expression.
move=backup/${date:now:yyyyMMdd}/${file:name}
move=backup/${date:now:yyyyMMdd}/${file:name}
About moveFailed Copier lienLien copié sur presse-papiers!
moveFailed
option allows you to move files that could not be processed succesfully to another location such as a error folder of your choice. For example to move the files in an error folder with a timestamp you can use moveFailed=/error/${file:name.noext}-${date:now:yyyyMMddHHmmssSSS}.${file:name.ext}
.
Message Headers Copier lienLien copié sur presse-papiers!
File producer only Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelFileName
|
Specifies the name of the file to write (relative to the endpoint directory). The name can be a String ; a String with a File Language or Simple expression; or an Expression object. If it's null then Apache Camel will auto-generate a filename based on the message unique ID.
|
CamelFileNameProduced
|
The actual absolute filepath (path + name) for the output file that was written. This header is set by Camel and its purpose is providing end-users with the name of the file that was written. |
File consumer only Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelFileName
|
Name of the consumed file as a relative file path with offset from the starting directory configured on the endpoint. |
CamelFileNameOnly
|
Only the file name (the name with no leading paths). |
CamelFileAbsolute
|
A boolean option specifying whether the consumed file denotes an absolute path or not. Should normally be false for relative paths. Absolute paths should normally not be used but we added to the move option to allow moving files to absolute paths. But can be used elsewhere as well.
|
CamelFileAbsolutePath
|
The absolute path to the file. For relative files this path holds the relative path instead. |
CamelFilePath
|
The file path. For relative files this is the starting directory + the relative filename. For absolute files this is the absolute path. |
CamelFileRelativePath
|
The relative path. |
CamelFileParent
|
The parent path. |
CamelFileLength
|
A long value containing the file size.
|
CamelFileLastModified
|
A Date value containing the last modified timestamp of the file.
|
Batch Consumer Copier lienLien copié sur presse-papiers!
Exchange Properties, file consumer only Copier lienLien copié sur presse-papiers!
BatchConsumer
it supports batching the files it polls. By batching it means that Apache Camel will add some properties to the Exchange so you know the number of files polled the current index in that order.
Property | Description |
---|---|
CamelBatchSize
|
The total number of files that was polled in this batch. |
CamelBatchIndex
|
The current index of the batch. Starts from 0. |
CamelBatchComplete
|
A boolean value indicating the last Exchange in the batch. Is only true for the last entry.
|
Common gotchas with folder and filenames Copier lienLien copié sur presse-papiers!
ID-MACHINENAME-2443-1211718892437-1-0
. If such a filename is not desired, then you must provide a filename in the CamelFileName
message header. The constant, Exchange.FILE_NAME
, can also be used.
from("direct:report").to("file:target/reports");
from("direct:report").to("file:target/reports");
report.txt
as the filename you have to do:
from("direct:report").setHeader(Exchange.FILE_NAME, constant("report.txt")).to( "file:target/reports");
from("direct:report").setHeader(Exchange.FILE_NAME, constant("report.txt")).to( "file:target/reports");
CamelFileName
:
from("direct:report").setHeader("CamelFileName", constant("report.txt")).to( "file:target/reports");
from("direct:report").setHeader("CamelFileName", constant("report.txt")).to( "file:target/reports");
from("direct:report").to("file:target/reports/?fileName=report.txt");
from("direct:report").to("file:target/reports/?fileName=report.txt");
Filename Expression Copier lienLien copié sur presse-papiers!
CamelFileName
header. See the File Language for syntax and samples.
Consuming files from folders where others drop files directly Copier lienLien copié sur presse-papiers!
readLock
options to see what suits your use cases. The best approach is however to write to another folder and after the write move the file in the drop folder. However if you write files directly to the drop folder then the option changed
could better detect whether a file is currently being written/copied as it uses a file changed algorithm to see whether the file size / modification changes over a period of time. The other read lock options rely on Java File API that sadly is not always very good at detecting this. You may also want to look at the doneFileName
option, which uses a marker file (done) to signal when a file is done and ready to be consumed.
Using done files Copier lienLien copié sur presse-papiers!
doneFileName
option on the endpoint.
from("file:bar?doneFileName=done");
from("file:bar?doneFileName=done");
doneFileName
option. Currently Camel supports the following two dynamic tokens: file:name
and file:name.noext
which must be enclosed in ${ }. The consumer only supports the static part of the done file name as either prefix or suffix (not both).
from("file:bar?doneFileName=${file:name}.done");
from("file:bar?doneFileName=${file:name}.done");
hello.txt
- is the file to be consumedhello.txt.done
- is the associated done file
from("file:bar?doneFileName=ready-${file:name}");
from("file:bar?doneFileName=ready-${file:name}");
hello.txt
- is the file to be consumedready-hello.txt
- is the associated done file
Writing done files Copier lienLien copié sur presse-papiers!
doneFileName
option on the file producer endpoint.
.to("file:bar?doneFileName=done");
.to("file:bar?doneFileName=done");
done
in the same directory as the target file.
doneFileName
option. Currently Camel supports the following two dynamic tokens: file:name
and file:name.noext
which must be enclosed in ${ }
.
.to("file:bar?doneFileName=done-${file:name}");
.to("file:bar?doneFileName=done-${file:name}");
done-foo.txt
if the target file was foo.txt
in the same directory as the target file.
.to("file:bar?doneFileName=${file:name}.done");
.to("file:bar?doneFileName=${file:name}.done");
foo.txt.done
if the target file was foo.txt
in the same directory as the target file.
.to("file:bar?doneFileName=${file:name.noext}.done");
.to("file:bar?doneFileName=${file:name.noext}.done");
foo.done
if the target file was foo.txt
in the same directory as the target file.
Read from a directory and write to another directory Copier lienLien copié sur presse-papiers!
from("file://inputdir/?delete=true").to("file://outputdir")
from("file://inputdir/?delete=true").to("file://outputdir")
outputdir
and delete the file in the inputdir
.
Reading recursively from a directory and writing to another Copier lienLien copié sur presse-papiers!
from("file://inputdir/?recursive=true&delete=true").to("file://outputdir")
from("file://inputdir/?recursive=true&delete=true").to("file://outputdir")
outputdir
and delete the file in the inputdir
. Will scan recursively into sub-directories. Will lay out the files in the same directory structure in the outputdir
as the inputdir
, including any sub-directories.
inputdir/foo.txt inputdir/sub/bar.txt
inputdir/foo.txt
inputdir/sub/bar.txt
outputdir/foo.txt outputdir/sub/bar.txt
outputdir/foo.txt
outputdir/sub/bar.txt
Using flatten Copier lienLien copié sur presse-papiers!
flatten=true
option on the file producer side:
from("file://inputdir/?recursive=true&delete=true").to("file://outputdir?flatten=true")
from("file://inputdir/?recursive=true&delete=true").to("file://outputdir?flatten=true")
outputdir/foo.txt outputdir/bar.txt
outputdir/foo.txt
outputdir/bar.txt
Reading from a directory and the default move operation Copier lienLien copié sur presse-papiers!
.camel
subdirectory in the directory the file was consumed from.
from("file://inputdir/?recursive=true&delete=true").to("file://outputdir")
from("file://inputdir/?recursive=true&delete=true").to("file://outputdir")
inputdir/foo.txt inputdir/sub/bar.txt
inputdir/foo.txt
inputdir/sub/bar.txt
inputdir/.camel/foo.txt inputdir/sub/.camel/bar.txt outputdir/foo.txt outputdir/sub/bar.txt
inputdir/.camel/foo.txt
inputdir/sub/.camel/bar.txt
outputdir/foo.txt
outputdir/sub/bar.txt
Read from a directory and process the message in java Copier lienLien copié sur presse-papiers!
File
object that points to the file that was just dropped into the inputdir
directory.
Read files from a directory and send the content to a jms queue Copier lienLien copié sur presse-papiers!
from("file://inputdir/").convertBodyTo(String.class).to("jms:test.queue")
from("file://inputdir/").convertBodyTo(String.class).to("jms:test.queue")
FileMessage
which contains a File
object as the body. If you send this directly to the JMS component the JMS message will only contain the File
object but not the content. By converting the File
to a String
, the message will contain the file contents, which is probably what you want.
<route> <from uri="file://inputdir/"/> <convertBodyTo type="java.lang.String"/> <to uri="jms:test.queue"/> </route>
<route>
<from uri="file://inputdir/"/>
<convertBodyTo type="java.lang.String"/>
<to uri="jms:test.queue"/>
</route>
Writing to files Copier lienLien copié sur presse-papiers!
Write to subdirectory using Exchange.FILE_NAME Copier lienLien copié sur presse-papiers!
<route> <from uri="bean:myBean"/> <to uri="file:/rootDirectory"/> </route>
<route>
<from uri="bean:myBean"/>
<to uri="file:/rootDirectory"/>
</route>
myBean
set the header Exchange.FILE_NAME
to values such as:
Exchange.FILE_NAME = hello.txt => /rootDirectory/hello.txt Exchange.FILE_NAME = foo/bye.txt => /rootDirectory/foo/bye.txt
Exchange.FILE_NAME = hello.txt => /rootDirectory/hello.txt
Exchange.FILE_NAME = foo/bye.txt => /rootDirectory/foo/bye.txt
Using expression for filenames Copier lienLien copié sur presse-papiers!
from("file://inbox?move=backup/${date:now:yyyyMMdd}/${file:name}").to("...");
from("file://inbox?move=backup/${date:now:yyyyMMdd}/${file:name}").to("...");
Avoiding reading the same file more than once (idempotent consumer) Copier lienLien copié sur presse-papiers!
idempotent=true
option.
from("file://inbox?idempotent=true").to("...");
from("file://inbox?idempotent=true").to("...");
idempotentRepository
option using the #
sign in the value to indicate it's a referring to a bean in the Registry with the specified id
.
DEBUG
level if it skips a file because it has been consumed before:
DEBUG FileConsumer is idempotent and the file has been consumed before. Will skip this file: target\idempotent\report.txt
DEBUG FileConsumer is idempotent and the file has been consumed before. Will skip this file: target\idempotent\report.txt
Using a file based idempotent repository Copier lienLien copié sur presse-papiers!
org.apache.camel.processor.idempotent.FileIdempotentRepository
instead of the in-memory based that is used as default. This repository uses a 1st level cache to avoid reading the file repository. It will only use the file repository to store the content of the 1st level cache. Thereby the repository can survive server restarts. It will load the content of the file into the 1st level cache upon startup. The file structure is very simple as it stores the key in separate lines in the file. By default, the file store has a size limit of 1mb and when the file grows larger, Apache Camel will truncate the file store and rebuild the content by flushing the 1st level cache into a fresh empty file.
idempotentRepository
using \#
sign to indicate Registry lookup:
Using a JPA based idempotent repository Copier lienLien copié sur presse-papiers!
META-INF/persistence.xml
where we need to use the class org.apache.camel.processor.idempotent.jpa.MessageProcessed
as model.
jpaTemplate
in the spring XML file:
idempotentRepository
option and the #
syntax:
<route> <from uri="file://inbox?idempotent=true&dempotentRepository=#jpaStore"/> <to uri="bean:processInbox"/> </route>
<route>
<from uri="file://inbox?idempotent=true&dempotentRepository=#jpaStore"/>
<to uri="bean:processInbox"/>
</route>
Filter using org.apache.camel.component.file.GenericFileFilter Copier lienLien copié sur presse-papiers!
skip
in the filename:
#
notation) that we have defined in the spring XML file:
Filtering using ANT path matcher Copier lienLien copié sur presse-papiers!
?
matches one character*
matches zero or more characters**
matches zero or more directories in a path
Sorting using Comparator Copier lienLien copié sur presse-papiers!
java.util.Comparator
in Java. You can then configure the endpoint with such a comparator and have Apache Camel sort the files before being processed.
public class MyFileSorter implements Comparator<GenericFile> { public int compare(GenericFile o1, GenericFile o2) { return o1.getFileName().compareToIgnoreCase(o2.getFileName()); } }
public class MyFileSorter implements Comparator<GenericFile> {
public int compare(GenericFile o1, GenericFile o2) {
return o1.getFileName().compareToIgnoreCase(o2.getFileName());
}
}
mySorter
) we have defined in the spring XML file:
Sorting using sortBy Copier lienLien copié sur presse-papiers!
sortBy
option is configured as follows:
sortBy=group 1;group 2;group 3;...
sortBy=group 1;group 2;group 3;...
sortBy=file:name
sortBy=file:name
reverse:
to the group, so the sorting is now Z..A:
sortBy=reverse:file:name
sortBy=reverse:file:name
sortBy=file:length
sortBy=file:length
ignoreCase:
for string comparison, so if you want to use file name sorting but to ignore the case then we do:
sortBy=ignoreCase:file:name
sortBy=ignoreCase:file:name
sortBy=reverse:ignoreCase:file:name
sortBy=reverse:ignoreCase:file:name
sortBy=file:modifed
sortBy=file:modifed
sortBy=file:modifed;file:name
sortBy=file:modifed;file:name
sortBy=date:file:yyyyMMdd;file:name
sortBy=date:file:yyyyMMdd;file:name
sortBy=date:file:yyyyMMdd;reverse:file:name
sortBy=date:file:yyyyMMdd;reverse:file:name
Using GenericFileProcessStrategy Copier lienLien copié sur presse-papiers!
processStrategy
can be used to use a custom GenericFileProcessStrategy
that allows you to implement your own begin, commit and rollback logic. For instance lets assume a system writes a file in a folder you should consume. But you should not start consuming the file before another ready file have been written as well.
GenericFileProcessStrategy
we can implement this as:
- In the
begin()
method we can test whether the special ready file exists. The begin method returns aboolean
to indicate if we can consume the file or not. - in the
commit()
method we can move the actual file and also delete the ready file.
Debug logging Copier lienLien copié sur presse-papiers!
Chapter 31. Flatpack Copier lienLien copié sur presse-papiers!
Flatpack Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
flatpack:[delim|fixed]:flatPackConfig.pzmap.xml[?options]
flatpack:[delim|fixed]:flatPackConfig.pzmap.xml[?options]
flatpack:someName[?options]
flatpack:someName[?options]
?option=value&option=value&...
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
delimiter
|
,
|
The default character delimiter for delimited files. |
textQualifier
|
"
|
The text qualifier for delimited files. |
ignoreFirstRecord
|
true
|
Whether the first line is ignored for delimited files (for the column headers). |
splitRows
|
true
|
As of Apache Camel 1.5, the component can either process each row one by one or the entire content at once. |
allowShortLines
|
false
|
*Camel 2.9.3:* Allows for lines to be shorter than expected and ignores the extra characters. |
ignoreExtraColumns
|
false
|
*Camel 2.9.3:* Allows for lines to be longer than expected and ignores the extra characters. |
Examples Copier lienLien copié sur presse-papiers!
flatpack:fixed:foo.pzmap.xml
creates a fixed-width endpoint using thefoo.pzmap.xml
file configuration.flatpack:delim:bar.pzmap.xml
creates a delimited endpoint using thebar.pzmap.xml
file configuration.flatpack:foo
creates a delimited endpoint calledfoo
with no file configuration.
Message Headers Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
camelFlatpackCounter
|
The current row index. For splitRows=false the counter is the total number of rows.
|
Message Body Copier lienLien copié sur presse-papiers!
org.apache.camel.component.flatpack.DataSetList
object that has converters for java.util.Map
or java.util.List
. Usually you want the Map
if you process one row at a time (splitRows=true
). Use List
for the entire content (splitRows=false
), where each element in the list is a Map
. Each Map
contains the key for the column name and its corresponding value.
Map row = exchange.getIn().getBody(Map.class); String firstName = row.get("FIRSTNAME");
Map row = exchange.getIn().getBody(Map.class);
String firstName = row.get("FIRSTNAME");
List
(even for splitRows=true
). The same example:
List data = exchange.getIn().getBody(List.class); Map row = (Map)data.get(0); String firstName = row.get("FIRSTNAME");
List data = exchange.getIn().getBody(List.class);
Map row = (Map)data.get(0);
String firstName = row.get("FIRSTNAME");
Header and Trailer records Copier lienLien copié sur presse-papiers!
header
for the header record (must be lowercase)trailer
for the trailer record (must be lowercase)
Using the endpoint Copier lienLien copié sur presse-papiers!
Map
for easy Bean Integration
Chapter 32. FOP Copier lienLien copié sur presse-papiers!
FOP Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
fop://outputFormat?[options]
fop://outputFormat?[options]
Output Formats Copier lienLien copié sur presse-papiers!
name | outputFormat | description |
---|---|---|
application/pdf | Portable Document Format | |
PS | application/postscript | Adobe Postscript |
PCL | application/x-pcl | Printer Control Language |
PNG | image/png | PNG images |
JPEG | image/jpeg | JPEG images |
SVG | image/svg+xml | Scalable Vector Graphics |
XML | application/X-fop-areatree | Area tree representation |
MIF | application/mif | FrameMaker's MIF |
RTF | application/rtf | Rich Text Format |
TXT | text/plain | Text |
Endpoint Options Copier lienLien copié sur presse-papiers!
name | default value | description |
---|---|---|
userConfigURL | none | The location of a configuration file with the following structure |
Message Operations Copier lienLien copié sur presse-papiers!
name | default value | description |
---|---|---|
CamelFop.Output.Format | Overrides the output format for that message | |
CamelFop.Encrypt.userPassword | PDF user password | |
CamelFop.Encrypt.ownerPassword | PDF owner passoword | |
CamelFop.Encrypt.allowPrint | true | Allows printing the PDF |
CamelFop.Encrypt.allowCopyContent | true | Allows copying content of the PDF |
CamelFop.Encrypt.allowEditContent | true | Allows editing content of the PDF |
CamelFop.Encrypt.allowEditAnnotations | true | Allows editing annotation of the PDF |
CamelFop.Render.producer | Apache FOP | Metadata element for the system/software that produces the document |
CamelFop.Render.creator | Metadata element for the user that created the document | |
CamelFop.Render.creationDate | Creation Date | |
CamelFop.Render.author | Author of the content of the document | |
CamelFop.Render.title | Title of the document | |
CamelFop.Render.subject | Subject of the document | |
CamelFop.Render.keywords | Set of keywords applicable to this document |
Example Copier lienLien copié sur presse-papiers!
from("file:source/data/xml") .to("xslt:xslt/template.xsl") .to("fop:application/pdf") .to("file:target/data");
from("file:source/data/xml")
.to("xslt:xslt/template.xsl")
.to("fop:application/pdf")
.to("file:target/data");
Chapter 33. FTP2 Copier lienLien copié sur presse-papiers!
FTP/SFTP Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
ftp://[username@]hostname[:port]/directoryname[?options] sftp://[username@]hostname[:port]/directoryname[?options] ftps://[username@]hostname[:port]/directoryname[?options]
ftp://[username@]hostname[:port]/directoryname[?options]
sftp://[username@]hostname[:port]/directoryname[?options]
ftps://[username@]hostname[:port]/directoryname[?options]
anonymous
login is attempted using no password. If no port number is provided, Apache Camel will provide default values according to the protocol (ftp = 21, sftp = 22, ftps = 21).
?option=value&option=value&...
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
username
|
null
|
Specifies the username to use to log in to the remote file systen. |
password
|
null
|
Specifies the password to use to log in to the remote file system. |
binary
|
false
|
Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false ).
|
disconnect
|
false
|
Camel 2.2: Whether or not to disconnect from remote FTP server right after use. Can be used for both consumer and producer. Disconnect will only disconnect the current connection to the FTP server. If you have a consumer which you want to stop, then you need to stop the consumer/route instead. |
localWorkDirectory
|
null
|
When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote file and thus can conserve memory. See below for more details. |
passiveMode
|
false
|
FTP only: Specifies whether to use passive mode connections. Default is active mode {false ).
|
securityProtocol
|
TLS
|
FTPS only: Sets the underlying security protocol. The following values are defined:
TLS : Transport Layer Security SSL : Secure Sockets Layer
|
disableSecureDataChannelDefaults
|
false
|
Camel 2.4: FTPS only: Whether or not to disable using default values for execPbsz and execProt when using secure data transfer. You can set this option to true if you want to be in absolute full control what the options execPbsz and execProt should be used.
|
execProt
|
null
|
Camel 2.4: FTPS only: Will by default use option
P if secure data channel defaults hasn't been disabled. Possible values are: C : Clear S : Safe (SSL protocol only) E : Confidential (SSL protocol only) P : Private
|
execPbsz
|
null
|
Camel 2.4: FTPS only: This option specifies the buffer size of the secure data channel. If option useSecureDataChannel has been enabled and this option has not been explicit set, then value 0 is used.
|
isImplicit
|
false
|
FTPS only: Sets the security mode(implicit/explicit). Default is explicit (false ).
|
knownHostsFile
|
null
|
SFTP only: Sets the known_hosts file, so that the SFTP endpoint can do host key verification.
|
privateKeyFilePassphrase
|
null
|
SFTP only: Set the private key file passphrase to that the SFTP endpoint can do private key verification. |
privateKeyFilePassphrase
|
null
|
SFTP only: Set the private key file passphrase to that the SFTP endpoint can do private key verification. |
ciphers
|
null
|
*Camel 2.8.2, 2.9: SFTP only* Set a comma separated list of ciphers that will be used in order of preference. Possible cipher names are defined by JCraft JSCH. Some examples include: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc. If not specified the default list from JSCH will be used. |
fastExistsCheck
|
false
|
*Camel 2.8.2, 2.9:* If set this option to be true, camel-ftp will use the list file directly to check if the file exists. Since some FTP server may not support to list the file directly, if the option is false, camel-ftp will use the old way to list the directory and check if the file exists. Note from Camel 2.10.1 onwards this option also influences readLock=changed to control whether it performs a fast check to update file information or not. This can be used to speed up the process if the FTP server has a lot of files.
|
strictHostKeyChecking
|
no
|
SFTP only:Camel 2.2: Sets whether to use strict host key checking. Possible values are: no , yes and ask . ask does not make sense to use as Camel cannot answer the question for you as its meant for human intervention. Note: The default in Camel 2.1 and below was ask .
|
maximumReconnectAttempts
|
3 | Specifies the maximum reconnect attempts Apache Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior. |
reconnectDelay
|
1000 | Delay in millis Apache Camel will wait before performing a reconnect attempt. |
connectTimeout
|
10000
|
Camel 2.4: Is the connect timeout in millis. This corresponds to using ftpClient.connectTimeout for the FTP/FTPS. For SFTP this option is also used when attempting to connect.
|
soTimeout
|
null
|
FTP and FTPS Only:Camel 2.4: Is the SocketOptions.SO_TIMEOUT value in millis. Note SFTP will automatic use the connectTimeout as the soTimeout .
|
timeout
|
30000
|
FTP and FTPS Only:Camel 2.4: Is the data timeout in millis. This corresponds to using ftpClient.dataTimeout for the FTP/FTPS. For SFTP there is no data timeout.
|
throwExceptionOnConnectFailed
|
false
|
Camel 2.5: Whether or not to thrown an exception if a successful connection and login could not be establish. This allows a custom pollStrategy to deal with the exception, for example to stop the consumer or the likes.
|
siteCommand
|
null
|
FTP and FTPS Only:Camel 2.5: To execute site commands after successful login. Multiple site commands can be separated using a new line character (\n). Use help site to see which site commands your FTP server supports.
|
stepwise
|
true
|
When consuming directories, specifies whether or not to use stepwise mode for traversing the directory tree. Stepwise means that it will CD one directory at a time. For more details, see the section called “Stepwise changing directories”. |
separator
|
Auto
|
Camel 2.6: Dictates what path separator char to use when uploading files. Auto means use the path provided without altering it. UNIX means use UNIX style path separators. Windows means use Windows style path separators.
|
chmod
|
null
|
*SFTP Producer Only:* Camel 2.9: Allows you to set chmod on the stored file. For example chmod=640 .
|
compression
|
0 | *SFTP Only:* Camel 2.8.3/2.9: To use compression. Specify a level from 1 to 10. Important: You must manually add the needed JSCH zlib JAR to the classpath for compression support. |
ftpClient
|
null
|
FTP and FTPS Only:Camel 2.1: Allows you to use a custom org.apache.commons.net.ftp.FTPClient instance.
|
ftpClientConfig
|
null
|
FTP and FTPS Only:Camel 2.1: Allows you to use a custom org.apache.commons.net.ftp.FTPClientConfig instance.
|
serverAliveInterval
|
0
|
SFTP Only:Camel 2.8 Allows you to set the serverAliveInterval of the sftp session |
serverAliveCountMax
|
1
|
SFTP Only:Camel 2.8 Allows you to set the serverAliveCountMax of the sftp session |
ftpClient.trustStore.file
|
null
|
FTPS Only: Sets the trust store file, so that the FTPS client can look up for trusted certificates. |
ftpClient.trustStore.type
|
JKS
|
FTPS Only: Sets the trust store type. |
ftpClient.trustStore.algorithm
|
SunX509
|
FTPS Only: Sets the trust store algorithm. |
ftpClient.trustStore.password
|
null
|
FTPS Only: Sets the trust store password. |
ftpClient.keyStore.file
|
null
|
FTPS Only: Sets the key store file, so that the FTPS client can look up for the private certificate. |
ftpClient.keyStore.type
|
JKS
|
FTPS Only: Sets the key store type. |
ftpClient.keyStore.algorithm
|
SunX509
|
FTPS Only: Sets the key store algorithm. |
ftpClient.keyStore.password
|
null
|
FTPS Only: Sets the key store password. |
ftpClient.keyStore.keyPassword
|
null
|
FTPS Only: Sets the private key password. |
sslContextParameters
|
null
|
*FTPS Only:* Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSL related options on ftpClient as well as the securityProtocol (SSL, TLS, etc.) set on FtpsConfiguration. See Using the JSSE Configuration Utility.
|
ftpClient.
properties related to SSL with the FTPS component, the trust store accept all certificates. If you only want trust selective certificates, you have to configure the trust store with the ftpClient.trustStore.xxx
options or by configuring a custom ftpClient
.
sslContextParameters
, the trust store is managed by the configuration of the provided SSLContextParameters instance.
ftpClient
and ftpClientConfig
from the URI directly by using the ftpClient.
or ftpClientConfig.
prefix.
setDataTimeout
on the FTPClient
to 30 seconds you can do:
from("ftp://foo@myserver?password=secret&ftpClient.dataTimeout=30000") .to("bean:foo");
from("ftp://foo@myserver?password=secret&ftpClient.dataTimeout=30000")
.to("bean:foo");
from("ftp://foo@myserver?password=secret&ftpClient.dataTimeout=30000&ftpClientConfig.serverLanguageCode=fr") .to("bean:foo");
from("ftp://foo@myserver?password=secret&ftpClient.dataTimeout=30000&ftpClientConfig.serverLanguageCode=fr")
.to("bean:foo");
ftpClient
or ftpClientConfig
to use by letting Camel lookup in the Registry for it.
from("ftp://foo@myserver?password=secret&ftpClientConfig=#myConfig").to("bean:foo");
from("ftp://foo@myserver?password=secret&ftpClientConfig=#myConfig").to("bean:foo");
More URI options Copier lienLien copié sur presse-papiers!
Examples Copier lienLien copié sur presse-papiers!
ftp://someone@someftpserver.com/public/upload/images/holiday2008?password=secret&binary=true ftp://someoneelse@someotherftpserver.co.uk:12049/reports/2008/password=secret&binary=false ftp://publicftpserver.com/download
ftp://someone@someftpserver.com/public/upload/images/holiday2008?password=secret&binary=true
ftp://someoneelse@someotherftpserver.co.uk:12049/reports/2008/password=secret&binary=false
ftp://publicftpserver.com/download
Default when consuming files Copier lienLien copié sur presse-papiers!
delete=true
to delete the files, or use move=.done
to move the files into a hidden done sub directory.
.camel
sub directory. The reason Camel does not do this by default for the FTP consumer is that it may lack permissions by default to be able to move or delete files.
limitations Copier lienLien copié sur presse-papiers!
Message Headers Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelFileName
|
Specifies the output file name (relative to the endpoint directory) to be used for the output message when sending to the endpoint. If this is not present and no expression either, then a generated message ID is used as the filename instead. |
CamelFileNameProduced
|
The actual absolute filepath (path + name) for the output file that was written. This header is set by Apache Camel and its purpose is providing end-users the name of the file that was written. |
CamelFileBatchIndex
|
Current index out of total number of files being consumed in this batch. |
CamelFileBatchSize
|
Total number of files being consumed in this batch. |
CamelFileHost
|
The remote hostname. |
CamelFileLocalWorkPath
|
Path to the local work file, if local work directory is used. |
About timeouts Copier lienLien copié sur presse-papiers!
connectTimeout
option for both of them to set a timeout in milliseconds to establish a network connection. An individual soTimeout
can also be set on the FTP/FTPS, which corresponds to using ftpClient.soTimeout
. Notice SFTP will automatically use connectTimeout
as its soTimeout
. The timeout
option only applies for FTP/FTSP as the data timeout, which corresponds to the ftpClient.dataTimeout
value. All timeout values are in milliseconds.
Using Local Work Directory Copier lienLien copié sur presse-papiers!
FileOutputStream
.
.inprogress
as extension while the file is being downloaded. Afterwards, the file is renamed to remove the .inprogress
suffix. And finally, when the Exchange is complete the local file is deleted.
from("ftp://someone@someserver.com?password=secret&localWorkDirectory=/tmp").to("file://inbox");
from("ftp://someone@someserver.com?password=secret&localWorkDirectory=/tmp").to("file://inbox");
java.io.File
handle is then used as the Exchange body. The file producer leverages this fact and can work directly on the work file java.io.File
handle and perform a java.io.File.rename
to the target filename. As Apache Camel knows it's a local work file, it can optimize and use a rename instead of a file copy, as the work file is meant to be deleted anyway.
Stepwise changing directories Copier lienLien copié sur presse-papiers!
- stepwise
- not stepwise
/
.
/ /one /one/two /one/two/sub-a /one/two/sub-b
/
/one
/one/two
/one/two/sub-a
/one/two/sub-b
sub-a
(a.txt
) and sub-b
(b.txt
) folder.
Using stepwise=true (default mode) Copier lienLien copié sur presse-papiers!
Using stepwise=false Copier lienLien copié sur presse-papiers!
Samples Copier lienLien copié sur presse-papiers!
<route> <from uri="ftp://scott@localhost/public/reports?password=tiger&inary=true&elay=60000"/> <to uri="file://target/test-reports"/> </route>
<route>
<from uri="ftp://scott@localhost/public/reports?password=tiger&inary=true&elay=60000"/>
<to uri="file://target/test-reports"/>
</route>
Consuming a remote FTP server triggered by a route Copier lienLien copié sur presse-papiers!
from("seda:start") // set the filename in FILE_NAME header so Apache Camel know the name of the remote file to poll .setHeader(Exchange.FILE_NAME, header("myfile")) .pollEnrich("ftp://admin@localhost:21/getme?password=admin&binary=false") .to("mock:result");
from("seda:start")
// set the filename in FILE_NAME header so Apache Camel know the name of the remote file to poll
.setHeader(Exchange.FILE_NAME, header("myfile"))
.pollEnrich("ftp://admin@localhost:21/getme?password=admin&binary=false")
.to("mock:result");
Consuming a remote FTPS server (implicit SSL) and client authentication Copier lienLien copié sur presse-papiers!
Consuming a remote FTPS server (explicit TLS) and a custom trust store configuration Copier lienLien copié sur presse-papiers!
from("ftps://admin@localhost:2222/public/camel?password=admin&ftpClient.trustStore.file=./src/test/resources/server.jks&ftpClient.trustStore.password=password") .to("bean:foo");
from("ftps://admin@localhost:2222/public/camel?password=admin&ftpClient.trustStore.file=./src/test/resources/server.jks&ftpClient.trustStore.password=password")
.to("bean:foo");
Filter using org.apache.camel.component.file.GenericFileFilter Copier lienLien copié sur presse-papiers!
org.apache.camel.component.file.GenericFileFilter
interface in Java. You can then configure the endpoint with the filter to skip certain files.
report
.
#
notation) that we have defined in the spring XML file:
Filtering using ANT path matcher Copier lienLien copié sur presse-papiers!
?
matches one character*
matches zero or more characters**
matches zero or more directories in a path
Debug logging Copier lienLien copié sur presse-papiers!
Chapter 34. GAE Copier lienLien copié sur presse-papiers!
34.1. Introduction to the GAE Components Copier lienLien copié sur presse-papiers!
Apache Camel Components for Google App Engine Copier lienLien copié sur presse-papiers!
- A good starting point for using Apache Camel on GAE is the Tutorial for Camel on Google App Engine
- The OAuth tutorial demonstrates how to implement OAuth in web applications.
camel-gae
project and provide connectivity to GAE's cloud computing services. They make the GAE cloud computing environment accessible to applications via Apache Camel interfaces. Following this pattern for other cloud computing environments could make it easier to port Apache Camel applications from one cloud computing provider to another. The following table lists the cloud computing services provided by Google App Engine and the supporting Apache Camel components. The documentation of each component can be found by following the link in the Camel Component column.
GAE service | Camel component | Component description |
---|---|---|
URL fetch service | ghttp | Provides connectivity to the GAE URL fetch service but can also be used to receive messages from servlets. |
Task queueing service | gtask | Supports asynchronous message processing on GAE by using the task queueing service as message queue. |
Mail service | gmail | Supports sending of emails via the GAE mail service. Receiving mails is not supported yet but will be added later. |
Memcache service | Not supported yet. | |
XMPP service | Not supported yet. | |
Images service | Not supported yet. | |
Datastore service | Not supported yet. | |
Accounts service | gauth glogin | These components interact with the Google Accounts API for authentication and authorization. Google Accounts is not specific to Google App Engine but is often used by GAE applications for implementing security. The gauth component is used by web applications to implement a Google-specific OAuth consumer. This component can also be used to OAuth-enable non-GAE web applications. The glogin component is used by Java clients (outside GAE) for programmatic login to GAE applications. For instructions how to protect GAE applications against unauthorized access refer to the Security for page. |
Camel context Copier lienLien copié sur presse-papiers!
SpringCamelContext
on Google App Engine differs between Camel 2.1 and higher versions. The problem is that usage of the Camel-specific Spring configuration XML schema from the http://camel.apache.org/schema/spring
namespace requires JAXB and Camel 2.1 depends on a Google App Engine SDK version that doesn't support JAXB yet. This limitation has been removed since Camel 2.2.
javax.management
package isn't on the App Engine JRE whitelist.
Apache Camel 2.1 Copier lienLien copié sur presse-papiers!
camel-gae
2.1 comes with the following CamelContext
implementations.
org.apache.camel.component.gae.context.GaeDefaultCamelContext
(extendsorg.apache.camel.impl.DefaultCamelContext
)org.apache.camel.component.gae.context.GaeSpringCamelContext
(extendsorg.apache.camel.spring.SpringCamelContext
)
GaeSpringCamelContext
additionally provides setter methods adding route builders as shown in the next example.
routeBuilders
property of the GaeSpringCamelContext
for setting a list of route builders. Using this approach, a SpringCamelContext
can be configured on GAE without the need for JAXB.
Apache Camel 2.2 Copier lienLien copié sur presse-papiers!
http://camel.apache.org/schema/spring
namespace for configuring a SpringCamelContext
but still need to disable JMX. Here's an example.
The web.xml Copier lienLien copié sur presse-papiers!
CamelHttpTransportServlet
from camel-servlet
. The following example shows how to configure this servlet together with a Spring application context XML file.
contextConfigLocation
init parameter. The appctx.xml
file must be on the classpath. The servlet mapping makes the Apache Camel application accessible under http://<appname>.appspot.com/camel/...
when deployed to Google App Engine where <appname>
must be replaced by a real GAE application name. The second servlet mapping is used internally by the task queueing service for background processing via web hooks. This mapping is relevant for the gtask component and is explained there in more detail.
34.2. gauth Copier lienLien copié sur presse-papiers!
gauth Component Copier lienLien copié sur presse-papiers!
gauth
component is used by web applications to implement a Google-specific OAuth consumer. It will be later extended to support other OAuth providers as well. Although this component belongs to the Camel Components for Google App Engine (GAE), it can also be used to OAuth-enable non-GAE web applications. For a detailed description of Google's OAuth implementation refer to the Google OAuth API reference.
URI format Copier lienLien copié sur presse-papiers!
gauth://name[?options]
gauth://name[?options]
name
can be either authorize
or upgrade
. An authorize
endpoint is used to obtain an unauthorized request token from Google and to redirect the user to the authorization page. The upgrade
endpoint is used to process OAuth callbacks from Google and to upgrade an authorized request token to a long-lived access token. Refer to the usage section for an example.
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Required | Description |
---|---|---|---|
callback
|
null
|
true (can alternatively be set via GAuthAuthorizeBinding.GAUTH_CALLBACK message header)
|
URL where to redirect the user after having granted or denied access. |
scope
|
null
|
true (can alternatively be set via GAuthAuthorizeBinding.GAUTH_SCOPE message header)
|
URL identifying the service(s) to be accessed. Scopes are defined by each Google service; see the service's documentation for the correct value. To specify more than one scope, list each one separated with a comma. Example: http://www.google.com/calendar/feeds/ .
|
consumerKey
|
null
|
true (can alternatively be set on component-level). |
Domain identifying the web application. This is the domain used when registering the application with Google. Example: camelcloud.appspot.com . For a non-registered application use anonymous .
|
consumerSecret
|
null
|
one of consumerSecret or keyLoaderRef is required (can alternatively be set on component-level).
|
Consumer secret of the web application. The consumer secret is generated when when registering the application with Google. It is needed if the HMAC-SHA1 signature method shall be used. For a non-registered application use anonymous .
|
keyLoaderRef
|
null
|
one of consumerSecret or keyLoaderRef is required (can be alternatively set on component-level)
|
Reference to a private key loader in the registry. Part of camel-gae are two key loaders: GAuthPk8Loader for loading a private key from a PKCS#8 file and GAuthJksLoader to load a private key from a Java key store. It is needed if the RSA-SHA1 signature method shall be used. These classes are defined in the org.apache.camel.component.gae.auth package.
|
authorizeBindingRef
|
Reference to GAuthAuthorizeBinding
|
false |
Reference to a OutboundBinding<GAuthEndpoint, GoogleOAuthParameters, GoogleOAuthParameters> in the registry for customizing how an Exchange is bound to GoogleOAuthParameters . This binding is used for teh authorization phase. Most applications won't change the default value.
|
upgradeBindingRef
|
Reference to GAuthAuthorizeBinding
|
false |
Reference to a OutboundBinding<GAuthEndpoint, GoogleOAuthParameters, GoogleOAuthParameters> in the registry. for customizing how an Exchange is bound to GoogleOAuthParameters . This binding is used for teh token upgrade phase. Most applications won't change the default value.
|
Message headers Copier lienLien copié sur presse-papiers!
Name | Type | Endpoint | Message | Description |
---|---|---|---|---|
GAuthAuthorizeBinding.GAUTH_CALLBACK
|
String
|
gauth:authorize
|
in |
Overrides the callback option.
|
GAuthAuthorizeBinding.GAUTH_SCOPE
|
String
|
gauth:authorize
|
in |
Overrides the scope option.
|
GAuthUpgradeBinding.GAUTH_ACCESS_TOKEN
|
String
|
gauth:upgrade
|
out | Contains the long-lived access token. This token should be stored by the applications in context of a user. |
GAuthUpgradeBinding.GAUTH_ACCESS_TOKEN_SECRET
|
String
|
gauth:upgrade
|
out | Contains the access token secret. This token secret should be stored by the applications in context of a user. |
Message body Copier lienLien copié sur presse-papiers!
gauth
component doesn't read or write message bodies.
Component configuration Copier lienLien copié sur presse-papiers!
consumerKey
, consumerSecret
or keyLoader
are usually set to the same values on gauth:authorize
and gauth:upgrade
endpoints. The gauth
component allows to configure them on component-level. These settings are then inherited by gauth
endpoints and need not be set redundantly in the endpoint URIs. Here are some configuration examples.
Usage Copier lienLien copié sur presse-papiers!
gauth.example.org
.
http://gauth.example.org/authorize
. The user is then redirected to a Google authorization page. After having granted access on this page, Google redirects the user to the web application which handles the callback and finally obtains a long-lived access token from Google.
servlet
component instead of the jetty
component.
- Application should store the access token in context of the current user. If the user logs in next time, the access token can directly be loaded from the database, for example, without doing the OAuth dance again.
- The access token is then used to get access to Google services, such as a Google Calendar API, on behalf of the user. Java applications will most likely use the GData Java library for that. See below for an example how to use the access token with the GData Java library to read a user's calendar feed.
- The user can revoke the access token at any time from his Google Accounts page. In this case, access to the corresponding Google service will throw an authorization exception. The web application should remove the stored access token and redirect the user again to the Google authorization page for creating another one.
consumerKey
and consumerSecret
settings.
GAE example Copier lienLien copié sur presse-papiers!
camelcloud.appspot.com
a configuration might look as follows. Here, the ghttp component is used to handle HTTP(S) requests instead of the jetty
component.
Access token usage Copier lienLien copié sur presse-papiers!
stdout
.
34.3. ghttp Copier lienLien copié sur presse-papiers!
ghttp Component Copier lienLien copié sur presse-papiers!
ghttp
component contributes to the Camel Components for Google App Engine (GAE). It provides connectivity to the GAE URL fetch service but can also be used to receive messages from servlets (the only way to receive HTTP requests on GAE). This is achieved by extending the Servlet component
. As a consequence, ghttp
URI formats and options sets differ on the consumer-side (from
) and producer-side (to
).
URI format Copier lienLien copié sur presse-papiers!
Format | Context | Comment |
---|---|---|
ghttp:///path[?options]
|
Consumer | See also Servlet component |
ghttp://hostname[:port][/path][?options] ghttps://hostname[:port][/path][?options]
|
Producer | See also Http component |
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
bridgeEndpoint
|
true
|
Producer |
If set to true the Exchange.HTTP_URI header will be ignored. To override the default endpoint URI with the Exchange.HTTP_URI header set this option to false .
|
throwExceptionOnFailure
|
true
|
Producer |
Throw a org.apache.camel.component.gae.http if the response code is >= 400. To disable throwing an exception set this option to false .
|
inboundBindingRef
|
reference to GHttpBinding
|
Consumer |
Reference to an InboundBinding<GHttpEndpoint, HttpServletRequest, HttpServletResponse> in the Registry for customizing the binding of an Exchange to the Servlet API. The referenced binding is used as post-processor to org.apache.camel.component.http.HttpBinding .
|
outboundBindingRef
|
reference to GHttpBinding
|
Producer |
Reference to an OutboundBinding<GHttpEndpoint, HTTPRequest, HTTPResponse> in the Registry for customizing the binding of an Exchange to the URLFetchService .
|
Message headers Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
Exchange.CONTENT_TYPE
|
String
|
The HTTP content type. Is set on both the in and out message to provide a content type, such as text/html .
|
Exchange.CONTENT_ENCODING
|
String
|
The HTTP content encoding. Is set on both the in and out message to provide a content encoding, such as gzip .
|
Exchange.HTTP_METHOD
|
String
|
The HTTP method to execute. One of GET , POST , PUT and DELETE . If not set, POST will be used if the message body is not null , GET otherwise.
|
Exchange.HTTP_QUERY
|
String
|
Overrides the query part of the endpoint URI or the the query part of Exchange.HTTP_URI (if defined). The query string must be in decoded form.
|
Exchange.HTTP_URI
|
String
|
Overrides the default endpoint URI if the bridgeEndpoint option is set to false . The URI string must be in decoded form.
|
Exchange.RESPONSE_CODE
|
int
|
The HTTP response code from URL fetch service responses. |
Message body Copier lienLien copié sur presse-papiers!
in
message body is converted to a byte[]
. The out
message body is made available as InputStream
. If the reponse size exceeds 1 megabyte a ResponseTooLargeException is thrown by the URL fetch service (see quotas and limits).
Receiving messages Copier lienLien copié sur presse-papiers!
ghttp
component, a CamelHttpTransportServlet
must be configured and mapped in the application's web.xml
(see the section called “The web.xml”). For example, to handle requests targeted at http://<appname>.appspot.com/camel/*
or http://localhost/camel/*
(when using a local development server) the following servlet mapping must be defined:
from("ghttp:///greeting").transform().constant("Hello")
from("ghttp:///greeting").transform().constant("Hello")
http://<appname>.appspot.com/camel/greeting
. In this example, the request body is ignored and the response body is set to Hello
. Requests targeted at http://<appname>.appspot.com/camel/greeting/*
are not processed by default. This requires setting the option matchOnUriPrefix
to true
.
from("ghttp:///greeting?matchOnUriPrefix=true").transform().constant("Hello")
from("ghttp:///greeting?matchOnUriPrefix=true").transform().constant("Hello")
Sending messages Copier lienLien copié sur presse-papiers!
ghttp
component uses the URL fetch service. For example, the Apache Camel homepage can the retrieved with the following endpoint definition on the producer-side.
from(...) ... .to("ghttp://camel.apache.org") ...
from(...)
...
.to("ghttp://camel.apache.org")
...
Exchange.HTTP_METHOD
message header or on the presence of an in-message body (GET
if null
, POST
otherwise). Retrieving the Camel homepage via a GAE application is as simple as
from("ghttp:///home") .to("ghttp://camel.apache.org")
from("ghttp:///home")
.to("ghttp://camel.apache.org")
GET
request to http://<appname>.appspot.com/camel/home
returns the Camel homepage. HTTPS-based communication with external services can be enabled with the ghttps
scheme.
from(...) ... .to("ghttps://svn.apache.org/repos/asf/camel/trunk/") ...
from(...)
...
.to("ghttps://svn.apache.org/repos/asf/camel/trunk/")
...
Dependencies Copier lienLien copié sur presse-papiers!
pom.xml
.
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-gae</artifactId> <version>${camel-version}</version> </dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-gae</artifactId>
<version>${camel-version}</version>
</dependency>
${camel-version}
must be replaced by the actual version of Apache Camel (2.1.0 or higher).
34.4. glogin Copier lienLien copié sur presse-papiers!
glogin Component Copier lienLien copié sur presse-papiers!
glogin
component is used by Apache Camel applications outside Google App Engine (GAE) for programmatic login to GAE applications. It is part of the Chapter 34, GAE. Security-enabled GAE applications normally redirect the user to a login page. After submitting username and password for authentication, the user is redirected back to the application. That works fine for applications where the client is a browser. For all other applications, the login process must be done programmatically. All the necessary steps for programmatic login are implemented by the glogin
component. These are
- Get an authentication token from Google Accounts via the ClientLogin API.
- Get an authorization cookie from Google App Engine's login API.
URI format Copier lienLien copié sur presse-papiers!
glogin://hostname[:port][?options]
glogin://hostname[:port][?options]
hostname
is either the internet hostname of a GAE application (e.g. camelcloud.appspot.com
) or the name of the host where the development server is running (e.g. localhost
). The port
is only used when connecting to a development server (i.e. when devMode=true
, see options) and defaults to 8080
.
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Required | Description |
---|---|---|---|
clientName
|
apache-camel-2.x
|
false |
A client name with recommended (but not required) format <organization>\-<appname>\-<version> .
|
userName
|
null
|
true (can alternatively be set via GLoginBinding.GLOGIN_USER_NAME message header)
|
Login username (an email address). |
password
|
null
|
true (can alternatively be set via GLoginBinding.GLOGIN_PASSWORD message header)
|
Login password. |
devMode
|
false
|
false |
If set to true a login to a development server is attempted.
|
devAdmin
|
false
|
false |
If set to true a login to a development server in admin role is attempted.
|
Message headers Copier lienLien copié sur presse-papiers!
Name | Type | Message | Description |
---|---|---|---|
GLoginBinding.GLOGIN_HOST_NAME
|
String
|
in | Overrides the hostname defined in the endpoint URI. |
GLoginBinding.GLOGIN_USER_NAME
|
String
|
in |
Overrides the userName option.
|
GLoginBinding.GLOGIN_PASSWORD
|
String
|
in |
Overrides the password option.
|
GLoginBinding.GLOGIN_TOKEN
|
String
|
out | Contains the authentication token obtained from Google Accounts. Login to a development server does not set this header. |
GLoginBinding.GLOGIN_COOKIE
|
String
|
out | Contains the application-specific authorization cookie obtained from Google App Engine (or a development server). |
Message body Copier lienLien copié sur presse-papiers!
glogin
component doesn't read or write message bodies.
Usage Copier lienLien copié sur presse-papiers!
ahlogincookie=test@example.org:false:11223191102230730701;Path=/
ahlogincookie=test@example.org:false:11223191102230730701;Path=/
ACSID=AJKiYcE...XxhH9P_jR_V3; expires=Sun, 07-Feb-2010 15:14:51 GMT; path=/
ACSID=AJKiYcE...XxhH9P_jR_V3; expires=Sun, 07-Feb-2010 15:14:51 GMT; path=/
34.5. gmail Copier lienLien copié sur presse-papiers!
gmail Component Copier lienLien copié sur presse-papiers!
gmail
component contributes to the Camel Components for Google App Engine (GAE). It supports sending of emails via the GAE mail service. Receiving mails is not supported yet but will be added later. Currently, only Google accounts that are application administrators can send emails.
URI format Copier lienLien copié sur presse-papiers!
gmail://user@gmail.com[?options] gmail://user@googlemail.com[?options]
gmail://user@gmail.com[?options]
gmail://user@googlemail.com[?options]
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
to
|
null
|
Producer | To-receiver of the email. This can be a single receiver or a comma-separated list of receivers. |
cc
|
null
|
Producer | Cc-receiver of the email. This can be a single receiver or a comma-separated list of receivers. |
bcc
|
null
|
Producer | Bcc-receiver of the email. This can be a single receiver or a comma-separated list of receivers. |
subject
|
null
|
Producer | Subject of the email. |
outboundBindingRef
|
reference to GMailBinding
|
Producer |
Reference to an OutboundBinding<GMailEndpoint, MailService.Message, void> in the Registry for customizing the binding of an Exchange to the mail service.
|
Message headers Copier lienLien copié sur presse-papiers!
Name | Type | Context | Description |
---|---|---|---|
GMailBinding.GMAIL_SUBJECT
|
String
|
Producer |
Subject of the email. Overrides subject endpoint option.
|
GMailBinding.GMAIL_SENDER
|
String
|
Producer | Sender of the email. Overrides sender definition in endpoint URI. |
GMailBinding.GMAIL_TO
|
String
|
Producer |
To-receiver(s) of the email. Overrides to endpoint option.
|
GMailBinding.GMAIL_CC
|
String
|
Producer |
Cc-receiver(s) of the email. Overrides cc endpoint option.
|
GMailBinding.GMAIL_BCC
|
String
|
Producer |
Bcc-receiver(s) of the email. Overrides bcc endpoint option.
|
Message body Copier lienLien copié sur presse-papiers!
in
message body is converted to a String
.
Usage Copier lienLien copié sur presse-papiers!
... .setHeader(GMailBinding.GMAIL_SUBJECT, constant("Hello")) .setHeader(GMailBinding.GMAIL_TO, constant("account2@somewhere.com")) .to("gmail://account1@gmail.com");
...
.setHeader(GMailBinding.GMAIL_SUBJECT, constant("Hello"))
.setHeader(GMailBinding.GMAIL_TO, constant("account2@somewhere.com"))
.to("gmail://account1@gmail.com");
Hello
from account1@gmail.com
to account2@somewhere.com
. The mail message body is taken from the in
message body. Please note that account1@gmail.com
must be an administrator account for the current GAE application.
Dependencies Copier lienLien copié sur presse-papiers!
pom.xml
.
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-gae</artifactId> <version>${camel-version}</version> </dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-gae</artifactId>
<version>${camel-version}</version>
</dependency>
$\{camel-version\
} must be replaced by the actual version of Apache Camel (2.1.0 or higher).
34.6. gsec Copier lienLien copié sur presse-papiers!
Security for Apache Camel GAE Applications Copier lienLien copié sur presse-papiers!
web.xml
file (see the section called “The web.xml”). This applies to Apache Camel applications as well. In the following example, the application is configured to only allow authenticated users (in any role) to access the application. Additionally, access to /worker/\*
URLs masy only be done by users in the admin role. By default, web hook URLs installed by the gtask component match the /worker/\*
pattern and should not be accessed by normal users. With this authorization constraint, only the task queuing service (which is always in the admin role) is allowed to access the web hooks. For implementing custom, non-declarative authorization logic, Apache Camel GAE applications should use the Google Accounts Java API.
Example 34.1. web.xml with authorization constraint
34.7. gtask Copier lienLien copié sur presse-papiers!
gtask Component Copier lienLien copié sur presse-papiers!
gtask
component contributes to the Camel Components for Google App Engine (GAE). It supports asynchronous message processing on GAE by using the task queueing service as message queue. For adding messages to a queue it uses the task queue API. For receiving messages from a queue it installs an HTTP callback handler. The handler is called by an HTTP POST callback (a web hook) initiated by the task queueing service. Whenever a new task is added to a queue a callback will be sent. The gtask
component abstracts from these details and supports endpoint URIs that make message queueing on GAE as easy as message queueing with JMS or SEDA.
URI format Copier lienLien copié sur presse-papiers!
gtask://queue-name
gtask://queue-name
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Context | Description |
---|---|---|---|
workerRoot
|
worker
|
Producer |
The servlet mapping for callback handlers. By default, this component requires a callback servlet mapping of /worker/* . If another servlet mapping is used e.g. /myworker/* it must be set as option on the producer side: to("gtask:myqueue?workerRoot=myworker") .
|
inboundBindingRef
|
reference to GTaskBinding
|
Consumer |
Reference to an InboundBinding<GTaskEndpoint, HttpServletRequest, HttpServletResponse> in the Registry for customizing the binding of an Exchange to the Servlet API. The referenced binding is used as post-processor to org.apache.camel.component.http.HttpBinding .
|
outboundBindingRef
|
reference to GTaskBinding
|
Producer |
Reference to an OutboundBinding<GTaskEndpoint, TaskOptions, void> in the Registry for customizing the binding of an Exchange to the task queueing service.
|
Message headers Copier lienLien copié sur presse-papiers!
Name | Type | Context | Description |
---|---|---|---|
GTaskBinding.GTASK_QUEUE_NAME
|
String
|
Consumer | Name of the task queue. |
GTaskBinding.GTASK_TASK_NAME
|
String
|
Consumer | Name of the task (generated value). |
GTaskBinding.GTASK_RETRY_COUNT
|
int
|
Consumer | Number of callback retries. |
Message body Copier lienLien copié sur presse-papiers!
in
message body is converted to a byte[]
and is POSTed to the callback handler as content-type application/octet-stream
.
Usage Copier lienLien copié sur presse-papiers!
default
queue. This queue will be used in the following examples. Please note that when using task queues on the local development server, tasks must be executed manually from the developer console.
Default queue Copier lienLien copié sur presse-papiers!
... .to(gtask:default) // add message to default queue from(gtask:default) // receive message from default queue (via a web hook) ...
...
.to(gtask:default) // add message to default queue
from(gtask:default) // receive message from default queue (via a web hook)
...
Dependencies Copier lienLien copié sur presse-papiers!
pom.xml
.
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-gae</artifactId> <version>${camel-version}</version> </dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-gae</artifactId>
<version>${camel-version}</version>
</dependency>
${camel-version}
must be replaced by the actual version of Apache Camel (2.1.0 or higher).
Chapter 35. Guava EventBus Copier lienLien copié sur presse-papiers!
Guava EventBus Component Copier lienLien copié sur presse-papiers!
EventBus
can be transparently forwarded to the Camel routes. EventBus component allows also to route body of Camel exchanges to the Guava EventBus
.
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
guava-eventbus:busName[?options]
guava-eventbus:busName[?options]
com.google.common.eventbus.EventBus
instance located in the Camel registry.
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
eventClass
|
null
|
*Camel 2.10:* If used on the consumer side of the route, will filter events received from the EventBus to the instances of the class and superclasses of eventClass . Null value of this option is equal to setting it to the java.lang.Object i.e. the consumer will capture all messages incoming to the event bus.
|
Usage Copier lienLien copié sur presse-papiers!
guava-eventbus
component on the consumer side of the route will capture messages sent to the Guava EventBus
and forward them to the Camel route. Guava EventBus consumer processes incoming messages asynchronously.
guava-eventbus
component on the producer side of the route will forward body of the Camel exchanges to the Guava EventBus
instance.
Chapter 36. HawtDB Copier lienLien copié sur presse-papiers!
HawtDB Copier lienLien copié sur presse-papiers!
- HawtDBAggregationRepository
Using HawtDBAggregationRepository Copier lienLien copié sur presse-papiers!
HawtDBAggregationRepository
is an AggregationRepository
which on the fly persists the aggregated messages. This ensures that you will not loose messages, as the default aggregator will use an in memory only AggregationRepository
.
Option | Type | Description |
---|---|---|
repositoryName
|
String |
A mandatory repository name. Allows you to use a shared HawtDBFile for multiple repositories.
|
persistentFileName
|
String | Filename for the persistent storage. If no file exists on startup a new file is created. |
bufferSize
|
int | The size of the memory segment buffer which is mapped to the file store. By default its 8mb. The value is in bytes. |
sync
|
boolean |
Whether or not the HawtDBFile should sync on write or not. Default is true . By sync on write ensures that its always waiting for all writes to be spooled to disk and thus will not loose updates. If you disable this option, then HawtDB will auto sync when it has batched up a number of writes.
|
pageSize
|
short | The size of memory pages. By default its 512 bytes. The value is in bytes. |
hawtDBFile
|
HawtDBFile |
Use an existing configured org.apache.camel.component.hawtdb.HawtDBFile instance.
|
returnOldExchange
|
boolean |
Whether the get operation should return the old existing Exchange if any existed. By default this option is false to optimize as we do not need the old exchange when aggregating.
|
useRecovery
|
boolean |
Whether or not recovery is enabled. This option is by default true . When enabled the Apache Camel section "Aggregator" in "Implementing Enterprise Integration Patterns" automatic recover failed aggregated exchange and have them resubmitted.
|
recoveryInterval
|
long | If recovery is enabled then a background task is run every x'th time to scan for failed exchanges to recover and resubmit. By default this interval is 5000 millis. |
maximumRedeliveries
|
int |
Allows you to limit the maximum number of redelivery attempts for a recovered exchange. If enabled then the Exchange will be moved to the dead letter channel if all redelivery attempts failed. By default this option is disabled. If this option is used then the deadLetterUri option must also be provided.
|
deadLetterUri
|
String |
An endpoint uri for a Dead Letter Channel where exhausted recovered Exchanges will be moved. If this option is used then the maximumRedeliveries option must also be provided.
|
repositoryName
option must be provided. Then either the persistentFileName
or the hawtDBFile
must be provided.
What is preserved when persisting Copier lienLien copié sur presse-papiers!
HawtDBAggregationRepository
will only preserve any Serializable
compatible data types. If a data type is not such a type its dropped and a WARN
is logged. And it only persists the Message
body and the Message
headers. The Exchange
properties are not persisted.
Recovery Copier lienLien copié sur presse-papiers!
HawtDBAggregationRepository
will by default recover any failed Exchange. It does this by having a background tasks that scans for failed Exchanges in the persistent store. You can use the checkInterval
option to set how often this task runs. The recovery works as transactional which ensures that Apache Camel will try to recover and redeliver the failed Exchange. Any Exchange which was found to be recovered will be restored from the persistent store and resubmitted and send out again.
Header | Type | Description |
---|---|---|
Exchange.REDELIVERED
|
Boolean | Is set to true to indicate the Exchange is being redelivered. |
Exchange.REDELIVERY_COUNTER
|
Integer | The redelivery attempt, starting from 1. |
confirm
method is invoked on the AggregationRepository
. This means if the same Exchange fails again it will be kept retried until it success.
maximumRedeliveries
to limit the maximum number of redelivery attempts for a given recovered Exchange. You must also set the deadLetterUri
option so Apache Camel knows where to send the Exchange when the maximumRedeliveries
was hit.
Using HawtDBAggregationRepository in Java DSL Copier lienLien copié sur presse-papiers!
target/data/hawtdb.dat
file.
Using HawtDBAggregationRepository in Spring XML Copier lienLien copié sur presse-papiers!
Dependencies Copier lienLien copié sur presse-papiers!
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-hawtdb</artifactId> <version>2.3.0</version> </dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-hawtdb</artifactId>
<version>2.3.0</version>
</dependency>
Chapter 37. Hazelcast Component Copier lienLien copié sur presse-papiers!
Hazelcast Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
hazelcast:[ map | multimap | queue | seda | set | atomicvalue | instance]:cachename[?options]
hazelcast:[ map | multimap | queue | seda | set | atomicvalue | instance]:cachename[?options]
Sections Copier lienLien copié sur presse-papiers!
Usage of Map Copier lienLien copié sur presse-papiers!
map cache producer - to("hazelcast:map:foo") Copier lienLien copié sur presse-papiers!
org.apache.camel.component.hazelcast.HazelcastConstants
.
Name | Type | Description |
---|---|---|
hazelcast.operation.type
|
String
|
valid values are: put, delete, get, update, query |
hazelcast.objectId
|
String
|
the object id to store / find your object inside the cache (not needed for the query operation) |
Name | Type | Description |
---|---|---|
CamelHazelcastOperationType
|
String
|
valid values are: put, delete, get, update, query Version 2.8 |
CamelHazelcastObjectId
|
String
|
the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8 |
template.sendBodyAndHeader("direct:[put|get|update|delete|query]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
template.sendBodyAndHeader("direct:[put|get|update|delete|query]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
Sample for put: Copier lienLien copié sur presse-papiers!
from("direct:put") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PUT_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
from("direct:put")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PUT_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
Sample for get: Copier lienLien copié sur presse-papiers!
from("direct:get") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX) .to("seda:out");
from("direct:get")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX)
.to("seda:out");
Sample for update: Copier lienLien copié sur presse-papiers!
from("direct:update") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.UPDATE_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
from("direct:update")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.UPDATE_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
Sample for delete: Copier lienLien copié sur presse-papiers!
from("direct:delete") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DELETE_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
from("direct:delete")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DELETE_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
Sample for query Copier lienLien copié sur presse-papiers!
from("direct:query") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.QUERY_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX) .to("seda:out");
from("direct:query")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.QUERY_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX)
.to("seda:out");
String q1 = "bar > 1000"; template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1);
String q1 = "bar > 1000";
template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1);
map cache consumer - from("hazelcast:map:foo") Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
hazelcast.listener.time
|
Long
|
time of the event in millis |
hazelcast.listener.type
|
String
|
the map consumer sets here "cachelistener" |
hazelcast.listener.action
|
String
|
type of event - here added, updated, envicted and removed |
hazelcast.objectId
|
String
|
the oid of the object |
hazelcast.cache.name
|
String
|
the name of the cache - e.g. "foo" |
hazelcast.cache.type
|
String
|
the type of the cache - here map |
Name | Type | Description |
---|---|---|
CamelHazelcastListenerTime
|
Long
|
time of the event in millis Version 2.8 |
CamelHazelcastListenerType
|
String
|
the map consumer sets here "cachelistener" Version 2.8 |
CamelHazelcastListenerAction
|
String
|
type of event - here added, updated, envicted and removed. Version 2.8 |
CamelHazelcastObjectId
|
String
|
the oid of the object Version 2.8 |
CamelHazelcastCacheName
|
String
|
the name of the cache - e.g. "foo" Version 2.8 |
CamelHazelcastCacheType
|
String
|
the type of the cache - here map Version 2.8 |
Usage of Multi Map Copier lienLien copié sur presse-papiers!
multimap cache producer - to("hazelcast:multimap:foo") Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
hazelcast.operation.type
|
String
|
valid values are: put, get, removevalue, delete |
hazelcast.objectId
|
String
|
the object id to store / find your object inside the cache |
Name | Type | Description |
---|---|---|
CamelHazelcastOperationType
|
String
|
valid values are: put, delete, get, update, query Available as of Apache Camel 2.8 |
CamelHazelcastObjectId
|
String
|
the object id to store / find your object inside the cache (not needed for the query operation) Version 2.8 |
template.sendBodyAndHeader("direct:[put|get|update|delete|query]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
template.sendBodyAndHeader("direct:[put|get|update|delete|query]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
Sample for put: Copier lienLien copié sur presse-papiers!
from("direct:put") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PUT_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
from("direct:put")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PUT_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
Sample for get: Copier lienLien copié sur presse-papiers!
from("direct:get") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX) .to("seda:out");
from("direct:get")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX)
.to("seda:out");
Sample for update: Copier lienLien copié sur presse-papiers!
from("direct:update") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.UPDATE_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
from("direct:update")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.UPDATE_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
Sample for delete: Copier lienLien copié sur presse-papiers!
from("direct:delete") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DELETE_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
from("direct:delete")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DELETE_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX);
Sample for query Copier lienLien copié sur presse-papiers!
from("direct:query") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.QUERY_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX) .to("seda:out");
from("direct:query")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.QUERY_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.MAP_PREFIX)
.to("seda:out");
String q1 = "bar > 1000"; template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1);
String q1 = "bar > 1000";
template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1);
map cache consumer - from("hazelcast:map:foo") Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
hazelcast.listener.time
|
Long
|
time of the event in millis |
hazelcast.listener.type
|
String
|
the map consumer sets here "cachelistener" |
hazelcast.listener.action
|
String
|
type of event - here added, updated, envicted and removed |
hazelcast.objectId
|
String
|
the oid of the object |
hazelcast.cache.name
|
String
|
the name of the cache - e.g. "foo" |
hazelcast.cache.type
|
String
|
the type of the cache - here map |
Name | Type | Description |
---|---|---|
CamelHazelcastListenerTime
|
Long
|
time of the event in millis Version 2.8 |
CamelHazelcastListenerType
|
String
|
the map consumer sets here "cachelistener" Version 2.8 |
CamelHazelcastListenerAction
|
String
|
type of event - here added, updated, envicted and removed. Version 2.8 |
CamelHazelcastObjectId
|
String
|
the oid of the object Version 2.8 |
CamelHazelcastCacheName
|
String
|
the name of the cache - e.g. "foo" Version 2.8 |
CamelHazelcastCacheType
|
String
|
the type of the cache - here map Version 2.8 |
Usage of Multi Map Copier lienLien copié sur presse-papiers!
multimap cache producer - to("hazelcast:multimap:foo") Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
hazelcast.operation.type
|
String
|
valid values are: put, get, removevalue, delete |
hazelcast.objectId
|
String
|
the object id to store / find your object inside the cache |
Name | Type | Description |
---|---|---|
CamelHazelcastOperationType
|
String
|
valid values are: put, get, removevalue, delete Version 2.8 |
CamelHazelcastObjectId
|
String
|
the object id to store / find your object inside the cache Version 2.8 |
Sample for put: Copier lienLien copié sur presse-papiers!
from("direct:put") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PUT_OPERATION)) .to(String.format("hazelcast:%sbar", HazelcastConstants.MULTIMAP_PREFIX));
from("direct:put")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PUT_OPERATION))
.to(String.format("hazelcast:%sbar", HazelcastConstants.MULTIMAP_PREFIX));
Sample for removevalue: Copier lienLien copié sur presse-papiers!
from("direct:removevalue") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.REMOVEVALUE_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.MULTIMAP_PREFIX);
from("direct:removevalue")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.REMOVEVALUE_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.MULTIMAP_PREFIX);
} you have to put "my-foo" inside the message body to remove the "my-foo" value.
Sample for get: Copier lienLien copié sur presse-papiers!
from("direct:get") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.MULTIMAP_PREFIX) .to("seda:out");
from("direct:get")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.MULTIMAP_PREFIX)
.to("seda:out");
Sample for delete: Copier lienLien copié sur presse-papiers!
from("direct:delete") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DELETE_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.MULTIMAP_PREFIX);
from("direct:delete")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DELETE_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.MULTIMAP_PREFIX);
template.sendBodyAndHeader("direct:[put|get|removevalue|delete]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
template.sendBodyAndHeader("direct:[put|get|removevalue|delete]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
multimap cache consumer - from("hazelcast:multimap:foo") Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
hazelcast.listener.time
|
Long
|
time of the event in millis |
hazelcast.listener.type
|
String
|
the map consumer sets here "cachelistener" |
hazelcast.listener.action
|
String
|
type of event - here added and removed (and soon envicted) |
hazelcast.objectId
|
String
|
the oid of the object |
hazelcast.cache.name
|
String
|
the name of the cache - e.g. "foo" |
hazelcast.cache.type
|
String
|
the type of the cache - here multimap |
Name | Type | Description |
---|---|---|
CamelHazelcastListenerTime
|
Long
|
time of the event in millis Version 2.8 |
CamelHazelcastListenerType
|
String
|
the map consumer sets here "cachelistener" Version 2.8 |
CamelHazelcastListenerAction
|
String
|
type of event - here added and removed (and soon envicted) Version 2.8 |
CamelHazelcastObjectId
|
String
|
the oid of the object Version 2.8 |
CamelHazelcastCacheName
|
String
|
the name of the cache - e.g. "foo" Version 2.8 |
CamelHazelcastCacheType
|
String
|
the type of the cache - here multimap Version 2.8 |
Usage of Queue Copier lienLien copié sur presse-papiers!
Queue producer – to("hazelcast:queue:foo") Copier lienLien copié sur presse-papiers!
Sample for add: Copier lienLien copié sur presse-papiers!
from("direct:add") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.ADD_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
from("direct:add")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.ADD_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
Sample for put: Copier lienLien copié sur presse-papiers!
from("direct:put") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PUT_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
from("direct:put")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PUT_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
Sample for poll: Copier lienLien copié sur presse-papiers!
from("direct:poll") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.POLL_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
from("direct:poll")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.POLL_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
Sample for peek: Copier lienLien copié sur presse-papiers!
from("direct:peek") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PEEK_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
from("direct:peek")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.PEEK_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
Sample for offer: Copier lienLien copié sur presse-papiers!
from("direct:offer") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.OFFER_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
from("direct:offer")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.OFFER_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
Sample for removevalue: Copier lienLien copié sur presse-papiers!
from("direct:removevalue") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.REMOVEVALUE_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
from("direct:removevalue")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.REMOVEVALUE_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.QUEUE_PREFIX);
Queue consumer – from("hazelcast:queue:foo") Copier lienLien copié sur presse-papiers!
Usage of List Copier lienLien copié sur presse-papiers!
List producer – to("hazelcast:list:foo") Copier lienLien copié sur presse-papiers!
Sample for add: Copier lienLien copié sur presse-papiers!
from("direct:add") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.ADD_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.LIST_PREFIX);
from("direct:add")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.ADD_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.LIST_PREFIX);
Sample for get: Copier lienLien copié sur presse-papiers!
from("direct:get") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.LIST_PREFIX) .to("seda:out");
from("direct:get")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.LIST_PREFIX)
.to("seda:out");
Sample for setvalue: Copier lienLien copié sur presse-papiers!
from("direct:set") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.SETVALUE_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.LIST_PREFIX);
from("direct:set")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.SETVALUE_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.LIST_PREFIX);
Sample for removevalue: Copier lienLien copié sur presse-papiers!
from("direct:removevalue") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.REMOVEVALUE_OPERATION)) .toF("hazelcast:%sbar", HazelcastConstants.LIST_PREFIX);
from("direct:removevalue")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.REMOVEVALUE_OPERATION))
.toF("hazelcast:%sbar", HazelcastConstants.LIST_PREFIX);
List consumer – from("hazelcast:list:foo") Copier lienLien copié sur presse-papiers!
Usage of SEDA Copier lienLien copié sur presse-papiers!
SEDA producer – to("hazelcast:seda:foo") Copier lienLien copié sur presse-papiers!
Name | default value | Description |
---|---|---|
transferExchange
|
false
|
Apache Camel 2.8.0: if set to true the whole Exchange will be transfered. If header or body contains not serializable objects, they will be skipped. |
from("direct:foo") .to("hazelcast:seda:foo");
from("direct:foo")
.to("hazelcast:seda:foo");
<route> <from uri="direct:start" /> <to uri="hazelcast:seda:foo" /> </route>
<route>
<from uri="direct:start" />
<to uri="hazelcast:seda:foo" />
</route>
SEDA consumer – from("hazelcast:seda:foo") Copier lienLien copié sur presse-papiers!
from("hazelcast:seda:foo") .to("mock:result");
from("hazelcast:seda:foo")
.to("mock:result");
<route> <from uri="hazelcast:seda:foo" /> <to uri="mock:result" /> </route>
<route>
<from uri="hazelcast:seda:foo" />
<to uri="mock:result" />
</route>
Usage of Atomic Number Copier lienLien copié sur presse-papiers!
atomic number producer - to("hazelcast:atomicnumber:foo") Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
hazelcast.operation.type
|
String
|
valid values are: setvalue, get, increase, decrease, destroy |
Name | Type | Description |
---|---|---|
CamelHazelcastOperationType
|
String
|
valid values are: setvalue, get, increase, decrease, destroy Available as of Apache Camel version 2.8 |
Sample for set: Copier lienLien copié sur presse-papiers!
from("direct:set") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.SETVALUE_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
from("direct:set")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.SETVALUE_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
template.sendBody("direct:set", 10);
Sample for get: Copier lienLien copié sur presse-papiers!
from("direct:get") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
from("direct:get")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.GET_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
long body = template.requestBody("direct:get", null, Long.class);
.
Sample for increment: Copier lienLien copié sur presse-papiers!
from("direct:increment") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.INCREMENT_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
from("direct:increment")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.INCREMENT_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
Sample for decrement: Copier lienLien copié sur presse-papiers!
from("direct:decrement") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DECREMENT_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
from("direct:decrement")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DECREMENT_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
Sample for destroy Copier lienLien copié sur presse-papiers!
from("direct:destroy") .setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DESTROY_OPERATION)) .toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
from("direct:destroy")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastConstants.DESTROY_OPERATION))
.toF("hazelcast:%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX);
cluster support Copier lienLien copié sur presse-papiers!
instance consumer - from("hazelcast:instance:foo") Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
hazelcast.listener.time
|
Long
|
time of the event in millis |
hazelcast.listener.type
|
String
|
the map consumer sets here "instancelistener" |
hazelcast.listener.action
|
String
|
type of event - here added or removed |
hazelcast.instance.host
|
String
|
host name of the instance |
hazelcast.instance.port
|
Integer
|
port number of the instance |
Name | Type | Description |
---|---|---|
CamelHazelcastListenerTime
|
Long
|
time of the event in millis Version 2.8 |
CamelHazelcastListenerType
|
String
|
the map consumer sets here "instancelistener" Version 2.8 |
CamelHazelcastListenerActionn
|
String
|
type of event - here added or removed. Version 2.8 |
CamelHazelcastInstanceHost
|
String
|
host name of the instance Version 2.8 |
CamelHazelcastInstancePort
|
Integer
|
port number of the instance Version 2.8 |
Chapter 38. hbase Copier lienLien copié sur presse-papiers!
HBase Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
Apache HBase Overview Copier lienLien copié sur presse-papiers!
Camel and HBase Copier lienLien copié sur presse-papiers!
- HBase groups columns into families, so just mapping a property to a column using a name convention is just not enough.
- HBase doesn't have the notion of type, which means that it stores everything as byte[] and doesn't know if the byte[] represents a String, a Number, a serialized Java object or just binary data.
Configuring the component Copier lienLien copié sur presse-papiers!
<bean id="hbase" class="org.apache.camel.component.hbase.HBaseComponent"> <property name="configuration" ref="config"/> </bean>
<bean id="hbase" class="org.apache.camel.component.hbase.HBaseComponent">
<property name="configuration" ref="config"/>
</bean>
HBase Producer Copier lienLien copié sur presse-papiers!
hbase://table[?options]
hbase://table[?options]
- Put
- Get
- Delete
- Scan
Supported URI options on producer Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
operation
|
CamelHBasePut
|
The HBase operation to perform. Supported values: CamelHBasePut , CamelHBaseGet , CamelHBaseDelete , and CamelHBaseScan .
|
maxResults
|
100
|
The maximum number of rows to scan.Supported operations: CamelHBaseScan .
|
mappingStrategyName
|
header
|
The strategy to use for mapping Camel messages to HBase columns. Supported values: header , or body .
|
mappingStrategyClassName
|
null
|
The class name of a custom mapping strategy implementation. |
filters
|
null
|
A list of filters. Supported operations: CamelHBaseScan .
|
Name | Default Value | Description |
---|---|---|
rowId
|
The id of the row. This has limited use as the row usually changes per Exchange. | |
rowType
|
String |
The type to covert row id to. Supported operations: CamelHBaseScan .
|
family
|
The column family. Supports a number suffix for referring to more than one columns | |
qualifier
|
The column qualifier. Supports a number suffix for referring to more than one columns | |
value
|
The value. Supports a number suffix for referring to more than one columns | |
valueType
|
String |
The value type. Supports a number suffix for referring to more than one columns. Supported operations: CamelHBaseGet , and CamelHBaseScan .
|
Put Operations. Copier lienLien copié sur presse-papiers!
Get Operations. Copier lienLien copié sur presse-papiers!
Delete Operations. Copier lienLien copié sur presse-papiers!
Scan Operations. Copier lienLien copié sur presse-papiers!
HBase Consumer Copier lienLien copié sur presse-papiers!
hbase://table[?options]
hbase://table[?options]
hbase:mutable?family=name&qualifer=first&valueType=java.lang.String&family=address&qualifer=number&valueType2=java.lang.Integer&rowType=java.lang.Long
hbase:mutable?family=name&qualifer=first&valueType=java.lang.String&family=address&qualifer=number&valueType2=java.lang.Integer&rowType=java.lang.Long
Supported URI options on consumer Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
initialDelay
|
1000
|
Milliseconds before the first polling starts. |
delay
|
500
|
Milliseconds before the next poll. |
useFixedDelay
|
true
|
Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. |
timeUnit |
TimeUnit.MILLISECONDS
|
time unit for initialDelay and delay options.
|
runLoggingLevel
|
TRACE
|
*Camel 2.8:* The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. |
operation
|
CamelHBasePut
|
The HBase operation to perform. Supported values: CamelHBasePut , CamelHBaseGet , CamelHBaseDelete , and CamelHBaseScan .
|
maxResults
|
100
|
The maximum number of rows to scan. Supported operations:CamelHBaseScan .
|
mappingStrategyName
|
header
|
The strategy to use for mapping Camel messages to HBase columns. Supported values: header , or body .
|
mappingStrategyClassName
|
null
|
The class name of a custom mapping strategy implementation. |
filters
|
null
|
A list of filters. Supported operations: CamelHBaseScan
|
Name | Default Value | Description |
---|---|---|
rowId
|
The id of the row. This has limited use as the row usually changes per Exchange. | |
rowType
|
String | The type to covert row id to. Supported operations: CamelHBaseScan |
family
|
The column family. *upports a number suffix for referring to more than one columns | |
qualifier
|
The column qualifier. *Supports a number suffix for referring to more than one columns | |
value
|
The value. Supports a number suffix for referring to more than one columns | |
rowModel
|
String | An instance of org.apache.camel.component.hbase.model.HBaseRow which describes how each row should be modeled |
HBase Idempotent repository Copier lienLien copié sur presse-papiers!
HBase Mapping Copier lienLien copié sur presse-papiers!
HBase Header mapping Examples Copier lienLien copié sur presse-papiers!
Header | Value |
---|---|
CamelHBaseRowId | myrow |
CamelHBaseFamily | myfamily |
CamelHBaseQualifier | myqualifier |
CamelHBaseValue | myvalue |
Header | Value |
---|---|
CamelHBaseRowId | myrow |
CamelHBaseFamily | myfamily |
CamelHBaseQualifier | myqualifier |
CamelHBaseValue | myvalue |
CamelHBaseRowId2 | myrow2 |
CamelHBaseFamily2 | myfamily |
CamelHBaseQualifier2 | myqualifier |
CamelHBaseValue2 | myvalue2 |
Header | Value |
---|---|
CamelHBaseFamily | myfamily |
CamelHBaseQualifier | myqualifier |
CamelHBaseValueType | Long |
Body mapping Examples Copier lienLien copié sur presse-papiers!
hbase:mytable?mappingStrategy=body
hbase:mytable?mappingStrategy=body
See also Copier lienLien copié sur presse-papiers!
Chapter 39. HDFS Copier lienLien copié sur presse-papiers!
HDFS Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
hdfs://hostname[:port][/path][?options]
hdfs://hostname[:port][/path][?options]
?option=value&option=value&...
The path is treated in the following way:
- as a consumer, if it's a file, it just reads the file, otherwise if it represents a directory it scans all the file under the path satisfying the configured pattern. All the files under that directory must be of the same type.
- as a producer, if at least one split strategy is defined, the path is considered a directory and under that directory the producer creates a different file per split named seg0, seg1, seg2, etc.
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
overwrite
|
true
|
The file can be overwritten |
bufferSize
|
4096
|
The buffer size used by HDFS |
replication
|
3
|
The HDFS replication factor |
blockSize
|
67108864
|
The size of the HDFS blocks |
fileType
|
NORMAL_FILE
|
It can be SEQUENCE_FILE, MAP_FILE, ARRAY_FILE, or BLOOMMAP_FILE, see Hadoop
|
fileSystemType
|
HDFS
|
It can be LOCAL for local filesystem |
keyType
|
NULL
|
The type for the key in case of sequence or map files. See below.
|
valueType
|
TEXT
|
The type for the key in case of sequence or map files. See below.
|
splitStrategy
|
A string describing the strategy on how to split the file based on different criteria. See below.
|
|
openedSuffix
|
opened
|
When a file is opened for reading/ writing the file is renamed with this suffix to avoid to read it during the writing phase.
|
readSuffix
|
read
|
Once the file has been read is renamed with this suffix to avoid to read it again.
|
initialDelay
|
0
|
For the consumer, how much to wait (milliseconds) before to start scanning the directory.
|
delay
|
0
|
The interval (milliseconds) between the directory scans.
|
pattern
|
*
|
The pattern used for scanning the directory
|
chunkSize
|
4096
|
When reading a normal file, this is split into chunks producing a message per chunk
|
connectOnStartup
|
true
|
*Camel 2.9.3/2.10.1:* Whether to connect to the HDFS file system on starting the producer/consumer. If false then the connection is created on-demand. Notice that HDFS may take up till 15 minutes to establish a connection, as it has hardcoded 45 x 20 sec redelivery. By setting this option to false allows your application to startup, and not block for up till 15 minutes.
|
KeyType and ValueType Copier lienLien copié sur presse-papiers!
- NULL it means that the key or the value is absent
- BYTE for writing a byte, the java Byte class is mapped into a BYTE
- BYTES for writing a sequence of bytes. It maps the java ByteBuffer class
- INT for writing java integer
- FLOAT for writing java float
- LONG for writing java long
- DOUBLE for writing java double
- TEXT for writing java strings
Splitting Strategy Copier lienLien copié sur presse-papiers!
- If the split strategy option has been defined, the actual file name will become a directory name and a <file name>/seg0 will be initially created.
- Every time a splitting condition is met a new file is created with name <original file name>/segN where N is 1, 2, 3, etc.The splitStrategy option is defined as a string with the following syntax:splitStrategy=<ST>:<value>,<ST>:<value>,*
<ST>
can be:
- BYTES a new file is created, and the old is closed when the number of written bytes is more than <value>
- MESSAGES a new file is created, and the old is closed when the number of written messages is more than <value>
- IDLE a new file is created, and the old is closed when no writing happened in the last <value> milliseconds
hdfs://localhost/tmp/simple-file?splitStrategy=IDLE:1000,BYTES:5
hdfs://localhost/tmp/simple-file?splitStrategy=IDLE:1000,BYTES:5
hadoop fs ls /tmp/simplefile
you'll find the following files seg0
, seg1
, seg2
, etc.
Using this component in OSGi Copier lienLien copié sur presse-papiers!
Chapter 40. HL7 Copier lienLien copié sur presse-papiers!
HL7 Component Copier lienLien copié sur presse-papiers!
- HL7 MLLP codec for Mina
- Agnostic data format using either plain String objects or HAPI HL7 model objects.
- Type Converter from/to HAPI and String
- HL7 DataFormat using HAPI library
- Even more ease-of-use as it's integrated well with the Chapter 67, MINA (Camel 2.11: camel-mina2 ) component.
pom.xml
for this component:
HL7 MLLP protocol Copier lienLien copié sur presse-papiers!
HL7MLLPCodec
as codec.
Name | Default Value | Description |
---|---|---|
startByte
|
0x0b
|
The start byte spanning the HL7 payload. |
endByte1
|
0x1c
|
The first end byte spanning the HL7 payload. |
endByte2
|
0x0d
|
The 2nd end byte spanning the HL7 payload. |
charset
|
JVM Default | The encoding (is a charset name) to use for the codec. If not provided, Camel will use the JVM default Charset. |
convertLFtoCR
|
true (Camel 2.11:false )
|
Will convert \n to \r (0x0d , 13 decimal) as HL7 stipulates \r as segment terminators. The HAPI library requires the use of \r .
|
validate
|
true
|
Whether HAPI Parser should validate or not. |
parser
|
ca.uhn.hl7v2.parser.PipeParser
|
*Camel 2.11:* To use a custom parser. Must be of type ca.uhn.hl7v2.parser.Parser .
|
Exposing a HL7 listener Copier lienLien copié sur presse-papiers!
<endpoint id="hl7listener" uri="mina:tcp://localhost:8888?sync=true&odec=#hl7codec"/> <!-- Camel 2.11: uri="mina2:tcp... -->
<endpoint id="hl7listener" uri="mina:tcp://localhost:8888?sync=true&odec=#hl7codec"/>
<!-- Camel 2.11: uri="mina2:tcp... -->
localhost
on port 8888
. We use sync=true to indicate that this listener is synchronous and therefore will return a HL7 response to the caller. Then we setup mina to use our HL7 codec with codec=#hl7codec. Notice that hl7codec
is just a Spring bean ID, so we could have named it mygreatcodecforhl7
or whatever. The codec is also set up in the Spring XML file:
<bean id="hl7codec" class="org.apache.camel.component.hl7.HL7MLLPCodec"> <property name="charset" value="iso-8859-1"/> </bean>
<bean id="hl7codec" class="org.apache.camel.component.hl7.HL7MLLPCodec">
<property name="charset" value="iso-8859-1"/>
</bean>
iso-8859-1
).
from("hl7listener").to("patientLookupService");
from("hl7listener").to("patientLookupService");
<bean id="patientLookupService" class="com.mycompany.healthcare.service.PatientLookupService"/>
<bean id="patientLookupService" class="com.mycompany.healthcare.service.PatientLookupService"/>
HL7 Model using java.lang.String Copier lienLien copié sur presse-papiers!
String
as its data format. Camel uses its Type Converter to convert to/from strings to the HAPI HL7 model objects. However, you can use plain String
objects if you prefer, for instance if you wish to parse the data yourself.
HL7v2 Model using HAPI Copier lienLien copié sur presse-papiers!
0101701234
.
MSH|^~\\&|MYSENDER|MYRECEIVER|MYAPPLICATION||200612211200||QRY^A19|1234|P|2.4 QRD|200612211200|R|I|GetPatient|||1^RD|0101701234|DEM||
MSH|^~\\&|MYSENDER|MYRECEIVER|MYAPPLICATION||200612211200||QRY^A19|1234|P|2.4
QRD|200612211200|R|I|GetPatient|||1^RD|0101701234|DEM||
ca.uhn.hl7v2.model.Message
object. To retrieve the patient ID in the message above, you can do this in Java code:
Message msg = exchange.getIn().getBody(Message.class); QRD qrd = (QRD)msg.get("QRD"); String patientId = qrd.getWhoSubjectFilter(0).getIDNumber().getValue();
Message msg = exchange.getIn().getBody(Message.class);
QRD qrd = (QRD)msg.get("QRD");
String patientId = qrd.getWhoSubjectFilter(0).getIDNumber().getValue();
QRY_A19 msg = exchange.getIn().getBody(QRY_A19.class); String patientId = msg.getQRD().getWhoSubjectFilter(0).getIDNumber().getValue();
QRY_A19 msg = exchange.getIn().getBody(QRY_A19.class);
String patientId = msg.getQRD().getWhoSubjectFilter(0).getIDNumber().getValue();
Message msg = exchange.getIn().getBody(Message.class);
Message msg = exchange.getIn().getBody(Message.class);
String
to Message
. This is powerful when combined with the HL7 listener, then you as the end-user don't have to work with byte[]
, String
or any other simple object formats. You can just use the HAPI HL7v2 model objects.
Message Headers Copier lienLien copié sur presse-papiers!
Key | MSH field | Example |
---|---|---|
CamelHL7SendingApplication
|
MSH-3
|
MYSERVER
|
CamelHL7SendingFacility
|
MSH-4
|
MYSERVERAPP
|
CamelHL7ReceivingApplication
|
MSH-5
|
MYCLIENT
|
CamelHL7ReceivingFacility
|
MSH-6
|
MYCLIENTAPP
|
CamelHL7Timestamp
|
MSH-7
|
20071231235900
|
CamelHL7Security
|
MSH-8
|
null
|
CamelHL7MessageType
|
MSH-9-1
|
ADT
|
CamelHL7TriggerEvent
|
MSH-9-2
|
A01
|
CamelHL7MessageControl
|
MSH-10
|
1234
|
CamelHL7ProcessingId
|
MSH-11
|
P
|
CamelHL7VersionId
|
MSH-12
|
2.4
|
String
types. If a header value is missing, its value is null
.
Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
validate
|
true |
Whether the HAPI Parser should validate using the default validation rules. Camel 2.11: better use the parser option and initialize the parser with the desired HAPI ValidationContext
|
parser
|
ca.uhn.hl7v2.parser.GenericParser
|
*Camel 2.11:* To use a custom parser. Must be of type ca.uhn.hl7v2.parser.Parser . Note that GenericParser also allows to parse XML-encoded HL7v2 messages.
|
Dependencies Copier lienLien copié sur presse-papiers!
camel-hl7
only references the HAPI base library. Applications are responsible for including structure libraries themselves. For example, if a application works with HL7v2 message versions 2.4 and 2.5 then the following dependencies must be added:
Terser language (Camel 2.11) Copier lienLien copié sur presse-papiers!
HL7 Validation predicate (Camel 2.11) Copier lienLien copié sur presse-papiers!
HL7 Acknowledgement expression (Camel 2.11) Copier lienLien copié sur presse-papiers!
ack
expression lets us accomplish this very elegantly:
More Samples Copier lienLien copié sur presse-papiers!
String
types in this example:
hl7service
= for instance using Spring and letting the bean id = hl7service
.
RouteBuilder
as follows:
Sample using plain String objects Copier lienLien copié sur presse-papiers!
String
objects as the data format, that we send, process and receive. As the sample is part of a unit test, there is some code for assertions, but you should be able to understand what happens. First we send the plain string, Hello World
, to the HL7MLLPCodec
and receive the response as a plain string, Bye World
.
Chapter 41. HTTP Copier lienLien copié sur presse-papiers!
HTTP Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
http:hostname[:port][/resourceUri][?param1=value1][¶m2=value2]
http:hostname[:port][/resourceUri][?param1=value1][¶m2=value2]
Examples Copier lienLien copié sur presse-papiers!
Java DSL | Spring DSL |
---|---|
from("direct:start") .to("http://myhost/mypath");
|
<from uri="direct:start"/> <to uri="http://oldhost"/>
|
Java DSL |
---|
from("direct:start") .setHeader(Exchange.HTTP_URI, simple("http://myserver/orders/${header.orderId}")) .to("http://dummyhost");
|
Java DSL |
---|
|
Java DSL | Spring DSL |
---|---|
from("direct:start") .setHeader(Exchange.HTTP_METHOD, constant("POST")) .to("http://www.google.com");
|
|
HttpEndpoint Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
throwExceptionOnFailure
|
true
|
Option to disable throwing the HttpOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardles of the HTTP status code.
|
bridgeEndpoint
|
false
|
If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all the fault response back. Camel 2.3: If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip".
|
disableStreamCache
|
false
|
DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support read it twice, otherwise DefaultHttpBinding will set the request input stream direct into the message body. |
httpBindingRef
|
null
|
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. From Camel 2.3 onwards prefer to use the httpBinding option.
|
httpBinding
|
null
|
Reference to a org.apache.camel.component.http.HttpBinding in the Registry.
|
httpClientConfigurerRef
|
null
|
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. From Camel 2.3 onwards prefer to use the httpClientConfigurer option.
|
httpClientConfigurer
|
null
|
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
|
httpClient.XXX
|
null
|
Setting options on the HttpClientParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds.
|
clientConnectionManager
|
null
|
To use a custom org.apache.http.conn.ClientConnectionManager .
|
transferException
|
false
|
*Camel 2.6:* If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException . The caused exception is required to be serialized.
|
headerFilterStrategy
|
null
|
*Camel 2.11:* Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry. It will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
|
Authentication and Proxy Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
authMethod
|
null
|
Authentication method, either as Basic , Digest or NTLM .
|
authMethodPriority
|
null
|
Priority of authentication methods. Is a list separated with comma. For example: Basic,Digest to exclude NTLM .
|
authUsername
|
null
|
Username for authentication |
authPassword
|
null
|
Password for authentication |
authDomain
|
null
|
Domain for NTML authentication |
authHost
|
null
|
Optional host for NTML authentication |
proxyHost
|
null
|
The proxy host name |
proxyPort
|
null
|
The proxy port number |
proxyAuthMethod
|
null
|
Authentication method for proxy, either as Basic , Digest or NTLM .
|
proxyAuthUsername
|
null
|
Username for proxy authentication |
proxyAuthPassword
|
null
|
Password for proxy authentication |
proxyAuthDomain
|
null
|
Domain for proxy NTML authentication |
proxyAuthHost
|
null
|
Optional host for proxy NTML authentication |
authMethod
or authProxyMethod
options. You can configure the proxy and authentication details on either the HttpComponent
or the HttpEndoint
. Values provided on the HttpEndpoint
will take precedence over HttpComponent
. Its most likely best to configure this on the HttpComponent
which allows you to do this once.
authMethodPriority
then it will fallback and use the select(ed) authMethod
as priority as well. So if you use authMethod.Basic
then the auhtMethodPriority
will be Basic
only.
HttpComponent Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
httpBinding
|
null
|
To use a custom org.apache.camel.component.http.HttpBinding .
|
httpClientConfigurer
|
null
|
To use a custom org.apache.camel.component.http.HttpClientConfigurer .
|
httpConnectionManager
|
null
|
To use a custom org.apache.commons.httpclient.HttpConnectionManager .
|
httpConfiguration
|
null
|
To use a custom org.apache.camel.component.http.HttpConfiguration
|
Message Headers Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
Exchange.HTTP_URI
|
String
|
URI to call. Will override existing URI set directly on the endpoint. |
Exchange.HTTP_METHOD
|
String
|
HTTP Method / Verb to use (GET/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) |
Exchange.HTTP_PATH
|
String
|
Request URI's path, the header will be used to build the request URI with the HTTP_URI. Camel 2.3.0: If the path is start with "/", http producer will try to find the relative path based on the Exchange.HTTP_BASE_URI header or the exchange.getFromEndpoint().getEndpointUri(); |
Exchange.HTTP_QUERY
|
String
|
URI parameters. Will override existing URI parameters set directly on the endpoint. |
Exchange.HTTP_RESPONSE_CODE
|
int
|
The HTTP response code from the external server. Is 200 for OK. |
Exchange.HTTP_CHARACTER_ENCODING
|
String
|
Character encoding. |
Exchange.CONTENT_TYPE
|
String
|
The HTTP content type. Is set on both the IN and OUT message to provide a content type, such as text/html .
|
Exchange.CONTENT_ENCODING
|
String
|
The HTTP content encoding. Is set on both the IN and OUT message to provide a content encoding, such as gzip .
|
Exchange.HTTP_SERVLET_REQUEST
|
HttpServletRequest
|
The HttpServletRequest object.
|
Exchange.HTTP_SERVLET_RESPONSE
|
HttpServletResponse
|
The HttpServletResponse object.
|
Exchange.HTTP_PROTOCOL_VERSION
|
String
|
*Camel 2.5:* You can set the http protocol version with this header, eg. "HTTP/1.0". If you didn't specify the header, HttpProducer will use the default value "HTTP/1.1" |
Message Body Copier lienLien copié sur presse-papiers!
Response code Copier lienLien copié sur presse-papiers!
- Response code is in the range 100..299, Camel regards it as a success response.
- Response code is in the range 300..399, Camel regards it as a redirection response and will throw a
HttpOperationFailedException
with the information. - Response code is 400+, Camel regards it as an external server failure and will throw a
HttpOperationFailedException
with the information.throwExceptionOnFailureThe option,throwExceptionOnFailure
, can be set tofalse
to prevent theHttpOperationFailedException
from being thrown for failed response codes. This allows you to get any response from the remote server. There is a sample below demonstrating this.
HttpOperationFailedException Copier lienLien copié sur presse-papiers!
- The HTTP status code
- The HTTP status line (text of the status code)
- Redirect location, if server returned a redirect
- Response body as a
java.lang.String
, if server provided a body as response
Calling using GET or POST Copier lienLien copié sur presse-papiers!
GET
or POST
HTTP method should be used: 1. Use method provided in header. 2. GET
if query string is provided in header. 3. GET
if endpoint is configured with a query string. 4. POST
if there is data to send (body is not null). 5. GET
otherwise.
How to get access to HttpServletRequest and HttpServletResponse Copier lienLien copié sur presse-papiers!
HttpServletRequest request = exchange.getIn().getBody(HttpServletRequest.class); HttpServletRequest response = exchange.getIn().getBody(HttpServletResponse.class);
HttpServletRequest request = exchange.getIn().getBody(HttpServletRequest.class);
HttpServletRequest response = exchange.getIn().getBody(HttpServletResponse.class);
Using client timeout - SO_TIMEOUT Copier lienLien copié sur presse-papiers!
Configuring a Proxy Copier lienLien copié sur presse-papiers!
Java DSL |
---|
from("direct:start") .to("http://oldhost?proxyHost=www.myproxy.com&proxyPort=80");
|
proxyUsername
and proxyPassword
options.
Using proxy settings outside of URI Copier lienLien copié sur presse-papiers!
Java DSL | Spring DSL |
---|---|
context.getProperties().put("http.proxyHost", "172.168.18.9"); context.getProperties().put("http.proxyPort" "8080");
|
|
Configuring charset Copier lienLien copié sur presse-papiers!
POST
to send data you can configure the charset
setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
Sample with scheduled poll Copier lienLien copié sur presse-papiers!
message.html
:
from("timer://foo?fixedRate=true&delay=0&period=10000") .to("http://www.google.com") .setHeader(FileComponent.HEADER_FILE_NAME, "message.html").to("file:target/google");
from("timer://foo?fixedRate=true&delay=0&period=10000")
.to("http://www.google.com")
.setHeader(FileComponent.HEADER_FILE_NAME, "message.html").to("file:target/google");
Getting the Response Code Copier lienLien copié sur presse-papiers!
HttpProducer.HTTP_RESPONSE_CODE
.
Using throwExceptionOnFailure=false to get any response back Copier lienLien copié sur presse-papiers!
throwExceptionOnFailure
option to false
so we get any response in the AggregationStrategy
. As the code is based on a unit test that simulates a HTTP status code 404, there is some assertion code etc.
Disabling Cookies Copier lienLien copié sur presse-papiers!
httpClient.cookiePolicy=ignoreCookies
Advanced Usage Copier lienLien copié sur presse-papiers!
HttpComponent
where you can set various classes to give you custom behavior.
Setting MaxConnectionsPerHost Copier lienLien copié sur presse-papiers!
org.apache.commons.httpclient.HttpConnectionManager
where you can configure various global configuration for the given component. By global, we mean that any endpoint the component creates has the same shared HttpConnectionManager
. So, if we want to set a different value for the max connection per host, we need to define it on the HTTP component and not on the endpoint URI that we usually use. So here comes:
http
component in Spring XML. Yes, we use the same scheme name, http
, because otherwise Camel will auto-discover and create the component with default settings. What we need is to overrule this so we can set our options. In the sample below we set the max connection to 5 instead of the default of 2.
Using preemptive authentication Copier lienLien copié sur presse-papiers!
httpClient.authenticationPreemptive=true
Accepting self signed certificates from remote server Copier lienLien copié sur presse-papiers!
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
org.apache.camel.component.http.SSLContextParametersSecureProtocolSocketFactory
, of the HTTP client's protocol socket factory in order to support the use of the Camel JSSE Configuration utility. The following example demonstrates how to configure the protocol registry and use the registered protocol information in a route.
Configuring Apache HTTP Client Directly Copier lienLien copié sur presse-papiers!
org.apache.camel.component.http.HttpClientConfigurer
to do some configuration on the http client if you need full control of it.
HttpClientConfigurer
, for example:
HttpClientConfigurer
, and registers https protocol providing a keystore or truststore per example above. Then, from your camel route builder class you can hook it up like so:
HttpComponent httpComponent = getContext().getComponent("http", HttpComponent.class); httpComponent.setHttpClientConfigurer(new MyHttpClientConfigurer());
HttpComponent httpComponent = getContext().getComponent("http", HttpComponent.class);
httpComponent.setHttpClientConfigurer(new MyHttpClientConfigurer());
HttpClientConfigurer
using the URI. For example:
Chapter 42. HTTP4 Copier lienLien copié sur presse-papiers!
HTTP4 Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
http4:hostname[:port][/resourceUri][?options]
http4:hostname[:port][/resourceUri][?options]
?option=value&option=value&...
HttpComponent Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
maxTotalConnections
|
200
|
The maximum number of connections. |
connectionsPerRoute
|
20
|
The maximum number of connections per route. |
httpClientConfigurer
|
null
|
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
|
clientConnectionManager
|
null
|
To use a custom org.apache.http.conn.ClientConnectionManager .
|
httpBinding
|
null
|
To use a custom org.apache.camel.component.http.HttpBinding .
|
httpContext
|
null
|
*Camel 2.9.2:* To use a custom org.apache.http.protocol.HttpContext when executing requests.
|
sslContextParameters
|
null
|
*Camel 2.8:* To use a custom org.apache.camel.util.jsse.SSLContextParameters . See Using the JSSE Configuration Utility.
|
x509HostnameVerifier
|
BrowserCompatHostnameVerifier
|
*Camel 2.7:* You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier .
|
HttpEndpoint Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
throwExceptionOnFailure
|
true
|
Option to disable throwing the HttpOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code.
|
bridgeEndpoint
|
false
|
If true, HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExcpetionOnFailure to be false to let the HttpProducer send all fault responses back. Also if set to true HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". |
disableStreamCache
|
false
|
DefaultHttpBinding will copy the request input stream into a stream cache and put it into the message body if this option is false to support multiple reads, otherwise DefaultHttpBinding will set the request input stream directly in the message body. |
headerFilterStrategy
|
null
|
*Camel 2.11:* Reference to a instance of org.apache.camel.spi.HeaderFilterStrategy in the Registry. t will be used to apply the custom headerFilterStrategy on the new create HttpEndpoint.
|
httpBindingRef
|
null
|
Reference to a org.apache.camel.component.http.HttpBinding in the Registry. Recommended to use the httpBinding option instead.
|
httpBinding
|
null
|
To use a custom org.apache.camel.component.http.HttpBinding .
|
httpClientConfigurerRef
|
null
|
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry. Recommended to use the httpClientConfigurer option instead.
|
httpContext
|
null
|
*Camel 2.9.2:* To use a custom org.apache.http.protocol.HttpContext when executing requests.
|
httpContextRef
|
null
|
*Camel 2.9.2:* Reference to a custom org.apache.http.protocol.HttpContext in the Registry. Recommended to use the httpContext option instead.
|
httpClientConfigurer
|
null
|
Reference to a org.apache.camel.component.http.HttpClientConfigurer in the Registry.
|
httpClient.XXX
|
null
|
Setting options on the BasicHttpParams. For instance httpClient.soTimeout=5000 will set the SO_TIMEOUT to 5 seconds. Look on the setter methods of the following parameter beans for a complete reference: AuthParamBean, ClientParamBean, ConnConnectionParamBean, ConnRouteParamBean, CookieSpecParamBean, HttpConnectionParamBean and HttpProtocolParamBean
|
clientConnectionManager
|
null
|
To use a custom org.apache.http.conn.ClientConnectionManager .
|
transferException
|
false
|
If enabled and an Exchange failed processing on the consumer side, and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is, instead of the HttpOperationFailedException . The caused exception is required to be serialized.
|
sslContextParametersRef
|
null
|
*Camel 2.8:* Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
|
x509HostnameVerifier
|
BrowserCompatHostnameVerifier
|
*Camel 2.7:* You can refer to a different org.apache.http.conn.ssl.X509HostnameVerifier instance in the Registry such as org.apache.http.conn.ssl.StrictHostnameVerifier or org.apache.http.conn.ssl.AllowAllHostnameVerifier .
|
Setting Basic Authentication and Proxy Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
username
|
null
|
Username for authentication. |
password
|
null
|
Password for authentication. |
domain
|
null
|
The domain name for authentication. |
host
|
null
|
The host name authentication. |
proxyHost
|
null
|
The proxy host name |
proxyPort
|
null
|
The proxy port number |
proxyUsername
|
null
|
Username for proxy authentication |
proxyPassword
|
null
|
Password for proxy authentication |
proxyDomain
|
null
|
The proxy domain name |
proxyNtHost
|
null
|
The proxy Nt host name |
Name | Default Value | Description |
authUsername
|
null
|
Username for authentication |
authPassword
|
null
|
Password for authentication |
authDomain
|
null
|
The domain name for authentication |
authHost
|
null
|
The host name authentication |
proxyAuthHost
|
null
|
The proxy host name |
proxyAuthPort
|
null
|
The proxy port number |
proxyAuthScheme
|
null
|
The proxy scheme, will fallback and use the scheme from the endpoint if not configured. |
proxyAuthUsername
|
null
|
Username for proxy authentication |
proxyAuthPassword
|
null
|
Password for proxy authentication |
proxyAuthDomain
|
null
|
The proxy domain name |
proxyAuthNtHost
|
null
|
The proxy Nt host name |
Message Headers Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
Exchange.HTTP_URI
|
String
|
URI to call. Will override existing URI set directly on the endpoint. |
Exchange.HTTP_PATH
|
String
|
Request URI's path, the header will be used to build the request URI with the HTTP_URI. |
Exchange.HTTP_QUERY
|
String
|
URI parameters. Will override existing URI parameters set directly on the endpoint. |
Exchange.HTTP_RESPONSE_CODE
|
int
|
The HTTP response code from the external server. Is 200 for OK. |
Exchange.HTTP_CHARACTER_ENCODING
|
String
|
Character encoding. |
Exchange.CONTENT_TYPE
|
String
|
The HTTP content type. Is set on both the IN and OUT message to provide a content type, such as text/html .
|
Exchange.CONTENT_ENCODING
|
String
|
The HTTP content encoding. Is set on both the IN and OUT message to provide a content encoding, such as gzip .
|
Message Body Copier lienLien copié sur presse-papiers!
Response code Copier lienLien copié sur presse-papiers!
- Response code is in the range 100..299, Camel regards it as a success response.
- Response code is in the range 300..399, Camel regards it as a redirection response and will throw a
HttpOperationFailedException
with the information. - Response code is 400+, Camel regards it as an external server failure and will throw a
HttpOperationFailedException
with the information.throwExceptionOnFailureThe option,throwExceptionOnFailure
, can be set tofalse
to prevent theHttpOperationFailedException
from being thrown for failed response codes. This allows you to get any response from the remote server. There is a sample below demonstrating this.
HttpOperationFailedException Copier lienLien copié sur presse-papiers!
- The HTTP status code
- The HTTP status line (text of the status code)
- Redirect location, if server returned a redirect
- Response body as a
java.lang.String
, if server provided a body as response
Calling using GET or POST Copier lienLien copié sur presse-papiers!
GET
or POST
HTTP method should be used: 1. Use method provided in header. 2. GET
if query string is provided in header. 3. GET
if endpoint is configured with a query string. 4. POST
if there is data to send (body is not null). 5. GET
otherwise.
How to get access to HttpServletRequest and HttpServletResponse Copier lienLien copié sur presse-papiers!
HttpServletRequest request = exchange.getIn().getBody(HttpServletRequest.class); HttpServletRequest response = exchange.getIn().getBody(HttpServletResponse.class);
HttpServletRequest request = exchange.getIn().getBody(HttpServletRequest.class);
HttpServletRequest response = exchange.getIn().getBody(HttpServletResponse.class);
Configuring URI to call Copier lienLien copié sur presse-papiers!
oldhost
, using HTTP.
from("direct:start") .to("http4://oldhost");
from("direct:start")
.to("http4://oldhost");
HttpConstants.HTTP_URI
, on the message.
from("direct:start") .setHeader(HttpConstants.HTTP_URI, constant("http://newhost")) .to("http4://oldhost");
from("direct:start")
.setHeader(HttpConstants.HTTP_URI, constant("http://newhost"))
.to("http4://oldhost");
org.apache.camel.component.http4.Constants
.
Configuring URI Parameters Copier lienLien copié sur presse-papiers!
Exchange.HTTP_QUERY
on the message.
from("direct:start") .to("http4://oldhost?order=123&detail=short");
from("direct:start")
.to("http4://oldhost?order=123&detail=short");
from("direct:start") .setHeader(Exchange.HTTP_QUERY, constant("order=123&detail=short")) .to("http4://oldhost");
from("direct:start")
.setHeader(Exchange.HTTP_QUERY, constant("order=123&detail=short"))
.to("http4://oldhost");
How to set the http method (GET/POST/PUT/DELETE/HEAD/OPTIONS/TRACE) to the HTTP producer Copier lienLien copié sur presse-papiers!
from("direct:start") .setHeader(Exchange.HTTP_METHOD, constant(org.apache.camel.component.http4.HttpMethods.POST)) .to("http4://www.google.com") .to("mock:results");
from("direct:start")
.setHeader(Exchange.HTTP_METHOD, constant(org.apache.camel.component.http4.HttpMethods.POST))
.to("http4://www.google.com")
.to("mock:results");
.setHeader("CamelHttpMethod", constant("POST"))
.setHeader("CamelHttpMethod", constant("POST"))
Using client timeout - SO_TIMEOUT Copier lienLien copié sur presse-papiers!
Configuring a Proxy Copier lienLien copié sur presse-papiers!
from("direct:start") .to("http4://oldhost?proxyAuthHost=www.myproxy.com&proxyAuthPort=80");
from("direct:start")
.to("http4://oldhost?proxyAuthHost=www.myproxy.com&proxyAuthPort=80");
proxyAuthUsername
and proxyAuthPassword
options.
Using proxy settings outside of URI Copier lienLien copié sur presse-papiers!
context.getProperties().put("http.proxyHost", "172.168.18.9"); context.getProperties().put("http.proxyPort" "8080");
context.getProperties().put("http.proxyHost", "172.168.18.9");
context.getProperties().put("http.proxyPort" "8080");
http.proxyScheme
property you can set to explicit configure the scheme to use.
Configuring charset Copier lienLien copié sur presse-papiers!
POST
to send data you can configure the charset
using the Exchange
property:
exchange.setProperty(Exchange.CHARSET_NAME, "ISO-8859-1");
exchange.setProperty(Exchange.CHARSET_NAME, "ISO-8859-1");
Sample with scheduled poll Copier lienLien copié sur presse-papiers!
message.html
:
from("timer://foo?fixedRate=true&delay=0&period=10000") .to("http4://www.google.com") .setHeader(FileComponent.HEADER_FILE_NAME, "message.html") .to("file:target/google");
from("timer://foo?fixedRate=true&delay=0&period=10000")
.to("http4://www.google.com")
.setHeader(FileComponent.HEADER_FILE_NAME, "message.html")
.to("file:target/google");
URI Parameters from the endpoint URI Copier lienLien copié sur presse-papiers!
&
character as separator, just as you would in the web browser. Camel does no tricks here.
// we query for Camel at the Google page template.sendBody("http4://www.google.com/search?q=Camel", null);
// we query for Camel at the Google page
template.sendBody("http4://www.google.com/search?q=Camel", null);
URI Parameters from the Message Copier lienLien copié sur presse-papiers!
Map headers = new HashMap(); headers.put(HttpProducer.QUERY, "q=Camel&lr=lang_en"); // we query for Camel and English language at Google template.sendBody("http4://www.google.com/search", null, headers);
Map headers = new HashMap();
headers.put(HttpProducer.QUERY, "q=Camel&lr=lang_en");
// we query for Camel and English language at Google
template.sendBody("http4://www.google.com/search", null, headers);
?
and you can separate parameters as usual with the &
char.
Getting the Response Code Copier lienLien copié sur presse-papiers!
HttpProducer.HTTP_RESPONSE_CODE
.
Disabling Cookies Copier lienLien copié sur presse-papiers!
httpClient.cookiePolicy=ignoreCookies
Advanced Usage Copier lienLien copié sur presse-papiers!
HttpComponent
where you can set various classes to give you custom behavior.
Using HTTPS to authenticate gotchas Copier lienLien copié sur presse-papiers!
httpClient.authenticationPreemptive=true
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
Programmatic configuration of the component Copier lienLien copié sur presse-papiers!
Spring DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
Configuring Apache HTTP Client Directly Copier lienLien copié sur presse-papiers!
org.apache.camel.component.http4.HttpsServerTestSupport
unit test base class. You can also implement a custom org.apache.camel.component.http4.HttpClientConfigurer
to do some configuration on the http client if you need full control of it.
HttpClientConfigurer
, for example:
HttpClientConfigurer
, and registers https protocol providing a keystore or truststore per example above. Then, from your camel route builder class you can hook it up like so:
HttpComponent httpComponent = getContext().getComponent("http4", HttpComponent.class); httpComponent.setHttpClientConfigurer(new MyHttpClientConfigurer());
HttpComponent httpComponent = getContext().getComponent("http4", HttpComponent.class);
httpComponent.setHttpClientConfigurer(new MyHttpClientConfigurer());
HttpClientConfigurer
using the URI. For example:
Chapter 43. iBATIS Copier lienLien copié sur presse-papiers!
iBATIS Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
ibatis:statementName[?options]
ibatis:statementName[?options]
?option=value&option=value&...
SqlMapConfig.xml
. It uses Spring resource loading so you can define it using classpath
, file
or http
as prefix to load resources with those schemes. In Camel 2.2 you can configure this on the iBatisComponent with the setSqlMapConfig(String)
method.
Options Copier lienLien copié sur presse-papiers!
Option | Type | Default | Description |
---|---|---|---|
consumer.onConsume
|
String
|
null
|
Statements to run after consuming. Can be used, for example, to update rows after they have been consumed and processed in Apache Camel. See sample later. Multiple statements can be separated with comma. |
consumer.useIterator
|
boolean
|
true
|
If true each row returned when polling will be processed individually. If false the entire List of data is set as the IN body.
|
consumer.routeEmptyResultSet
|
boolean
|
false
|
Apache Camel 2.0: Sets whether empty result set should be routed or not. By default, empty result sets are not routed. |
statementType
|
StatementType
|
null
|
Apache Camel 1.6.1/2.0: Mandatory to specify for IbatisProducer to control which iBatis SqlMapClient method to invoke. The enum values are: QueryForObject , QueryForList , Insert , Update , Delete .
|
maxMessagesPerPoll
|
int
|
0
|
Apache Camel 2.0: An integer to define a maximum messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid when starting up the server that there are thousands of files. Set a value of 0 or negative to disabled it. |
isolation
|
String
|
TRANSACTION_REPEATABLE_READ
|
*Camel 2.9:* A String the defines the transaction isolation level of the will be used. Allowed values are TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE |
isolation
|
String
|
TRANSACTION_REPEATABLE_READ
|
*Camel 2.9:* A String the defines the transaction isolation level of the will be used. Allowed values are TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE |
Message Headers Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelIBatisStatementName
|
String
|
Apache Camel 2.0: The statementName used (for example: insertAccount). |
CamelIBatisResult
|
Object
|
Apache Camel 1.6.2/2.0: The response returned from iBatis in any of the operations. For instance an INSERT could return the auto-generated key, or number of rows etc.
|
Message Body Copier lienLien copié sur presse-papiers!
SELECT
statement. That means, for example, for INSERT
statements Apache Camel will not replace the body. This allows you to continue routing and keep the original body. The response from iBatis is always stored in the header with the key CamelIBatisResult
.
Samples Copier lienLien copié sur presse-papiers!
from("activemq:queue:newAccount"). to("ibatis:insertAccount?statementType=Insert");
from("activemq:queue:newAccount").
to("ibatis:insertAccount?statementType=Insert");
statementType
, as we need to instruct Apache Camel which SqlMapClient
operation to invoke.
Using StatementType for better control of IBatis Copier lienLien copié sur presse-papiers!
SELEECT
, UPDATE
, DELETE
or INSERT
etc. This is now possible in Apache Camel 1.6.1/2.0. So for instance if we want to route to an iBatis endpoint in which the IN body contains parameters to a SELECT
statement we can do:
from("direct:start") .to("ibatis:selectAccountById?statementType=QueryForObject") .to("mock:result");
from("direct:start")
.to("ibatis:selectAccountById?statementType=QueryForObject")
.to("mock:result");
selectAccountById
and the IN body should contain the account id we want to retrieve, such as an Integer
type.
QueryForList
:
from("direct:start") .to("ibatis:selectAllAccounts?statementType=QueryForList") .to("mock:result");
from("direct:start")
.to("ibatis:selectAllAccounts?statementType=QueryForList")
.to("mock:result");
UPDATE
, where we can send an Account
object as IN body to iBatis:
from("direct:start") .to("ibatis:updateAccount?statementType=Update") .to("mock:result");
from("direct:start")
.to("ibatis:updateAccount?statementType=Update")
.to("mock:result");
Scheduled polling example Copier lienLien copié sur presse-papiers!
from("timer://pollTheDatabase?delay=30000").to("ibatis:selectAllAccounts?statementType=QueryForList").to("activemq:queue:allAccounts");
from("timer://pollTheDatabase?delay=30000").to("ibatis:selectAllAccounts?statementType=QueryForList").to("activemq:queue:allAccounts");
<!-- Select with no parameters using the result map for Account class. --> <select id="selectAllAccounts" resultMap="AccountResult"> select * from ACCOUNT </select>
<!-- Select with no parameters using the result map for Account class. -->
<select id="selectAllAccounts" resultMap="AccountResult">
select * from ACCOUNT
</select>
Using onConsume Copier lienLien copié sur presse-papiers!
UPDATE
statements. Apache Camel supports executing multiple statements whose name should be separated by comma.
from("ibatis:selectUnprocessedAccounts?consumer.onConsume=consumeAccount").to("mock:results");
from("ibatis:selectUnprocessedAccounts?consumer.onConsume=consumeAccount").to("mock:results");
<select id="selectUnprocessedAccounts" resultMap="AccountResult"> select * from ACCOUNT where PROCESSED = false </select>
<select id="selectUnprocessedAccounts" resultMap="AccountResult">
select * from ACCOUNT where PROCESSED = false
</select>
<update id="consumeAccount" parameterClass="Account"> update ACCOUNT set PROCESSED = true where ACC_ID = #id# </update>
<update id="consumeAccount" parameterClass="Account">
update ACCOUNT set PROCESSED = true where ACC_ID = #id#
</update>
Chapter 44. IRC Copier lienLien copié sur presse-papiers!
IRC Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
irc:nick@host[:port]/#room[?options]
irc:nick@host[:port]/#room[?options]
irc:nick@host[:port]?channels=#channel1,#channel2,#channel3[?options]
irc:nick@host[:port]?channels=#channel1,#channel2,#channel3[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Description | Example | Default Value |
---|---|---|---|
channels
|
New in 2.0, comma separated list of IRC channels to join. |
channels=#channel1,#channel2
|
null
|
nickname
|
The nickname used in chat. |
irc:MyNick@irc.server.org#channel or irc:irc.server.org#channel?nickname=MyUser
|
null
|
username
|
The IRC server user name. |
irc:MyUser@irc.server.org#channel or irc:irc.server.org#channel?username=MyUser
|
Same as nickname. |
password
|
The IRC server password. |
password=somepass
|
None |
realname
|
The IRC user's actual name. |
realname=MyName
|
None |
colors
|
Whether or not the server supports color codes. |
true, false
|
true
|
onReply
|
Whether or not to handle general responses to commands or informational messages. |
true, false
|
false
|
onNick
|
Handle nickname change events. |
true, false
|
true
|
onQuit
|
Handle user quit events. |
true, false
|
true
|
onJoin
|
Handle user join events. |
true, false
|
true
|
onKick
|
Handle kick events. |
true, false
|
true
|
onMode
|
Handle mode change events. |
true, false
|
true
|
onPart
|
Handle user part events. |
true, false
|
true
|
onTopic
|
Handle topic change events. |
true, false
|
true
|
onPrivmsg
|
Handle message events. |
true, false
|
true
|
trustManager
|
New in 2.0, the trust manager used to verify the SSL server's certificate. |
trustManager=#referenceToTrustManagerBean
|
The default trust manager, which accepts all certificates, will be used. |
keys
|
Camel 2.2: Comma separated list of IRC channel keys. Important to be listed in same order as channels. When joining multiple channels with only some needing keys just insert an empty value for that channel. |
irc:MyNick@irc.server.org/#channel?keys=chankey
|
null
|
sslContextParameters |
*Camel 2.9:* Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that this setting overrides the trustManager option.
|
\#mySslContextParameters |
null
|
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
Programmatic configuration of the endpoint Copier lienLien copié sur presse-papiers!
Spring DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
Using the legacy basic configuration options Copier lienLien copié sur presse-papiers!
ircs:host[:port]/#room?username=user&password=pass
ircs:host[:port]/#room?username=user&password=pass
trustManager
parameter as follows:
ircs:host[:port]/#room?username=user&password=pass&trustManager=#referenceToMyTrustManagerBean
ircs:host[:port]/#room?username=user&password=pass&trustManager=#referenceToMyTrustManagerBean
Using keys Copier lienLien copié sur presse-papiers!
irc:nick@irc.server.org?channels=#chan1,#chan2,#chan3&keys=chan1Key,,chan3key
irc:nick@irc.server.org?channels=#chan1,#chan2,#chan3&keys=chan1Key,,chan3key
Chapter 45. Jasypt Copier lienLien copié sur presse-papiers!
Jasypt component Copier lienLien copié sur presse-papiers!
camel-jasypt
on the classpath those encrypted values will automatic be decrypted on-the-fly by Camel. This ensures that human eyes can't easily spot sensitive information such as usernames and passwords.
pom.xml
for this component:
Tooling Copier lienLien copié sur presse-papiers!
tiger
you run with the following parameters. In the apache camel kit, you cd into the lib folder and run the following java cmd, where <CAMEL_HOME>
is where you have downloaded and extract the Camel distribution.
cd <CAMEL_HOME>/lib java -jar camel-jasypt-2.5.0.jar -c encrypt -p secret -i tiger
$ cd <CAMEL_HOME>/lib
$ java -jar camel-jasypt-2.5.0.jar -c encrypt -p secret -i tiger
Encrypted text: qaEEacuW7BUti8LcMgyjKw==
Encrypted text: qaEEacuW7BUti8LcMgyjKw==
qaEEacuW7BUti8LcMgyjKw==
can be decrypted back to tiger
if you know the master password which was secret
. If you run the tool again then the encrypted value will return a different result. But decrypting the value will always return the correct original value.
cd <CAMEL_HOME>/lib java -jar camel-jasypt-2.5.0.jar -c decrypt -p secret -i qaEEacuW7BUti8LcMgyjKw==
$ cd <CAMEL_HOME>/lib
$ java -jar camel-jasypt-2.5.0.jar -c decrypt -p secret -i qaEEacuW7BUti8LcMgyjKw==
Decrypted text: tiger
Decrypted text: tiger
ENC(value here)
refer to a mock endpoint name by that encrypted password here is a password which is encrypted
# refer to a mock endpoint name by that encrypted password
cool.result=mock:{{cool.password}}
# here is a password which is encrypted
cool.password=ENC(bsW9uV37gQ0QHFu7KO03Ww==)
Tooling dependencies for Camel 2.5 and 2.6 Copier lienLien copié sur presse-papiers!
MANIFEST.MF
file of camel-jasypt
with optional/
as prefix. Hence why the java cmd above can pickup the needed JARs from the Apache Distribution in the optional
directory.
jasypt-1.6.jar commons-lang-2.4.jar commons-codec-1.4.jar icu4j-4.0.1.jar
jasypt-1.6.jar commons-lang-2.4.jar commons-codec-1.4.jar icu4j-4.0.1.jar
icu4j-4.0.1.jar
is only needed when running on JDK 1.5.
lib/optional
directory of the Camel distribution. You can download it from Apache Central Maven repo.
Tooling dependencies for Camel 2.7 or better Copier lienLien copié sur presse-papiers!
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Type | Description |
---|---|---|---|
password
|
null
|
String
|
Specifies the master password to use for decrypting. This option is mandatory. See below for more details. |
algorithm
|
null
|
String
|
Name of an optional algorithm to use. |
Protecting the master password Copier lienLien copié sur presse-papiers!
password
option supports prefixes which dictates this. sysenv:
means to lookup the OS system environment with the given key. sys:
means to lookup a JVM system property.
export CAMEL_ENCRYPTION_PASSWORD=secret
$ export CAMEL_ENCRYPTION_PASSWORD=secret
unset CAMEL_ENCRYPTION_PASSWORD
$ unset CAMEL_ENCRYPTION_PASSWORD
password
option is then a matter of defining as follows: password=sysenv:CAMEL_ENCRYPTION_PASSWORD
.
Example with Java DSL Copier lienLien copié sur presse-papiers!
JasyptPropertiesParser
instance and set it on the Properties component as show below:
myproperties.properties
then contain the encrypted value, such as shown below. Notice how the password value is encrypted and the value has the tokens surrounding ENC(value here)
refer to a mock endpoint name by that encrypted password here is a password which is encrypted
# refer to a mock endpoint name by that encrypted password
cool.result=mock:{{cool.password}}
# here is a password which is encrypted
cool.password=ENC(bsW9uV37gQ0QHFu7KO03Ww==)
Example with Spring XML Copier lienLien copié sur presse-papiers!
JasyptPropertiesParser
which is shown below. Then the Camel Properties component is told to use jasypt
as the properties parser, which means Jasypt have its chance to decrypt values looked up in the properties.
<camelContext>
tag which is shown below. Notice how we use the propertiesParserRef
attribute to refer to Jasypt.
See Also Copier lienLien copié sur presse-papiers!
- Encrypted passwords in ActiveMQ - ActiveMQ has a similar feature as this
camel-jasypt
component
Chapter 46. JavaSpace Copier lienLien copié sur presse-papiers!
JavaSpace Component Copier lienLien copié sur presse-papiers!
net.jini.core.entry.Entry
class. It is also possible to pass the bean ID of a template that can be used for reading/taking the entries from the space. This component can be used for sending/receiving any serializable object acting as a sort of generic transport. The JavaSpace component contains a special optimization for dealing with the BeanExchange
. It can be used to invoke a POJO remotely, using a JavaSpace as a transport. This latter feature can provide a simple implementation of the master/worker pattern, where a POJO provides the business logic for the worker. Look at the test cases for examples of various use cases for this component.
URI format Copier lienLien copié sur presse-papiers!
javaspace:jini://host[?options]
javaspace:jini://host[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
spaceName
|
null
|
Specifies the JavaSpace name. |
verb
|
take
|
Specifies the verb for getting JavaSpace entries. The values can be: take or read .
|
transactional
|
false
|
If true , sending and receiving entries is performed within a transaction.
|
transactionalTimeout
|
Long.MAX_VALUE
|
Specifies the transaction timeout. |
concurrentConsumers
|
1
|
Specifies the number of concurrent consumers getting entries from the JavaSpace. |
templateId
|
null
|
If present, this option specifies the Spring bean ID of the template to use for reading/taking entries. |
Sending and Receiving Entries Copier lienLien copié sur presse-papiers!
//Sending route from("direct:input").to("javaspace:jini://localhost?spaceName=mySpace"); //Receiving Route from("javaspace:jini://localhost?spaceName=mySpace&templateId=template&verb=take&concurrentConsumers=1")
//Sending route
from("direct:input").to("javaspace:jini://localhost?spaceName=mySpace");
//Receiving Route
from("javaspace:jini://localhost?spaceName=mySpace&templateId=template&verb=take&concurrentConsumers=1")
Entry
type.
Sending and receiving serializable objects Copier lienLien copié sur presse-papiers!
Entry
and then it automatically wraps the payload with a Camel Jini Entry
. In this way, a JavaSpace can be used as a generic transport mechanism.
Using JavaSpace as a remote invocation transport Copier lienLien copié sur presse-papiers!
from("direct:input").to("javaspace:jini://localhost?spaceName=mySpace"); //Client side from("javaspace:jini://localhost?concurrentConsumers=10&spaceName=mySpace").to("pojo:pojo"); //Server side
from("direct:input").to("javaspace:jini://localhost?spaceName=mySpace"); //Client side
from("javaspace:jini://localhost?concurrentConsumers=10&spaceName=mySpace").to("pojo:pojo"); //Server side
Chapter 47. JBI Copier lienLien copié sur presse-papiers!
47.1. JBI Component Copier lienLien copié sur presse-papiers!
Overview Copier lienLien copié sur presse-papiers!
StreamSource
types from ServiceMix in Camel.
from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
{http://foo.bar.org}MyService
and the endpoint name is MyEndpoint
(see URI-format).
to("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
to("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
URI format Copier lienLien copié sur presse-papiers!
jbi:service:serviceNamespace[sep]serviceName[?options] jbi:endpoint:serviceNamespace[sep]serviceName[sep]endpointName[?options] jbi:name:endpointName[?options]
jbi:service:serviceNamespace[sep]serviceName[?options]
jbi:endpoint:serviceNamespace[sep]serviceName[sep]endpointName[?options]
jbi:name:endpointName[?options]
/
(forward slash), ifserviceNamespace
starts withhttp://
, or:
(colon), ifserviceNamespace
starts withurn:foo:bar
.
jbi:service:
or jbi:endpoint:
URI formats sets the service QName on the JBI endpoint to the one specified. Otherwise, the default Camel JBI Service QName is used, which is:
{http://activemq.apache.org/camel/schema/jbi}endpoint
{http://activemq.apache.org/camel/schema/jbi}endpoint
?option=value&option=value&...
Examples Copier lienLien copié sur presse-papiers!
jbi:service:http://foo.bar.org/MyService jbi:endpoint:urn:foo:bar:MyService:MyEndpoint jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint jbi:name:cheese
jbi:service:http://foo.bar.org/MyService
jbi:endpoint:urn:foo:bar:MyService:MyEndpoint
jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint
jbi:name:cheese
URI options Copier lienLien copié sur presse-papiers!
Name | Default value | Description |
---|---|---|
mep
|
MEP of the Camel Exchange |
Allows users to override the MEP set on the Exchange object. Valid values for this option are in-only , in-out , robust-in-out and in-optional-out .
|
operation
|
Value of the jbi.operation header property
|
Specifies the JBI operation for the MessageExchange . If no value is supplied, the JBI binding will use the value of the jbi.operation header property.
|
serialization
|
basic
|
Default value (basic ) will check if headers are serializable by looking at the type, setting this option to strict will detect objects that can not be serialized although they implement the Serializable interface. Set to nocheck to disable this check altogether, note that this should only be used for in-memory transports like SEDAFlow, otherwise you can expect to get NotSerializableException thrown at runtime.
|
convertException
|
false
|
false : send any exceptions thrown from the Camel route back unmodified true : convert all exceptions to a JBI FaultException (can be used to avoid non-serializable exceptions or to implement generic error handling
|
Examples Copier lienLien copié sur presse-papiers!
jbi:service:http://foo.bar.org/MyService?mep=in-out (override the MEP, use InOut JBI MessageExchanges) jbi:endpoint:urn:foo:bar:MyService:MyEndpoint?mep=in (override the MEP, use InOnly JBI MessageExchanges) jbi:endpoint:urn:foo:bar:MyService:MyEndpoint?operation={http://www.mycompany.org}AddNumbers (overide the operation for the JBI Exchange to {http://www.mycompany.org}AddNumbers)
jbi:service:http://foo.bar.org/MyService?mep=in-out (override the MEP, use InOut JBI MessageExchanges)
jbi:endpoint:urn:foo:bar:MyService:MyEndpoint?mep=in (override the MEP, use InOnly JBI MessageExchanges)
jbi:endpoint:urn:foo:bar:MyService:MyEndpoint?operation={http://www.mycompany.org}AddNumbers
(overide the operation for the JBI Exchange to {http://www.mycompany.org}AddNumbers)
Using Stream bodies Copier lienLien copié sur presse-papiers!
DEBUG
logging, the body is usually logged and thus read. To deal with this, Camel has a streamCaching
option that can cache the stream, enabling you to read it multiple times.
from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint").streamCaching().to("xslt:transform.xsl", "bean:doSomething");
from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint").streamCaching().to("xslt:transform.xsl", "bean:doSomething");
streamCaching()
option. We store big input streams (by default, over 64K) in a temp
file using CachedOutputStream
. When you close the input stream, the temp file will be deleted.
Creating a JBI Service Unit Copier lienLien copié sur presse-papiers!
- Create a Spring XML file at
src/main/resources/camel-context.xml
to bootstrap your routes inside the JBI Service Unit. - Change the POM file's packaging to
jbi-service-unit
.
pom.xml
should look something like this to enable the jbi-service-unit
packaging:
47.2. JBI Service Unit Archetype Copier lienLien copié sur presse-papiers!
JBI Service Unit Archetype Copier lienLien copié sur presse-papiers!
cd myArtifactId mvn install
cd myArtifactId
mvn install
Chapter 48. jclouds Copier lienLien copié sur presse-papiers!
Jclouds Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
Configuring the component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
jclouds:blobstore:[provider id][?options] jclouds:compute:[provider id][?options]
jclouds:blobstore:[provider id][?options]
jclouds:compute:[provider id][?options]
?option=value&option=value&...
Blobstore URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
operation
|
PUT | *Producer Only*. Specifies the type of operation that will be performed to the blobstore. Allowed values are PUT, GET. |
container
|
null | The name of the blob container. |
blobName
|
null | The name of the blob. |
jclouds:blobstore:aws-s3?operation=CamelJcloudsGet&container=mycontainer&blobName=someblob
jclouds:blobstore:aws-s3?operation=CamelJcloudsGet&container=mycontainer&blobName=someblob
Message Headers for blobstore Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelJcloudsOperation
|
The operation to be performed on the blob. The valid options are
|
CamelJcloudsContainer
|
The name of the blob container. |
CamelJcloudsBlobName
|
The name of the blob. |
Blobstore Usage Samples Copier lienLien copié sur presse-papiers!
Example 1: Putting to the blob Copier lienLien copié sur presse-papiers!
<route> <from uri="direct:start"/> <to uri="jclouds:blobstore:aws-s3?operation=PUT&container=mycontainer&blobName=myblob"/> </route>
<route>
<from uri="direct:start"/>
<to uri="jclouds:blobstore:aws-s3?operation=PUT&container=mycontainer&blobName=myblob"/>
</route>
Example 2: Getting/Reading from a blob Copier lienLien copié sur presse-papiers!
<route> <from uri="direct:start"/> <to uri="jclouds:blobstore:aws-s3?operation=PUT&container=mycontainer&blobName=myblob"/> </route>
<route>
<from uri="direct:start"/>
<to uri="jclouds:blobstore:aws-s3?operation=PUT&container=mycontainer&blobName=myblob"/>
</route>
Example 3: Consuming a blob Copier lienLien copié sur presse-papiers!
from("jclouds:blobstore:aws-s3" + "?container=mycontainer") .to("direct:next");
from("jclouds:blobstore:aws-s3" +
"?container=mycontainer")
.to("direct:next");
<route> <from uri="jclouds:blobstore:aws-s3?operation=GET&container=mycontainer&blobName=myblob"/> <to uri="direct:next"/> </route>
<route>
<from uri="jclouds:blobstore:aws-s3?operation=GET&container=mycontainer&blobName=myblob"/>
<to uri="direct:next"/>
</route>
Compute Service URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
operation
|
PUT | Specifies the type of operation that will be performed to the compute service. Allowed values are CREATE_NODE, RUNS_CRIPT, DESTROY_NODE, LIST_NODES, LIST_IMAGES, LIST_HARDWARE. |
imageId
|
null | *CREATE_NODE operation only* The imageId that will be used for creating a node. Values depend on the actual cloud provider. |
locationId
|
null | *CREATE_NODE operation only* The location that will be used for creating a node. Values depend on the actual cloud provider. |
hardwareId
|
null | *CREATE_NODE operation only* The hardware that will be used for creating a node. Values depend on the actual cloud provider. |
group
|
null | *CREATE_NODE operation only* The group that will be assigned to the newly created node. Values depend on the actual cloud provider. |
nodeId
|
null | *RUN_SCRIPT & DESTROY_NODE operation only* The id of the node that will run the script or destroyed. |
user
|
null | *RUN_SCRIPT operation only* The user on the target node that will run the script. |
jclouds:compute:aws-ec2?operation=CREATE_NODE&imageId=AMI_XXXXX&locationId=eu-west-1&group=mygroup
jclouds:compute:aws-ec2?operation=CREATE_NODE&imageId=AMI_XXXXX&locationId=eu-west-1&group=mygroup
Compute Usage Samples Copier lienLien copié sur presse-papiers!
Example 1: Listing the available images. Copier lienLien copié sur presse-papiers!
from("jclouds:compute:aws-ec2" + "&operation=LIST_IMAGES") .to("direct:next");
from("jclouds:compute:aws-ec2" +
"&operation=LIST_IMAGES")
.to("direct:next");
<route> <from uri="jclouds:compute:aws-ec2?operation=LIST_IMAGES"/> <to uri="direct:next"/> </route>
<route>
<from uri="jclouds:compute:aws-ec2?operation=LIST_IMAGES"/>
<to uri="direct:next"/>
</route>
Example 2: Create a new node. Copier lienLien copié sur presse-papiers!
<route> <from uri="direct:start"/> <to uri="jclouds:compute:aws-ec2?operation=CREATE_NODE&imageId=AMI_XXXXX&locationId=XXXXX&group=myGroup"/> </route>
<route>
<from uri="direct:start"/>
<to uri="jclouds:compute:aws-ec2?operation=CREATE_NODE&imageId=AMI_XXXXX&locationId=XXXXX&group=myGroup"/>
</route>
Example 3: Run a shell script on running node. Copier lienLien copié sur presse-papiers!
<route> <from uri="direct:start"/> <to uri="jclouds:compute:aws-ec2?operation=RUN_SCRIPT&?nodeId=10&user=ubuntu"/> </route>
<route>
<from uri="direct:start"/>
<to uri="jclouds:compute:aws-ec2?operation=RUN_SCRIPT&?nodeId=10&user=ubuntu"/>
</route>
See also Copier lienLien copié sur presse-papiers!
Chapter 49. JCR Copier lienLien copié sur presse-papiers!
JCR Component Copier lienLien copié sur presse-papiers!
jcr
component allows you to add/read nodes to/from a JCR compliant content repository (for example, Apache Jackrabbit) with its producer, or register an EventListener with the consumer.
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
jcr://user:password@repository/path/to/node
jcr://user:password@repository/path/to/node
Usage Copier lienLien copié sur presse-papiers!
repository
element of the URI is used to look up the JCR Repository
object in the Camel context registry.
Producer Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
CamelJcrOperation
|
CamelJcrInsert
|
CamelJcrInsert or CamelJcrGetById operation to use |
CamelJcrNodeName
|
null
|
Used to determine the node name to use. |
- If the operation is CamelJcrInsert: A new node is created in the content repository, all the message properties of the IN message are transformed to JCR
Value
instances and added to the new node and the node's UUID is returned in the OUT message. - If the operation is CamelJcrGetById: A new node is retrieved from the repository using the message body as node identifier.
Consumer Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
eventTypes
|
0
|
A combination of one or more event types encoded as a bit mask value such as javax.jcr.observation.Event.NODE_ADDED, javax.jcr.observation.Event.NODE_REMOVED, etc. |
deep
|
false
|
When it is true, events whose associated parent node is at current path or within its subgraph are received. |
uuids
|
null
|
Only events whose associated parent node has one of the identifiers in the comma separated uuid list will be received. |
nodeTypeNames
|
null
|
Only events whose associated parent node has one of the node types (or a subtype of one of the node types) in this list will be received. |
noLocal
|
false
|
If noLocal is true , then events generated by the session through which the listener was registered are ignored. Otherwise, they are not ignored.
|
sessionLiveCheckInterval
|
60000
|
Interval in milliseconds to wait before each session live checking. |
sessionLiveCheckIntervalOnStart
|
3000
|
Interval in milliseconds to wait before the first session live checking. |
Example Copier lienLien copié sur presse-papiers!
node
under the /home/test
node in the content repository. One additional attribute is added to the node as well: my.contents.property
which will contain the body of the message being sent.
from("direct:a").setProperty(JcrConstants.JCR_NODE_NAME, constant("node")) .setProperty("my.contents.property", body()) .to("jcr://user:pass@repository/home/test");
from("direct:a").setProperty(JcrConstants.JCR_NODE_NAME, constant("node"))
.setProperty("my.contents.property", body())
.to("jcr://user:pass@repository/home/test");
<route> <from uri="jcr://user:pass@repository/import-application/inbox?eventTypes=3&deep=true" /> <to uri="direct:execute-import-application" /> </route>
<route>
<from uri="jcr://user:pass@repository/import-application/inbox?eventTypes=3&deep=true" />
<to uri="direct:execute-import-application" />
</route>
Chapter 50. JDBC Copier lienLien copié sur presse-papiers!
JDBC Component Copier lienLien copié sur presse-papiers!
from()
statement.
URI format Copier lienLien copié sur presse-papiers!
jdbc:dataSourceName[?options]
jdbc:dataSourceName[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
readSize
|
0
|
The default maximum number of rows that can be read by a polling query. |
statement.<xxx>
|
null
|
Apache Camel 2.1: Sets additional options on the java.sql.Statement that is used behind the scenes to execute the queries. For instance, statement.maxRows=10 . For detailed documentation, see the java.sql.Statement javadoc documentation.
|
useJDBC4ColumnNameAndLabelSemantics
|
true
|
Sets whether to use JDBC 4/3 column label/name semantics. You can use this option to turn it false in case you have issues with your JDBC driver to select data. This only applies when using SQL SELECT using aliases (e.g. SQL SELECT id as identifier, name as given_name from persons ).
|
resetAutoCommit
|
true
|
*Camel 2.9:* Camel will set the autoCommit on the JDBC connection to be false, commit the change after executed the statement and reset the autoCommit flag of the connection at the end, if the resetAutoCommit is true. If the JDBC connection doesn't support to reset the autoCommit flag, you can set the resetAutoCommit flag to be false, and Camel will not try to reset the autoCommit flag. |
Result Copier lienLien copié sur presse-papiers!
ArrayList<HashMap<String, Object>>
. The List
object contains the list of rows and the Map
objects contain each row with the String
key as the column name.
ResultSetMetaData
to be able to return the column name as the key in the Map
.
Message Headers Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelJdbcRowCount
|
If the query is a SELECT , the row count is returned in this OUT header.
|
CamelJdbcUpdateCount
|
If the query is an UPDATE , the update count is returned in this OUT header.
|
CamelGeneratedKeysRows
|
*Camel 2.10:* Rows that contains the generated kets. |
CamelGeneratedKeysRowCount
|
*Camel 2.10:* The number of rows in the header that contains generated keys. |
Generated keys Copier lienLien copié sur presse-papiers!
CamelRetrieveGeneratedKeys=true
. Then the generated keys will be provided as headers with the keys listed in the table above.
Samples Copier lienLien copié sur presse-papiers!
testdb
:
JndiRegistry reg = super.createRegistry(); reg.bind("testdb", db); return reg;
JndiRegistry reg = super.createRegistry();
reg.bind("testdb", db);
return reg;
testdb
datasource that was bound in the previous step:
// lets add simple route public void configure() throws Exception { from("direct:hello").to("jdbc:testdb?readSize=100"); }
// lets add simple route
public void configure() throws Exception {
from("direct:hello").to("jdbc:testdb?readSize=100");
}
DataSource
in Spring like this:
Sample - Polling the database every minute Copier lienLien copié sur presse-papiers!
from("timer://foo?period=60000").setBody(constant("select * from customer")).to("jdbc:testdb").to("activemq:queue:customers");
from("timer://foo?period=60000").setBody(constant("select * from customer")).to("jdbc:testdb").to("activemq:queue:customers");
Chapter 51. Jetty Copier lienLien copié sur presse-papiers!
Jetty Component Copier lienLien copié sur presse-papiers!
String
which is safe to be re-read multiple times.
URI format Copier lienLien copié sur presse-papiers!
jetty:http://hostname[:port][/resourceUri][?options]
jetty:http://hostname[:port][/resourceUri][?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
sessionSupport
|
false
|
Specifies whether to enable the session manager on the server side of Jetty. |
httpClient.XXX
|
null
|
Configuration of Jetty's HttpClient. For example, setting httpClient.idleTimeout=30000 sets the idle timeout to 30 seconds.
|
httpBindingRef
|
null
|
Reference to an org.apache.camel.component.http.HttpBinding in the Registry. HttpBinding can be used to customize how a response should be written for the consumer.
|
jettyHttpBindingRef
|
null
|
*Camel 2.6.0+:* Reference to an org.apache.camel.component.jetty.JettyHttpBinding in the Registry. JettyHttpBinding can be used to customize how a response should be written for the producer.
|
matchOnUriPrefix
|
false
|
Whether or not the CamelServlet should try to find a target consumer by matching the URI prefix if no exact match is found. See here How do I let Jetty match wildcards.
|
handlers
|
null
|
Specifies a comma-delimited set of org.mortbay.jetty.Handler instances in your Registry (such as your Spring ApplicationContext ). These handlers are added to the Jetty servlet context (for example, to add security).
|
chunked
|
true
|
*Camel 2.2:* If this option is false Jetty servlet will disable the HTTP streaming and set the content-length header on the response |
enableJmx
|
false
|
*Camel 2.3:* If this option is true, Jetty JMX support will be enabled for this endpoint. See Jetty JMX support for more details. |
disableStreamCache
|
false
|
*Camel 2.3:* Determines whether or not the raw input stream from Jetty is cached or not (Camel will read the stream into a in memory/overflow to file, Stream caching) cache. By default Camel will cache the Jetty input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream, such as streaming it directly to a file or other persistent store. DefaultHttpBinding will copy the request input stream into a stream cache and put it into message body if this option is false to support reading the stream multiple times. If you use Jetty to bridge/proxy an endpoint then consider enabling this option to improve performance, in case you do not need to read the message payload multiple times.
|
bridgeEndpoint
|
false
|
*Camel 2.1:* If the option is true , HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request. You may also set the throwExceptionOnFailure to be false to let the HttpProducer send all the fault response back. Camel 2.3: If the option is true, HttpProducer and CamelServlet will skip the gzip processing if the content-encoding is "gzip". Also consider setting disableStreamCache to true to optimize when bridging.
|
enableMultipartFilter
|
true
|
*Camel 2.5:* Whether Jetty org.eclipse.jetty.servlets.MultiPartFilter is enabled or not. You should set this value to false when bridging endpoints, to ensure multipart requests is proxied/bridged as well.
|
multipartFilterRef
|
null
|
*Camel 2.6:* Allows using a custom multipart filter. Note: setting multipartFilterRef forces the value of enableMultipartFilter to true .
|
FiltersRef
|
null
|
*Camel 2.9:* Allows using a custom filters which is putted into a list and can be find in the Registry |
continuationTimeout
|
null
|
*Camel 2.6:* Allows to set a timeout in millis when using Jetty as consumer (server). By default Jetty uses 30000. You can use a value of <= 0 to never expire. If a timeout occurs then the request will be expired and Jetty will return back a http error 503 to the client. This option is only in use when using Jetty with the Asynchronous Routing Engine.
|
useContinuation
|
true
|
*Camel 2.6:* Whether or not to use Jetty continuations for the Jetty Server. |
sslContextParametersRef
|
null
|
*Camel 2.8:* Reference to a org.apache.camel.util.jsse.SSLContextParameters in the CAMEL:Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
|
traceEnabled
|
false
|
Specifies whether to enable HTTP TRACE for this Jetty consumer. By default TRACE is turned off. |
Message Headers Copier lienLien copié sur presse-papiers!
http://myserver/myserver?orderid=123
, the exchange will contain a header named orderid
with the value 123.
Usage Copier lienLien copié sur presse-papiers!
Component Options Copier lienLien copié sur presse-papiers!
JettyHttpComponent
provides the following options:
Name | Default Value | Description |
---|---|---|
enableJmx
|
false
|
*Camel 2.3:* If this option is true, Jetty JMX support will be enabled for this endpoint. See Jetty JMX support for more details. |
sslKeyPassword
|
null
|
*Consumer only*: The password for the keystore when using SSL. |
sslPassword
|
null
|
*Consumer only*: The password when using SSL. |
sslKeystore
|
null
|
*Consumer only*: The path to the keystore. |
minThreads
|
null
|
*Camel 2.5* Consumer only: To set a value for minimum number of threads in server thread pool. |
maxThreads
|
null
|
*Camel 2.5* Consumer only: To set a value for maximum number of threads in server thread pool. |
threadPool
|
null
|
*Camel 2.5* Consumer only: To use a custom thread pool for the server. |
sslSocketConnectors
|
null
|
*Camel 2.3* Consumer only: A map which contains per port number specific SSL connectors. See section SSL support for more details. |
socketConnectors
|
null
|
*Camel 2.5* Consumer only: A map which contains per port number specific HTTP connectors. Uses the same principle as sslSocketConnectors and therefore see section SSL support for more details.
|
sslSocketConnectorProperties
|
null
|
*Camel 2.5* Consumer only. A map which contains general SSL connector properties. See section SSL support for more details. |
socketConnectorProperties
|
null
|
*Camel 2.5* Consumer only. A map which contains general HTTP connector properties. Uses the same principle as sslSocketConnectorProperties and therefore see section SSL support for more details.
|
httpClient
|
null
|
*Producer only*: To use a custom HttpClient with the jetty producer.
|
httpClientMinThreads
|
null
|
*Producer only*: To set a value for minimum number of threads in HttpClient thread pool.
|
httpClientMaxThreads
|
null
|
*Producer only*: To set a value for maximum number of threads in HttpClient thread pool.
|
httpClientThreadPool
|
null
|
*Producer only*: To use a custom thread pool for the client. |
sslContextParameters
|
null
|
*Camel 2.8:* To configure a custom SSL/TLS configuration options at the component level. See Using the JSSE Configuration Utility for more details. |
Producer Example Copier lienLien copié sur presse-papiers!
from("direct:start").to("jetty://http://www.google.com");
from("direct:start").to("jetty://http://www.google.com");
<route> <from uri="direct:start"/> <to uri="jetty://http://www.google.com"/> <route>
<route>
<from uri="direct:start"/>
<to uri="jetty://http://www.google.com"/>
<route>
Consumer Example Copier lienLien copié sur presse-papiers!
http://localhost:8080/myapp/myservice
:
from("jetty:http://localhost:{{port}}/myapp/myservice").process(new MyBookService());
from("jetty:http://localhost:{{port}}/myapp/myservice").process(new MyBookService());
localhost
in a URL, Camel exposes the endpoint only on the local TCP/IP network interface, so it cannot be accessed from outside the machine it operates on.
0.0.0.0
address should be used.
MyBookService
class, which accesses the HTTP request contents and then returns a response. Note: The assert
call appears in this example, because the code is part of an unit test.
one
, to the endpoint, mock:one
, and all others to mock:other
.
http://serverUri?one=hello
, the Jetty component will copy the HTTP request parameter, one
to the exchange's in.header
. We can then use the simple
language to route exchanges that contain this header to a specific endpoint and all others to another. If we used a language more powerful than Simple\-\--such as- El -or- OGNL\--we could also test for the parameter value and do routing based on the header value as well.
Session Support Copier lienLien copié sur presse-papiers!
sessionSupport
, can be used to enable a HttpSession
object and access the session object while processing the exchange. For example, the following route enables sessions:
<route> <from uri="jetty:http://0.0.0.0/myapp/myservice/?sessionSupport=true"/> <processRef ref="myCode"/> <route>
<route>
<from uri="jetty:http://0.0.0.0/myapp/myservice/?sessionSupport=true"/>
<processRef ref="myCode"/>
<route>
<bean id="myCode"class="com.mycompany.MyCodeProcessor"/>
<bean id="myCode"class="com.mycompany.MyCodeProcessor"/>
HttpSession
as follows:
public void process(Exchange exchange) throws Exception { HttpSession session = exchange.getIn(HttpMessage.class).getRequest().getSession(); ... }
public void process(Exchange exchange) throws Exception {
HttpSession session = exchange.getIn(HttpMessage.class).getRequest().getSession();
...
}
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
Programmatic configuration of the component Copier lienLien copié sur presse-papiers!
Spring DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
Configuring Jetty Directly Copier lienLien copié sur presse-papiers!
https://
prefix---for example:
<from uri="jetty:https://0.0.0.0/myapp/myservice/"/>
<from uri="jetty:https://0.0.0.0/myapp/myservice/"/>
jetty.ssl.keystore
specifies the location of the Java keystore file, which contains the Jetty server's own X.509 certificate in a key entry. A key entry stores the X.509 certificate (effectively, the public key) and also its associated private key.jetty.ssl.password
the store password, which is required to access the keystore file (this is the same password that is supplied to thekeystore
command's\-storepass
option).jetty.ssl.keypassword
the key password, which is used to access the certificate's key entry in the keystore (this is the same password that is supplied to thekeystore
command's\-keypass
option).
org.eclipse.jetty.ssl.keystore
specifies the location of the Java keystore file, which contains the Jetty server's own X.509 certificate in a key entry. A key entry stores the X.509 certificate (effectively, the public key) and also its associated private key.org.eclipse.jetty.ssl.password
the store password, which is required to access the keystore file (this is the same password that is supplied to thekeystore
command's\-storepass
option).org.eclipse.jetty.ssl.keypassword
the key password, which is used to access the certificate's key entry in the keystore (this is the same password that is supplied to thekeystore
command's\-keypass
option).
Configuring general SSL properties Copier lienLien copié sur presse-papiers!
How to obtain reference to the X509Certificate Copier lienLien copié sur presse-papiers!
HttpServletRequest req = exchange.getIn().getBody(HttpServletRequest.class); X509Certificate cert = (X509Certificate) req.getAttribute("javax.servlet.request.X509Certificate")
HttpServletRequest req = exchange.getIn().getBody(HttpServletRequest.class);
X509Certificate cert = (X509Certificate) req.getAttribute("javax.servlet.request.X509Certificate")
Configuring general HTTP properties Copier lienLien copié sur presse-papiers!
Default behavior for returning HTTP status codes Copier lienLien copié sur presse-papiers!
org.apache.camel.component.http.DefaultHttpBinding
class, which handles how a response is written and also sets the HTTP status code.
HttpProducer.HTTP_RESPONSE_CODE
header of the OUT message.
Customizing HttpBinding Copier lienLien copié sur presse-papiers!
org.apache.camel.component.http.DefaultHttpBinding
to handle how a response is written. If you like, you can customize this behavior either by implementing your own HttpBinding
class or by extending DefaultHttpBinding
and overriding the appropriate methods.
DefaultHttpBinding
in order to change how exceptions are returned:
<bean id="mybinding"class="com.mycompany.MyHttpBinding"/>
<bean id="mybinding"class="com.mycompany.MyHttpBinding"/>
<route><from uri="jetty:http://0.0.0.0:8080/myapp/myservice?httpBindingRef=mybinding"/><to uri="bean:doSomething"/></route>
<route><from uri="jetty:http://0.0.0.0:8080/myapp/myservice?httpBindingRef=mybinding"/><to uri="bean:doSomething"/></route>
Jetty handlers and security configuration Copier lienLien copié sur presse-papiers!
from("jetty:http://0.0.0.0:9080/myservice?handlers=securityHandler")
from("jetty:http://0.0.0.0:9080/myservice?handlers=securityHandler")
handlers
option equal to a comma-separated list of bean IDs.
How to return a custom HTTP 500 reply message Copier lienLien copié sur presse-papiers!
HttpBinding
to be in control of the message mapping, but often it may be easier to use Camel's Exception Clause to construct the custom reply message. For example as show here, where we return Dude something went wrong
with HTTP error code 500:
Multi-part Form support Copier lienLien copié sur presse-papiers!
Jetty JMX support Copier lienLien copié sur presse-papiers!
<from uri="jetty:https://0.0.0.0/myapp/myservice1/?enableJmx=true"/>
<from uri="jetty:https://0.0.0.0/myapp/myservice1/?enableJmx=true"/>
<from uri="jetty:https://0.0.0.0/myapp/myservice2/?enableJmx=false"/>
<from uri="jetty:https://0.0.0.0/myapp/myservice2/?enableJmx=false"/>
Chapter 52. Jing Copier lienLien copié sur presse-papiers!
Jing Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
rng:someLocalOrRemoteResource rnc:someLocalOrRemoteResource
rng:someLocalOrRemoteResource
rnc:someLocalOrRemoteResource
Example | Description |
---|---|
rng:foo/bar.rng
|
References the XML file foo/bar.rng on the classpath |
rnc:http://foo.com/bar.rnc
|
References the RelaxNG Compact Syntax file from the URL, http://foo.com/bar.rnc .
|
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
useDom
|
false
|
Apache Camel 2.0: Specifies whether DOMSource/DOMResult or SaxSource/SaxResult should be used by the validator. |
Example Copier lienLien copié sur presse-papiers!
Chapter 53. JMS Copier lienLien copié sur presse-papiers!
JMS Component Copier lienLien copié sur presse-papiers!
JmsTemplate
for sending and a MessageListenerContainer
for consuming.
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
jms:[queue:|topic:]destinationName[?options]
jms:[queue:|topic:]destinationName[?options]
destinationName
is a JMS queue or topic name. By default, the destinationName
is interpreted as a queue name. For example, to connect to the queue, FOO.BAR
use:
jms:FOO.BAR
jms:FOO.BAR
queue:
prefix, if you prefer:
jms:queue:FOO.BAR
jms:queue:FOO.BAR
topic:
prefix. For example, to connect to the topic, Stocks.Prices
, use:
jms:topic:Stocks.Prices
jms:topic:Stocks.Prices
?option=value&option=value&...
Using ActiveMQ Copier lienLien copié sur presse-papiers!
JmsTemplate
for sending messages. This is not ideal for use in a non-J2EE container and typically requires some caching in the JMS provider to avoid poor performance.
- Use the ActiveMQ component, which is already optimized to use ActiveMQ efficiently
- Use the
PoolingConnectionFactory
in ActiveMQ.
Transactions and Cache Levels Copier lienLien copié sur presse-papiers!
transacted=true
) then the default settings for cache level can impact performance. If you are using XA transactions then you cannot cache as it can cause the XA transaction to not work properly.
cacheLevelName=CACHE_CONSUMER
.
cacheLevelName
is CACHE_CONSUMER
. You will need to explicitly set cacheLevelName=CACHE_NONE
. In Camel 2.8 onwards, the default setting for cacheLevelName
is CACHE_AUTO
. This default auto detects the mode and sets the cache level accordingly to:
- CACHE_CONSUMER = if transacted=false
- CACHE_NONE = if transacted=true
cacheLevelName=CACHE_CONSUMER
if you are using non-XA transactions.
Durable Subscriptions Copier lienLien copié sur presse-papiers!
clientId
must be unique and can only be used by a single JMS connection instance in your entire network. You may prefer to use Virtual Topics instead to avoid this limitation. More background on durable messaging here.
Message Header Mapping Copier lienLien copié sur presse-papiers!
- Dots are replaced by
\_DOT\_
and the replacement is reversed when Camel consume the message - Hyphen is replaced by
\_HYPHEN\_
and the replacement is reversed when Camel consumes the message
Options Copier lienLien copié sur presse-papiers!
Most commonly used options Copier lienLien copié sur presse-papiers!
Option | Default Value | Description |
---|---|---|
clientId
|
null
|
Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. You may prefer to use Virtual Topics instead. |
concurrentConsumers
|
1
|
Specifies the default number of concurrent consumers. |
disableReplyTo
|
false
|
If true , a producer will behave like a InOnly exchange with the exception that JMSReplyTo header is sent out and not be suppressed like in the case of InOnly . Like InOnly the producer will not wait for a reply. A consumer with this flag will behave like InOnly . This feature can be used to bridge InOut requests to another queue so that a route on the other queue will send it�s response directly back to the original JMSReplyTo .
|
durableSubscriptionName
|
null
|
The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.
|
maxConcurrentConsumers
|
1
|
Specifies the maximum number of concurrent consumers. |
maxMessagesPerTask
|
\-1
|
The number of messages per task. \-1 is unlimited. If you use a range for concurrent consumers (eg min < max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.
|
preserveMessageQos
|
false
|
Set to true , if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority , JMSDeliveryMode , and JMSExpiration . You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header.
|
replyTo
|
null
|
Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo() . If you do Request Reply over JMS then make sure to read the section Request-reply over JMS further below for more details, and the replyToType option as well.
|
replyToType
|
null
|
*Camel 2.9:* Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary , Shared , or Exclusive . By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See further below for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive .
|
requestTimeout
|
20000
|
*Producer only:* The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. See below in section About time to live for more details. See also the requestTimeoutCheckerInterval option. |
selector
|
null
|
Sets the JMS Selector, which is an SQL 92 predicate that is used to filter messages within the broker. You may have to encode special characters such as = as %3D Before Camel 2.3.0, we don't support this option in CamelConsumerTemplate |
timeToLive
|
null
|
When sending messages, specifies the time-to-live of the message (in milliseconds). See below in section About time to live for more details. |
transacted
|
false
|
Specifies whether to use transacted mode for sending/receiving messages using the InOnly Exchange Pattern. |
testConnectionOnStartup
|
false
|
*Camel 2.1:* Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. From Camel 2.8 onwards also the JMS producers is tested as well. |
All the other options Copier lienLien copié sur presse-papiers!
Option | Default Value | Description |
---|---|---|
acceptMessagesWhileStopping
|
false
|
Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqued on the queue. If this option is false , and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option.
|
acknowledgementModeName
|
AUTO_ACKNOWLEDGE
|
The JMS acknowledgement name, which is one of: TRANSACTED , CLIENT_ACKNOWLEDGE , AUTO_ACKNOWLEDGE , DUPS_OK_ACKNOWLEDGE
|
acknowledgementMode
|
\-1
|
The JMS acknowledgement mode defined as an Integer. Allows you to set vendor-specific extensions to the acknowledgment mode. For the regular modes, it is preferable to use the acknowledgementModeName instead.
|
allowNullBody
|
true
|
*Camel 2.9.3/2.10.1:* Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.
|
alwaysCopyMessage
|
false
|
If true , Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true , if a replyToDestinationSelectorName is set)
|
asyncConsumer
|
false
|
*Camel 2.9:* Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer=true does not run asynchronously, as transactions must be executed synchronously (Camel 3.0 may support async transactions).
|
asyncStartListener
|
false
|
*Camel 2.10:* Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true , you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.
|
asyncStopListener
|
false
|
*Camel 2.10:* Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.
|
autoStartup
|
true
|
Specifies whether the consumer container should auto-startup. |
cacheLevelName
|
CACHE_AUTO (Camel >= 2.8.0) CACHE_CONSUMER (Camel <= 2.7.1)
|
Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO , CACHE_CONNECTION , CACHE_CONSUMER , CACHE_NONE , and CACHE_SESSION . The default setting for Camel 2.8 and newer is CACHE_AUTO . For Camel 2.7.1 and older the default is CACHE_CONSUMER . See the Spring documentation and Transactions Cache Levels for more information.
|
cacheLevel
|
Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.
|
|
consumerType
|
Default
|
The consumer type to use, which can be one of: Simple , Default , or Custom . The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer , Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer . When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactoryRef option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use (new option in Camel 2.11 and 2.10.2). This option was temporary removed in Camel 2.7 and 2.8. But has been added back from Camel 2.9 onwards.
|
connectionFactory
|
null
|
The default JMS connection factory to use for the listenerConnectionFactory and templateConnectionFactory , if neither is specified.
|
deliveryPersistent
|
true
|
Specifies whether persistent delivery is used by default. |
destination
|
null
|
Specifies the JMS Destination object to use on this endpoint. |
destinationName
|
null
|
Specifies the JMS destination name to use on this endpoint. |
destinationResolver
|
null
|
A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).
|
disableTimeToLive
|
false
|
*Camel 2.8:* Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.
|
eagerLoadingOfProperties
|
false
|
Enables eager loading of JMS properties as soon as a message is received, which is generally inefficient, because the JMS properties might not be required. But this feature can sometimes catch early any issues with the underlying JMS provider and the use of JMS properties. This feature can also be used for testing purposes, to ensure JMS properties can be understood and handled correctly. |
exceptionListener
|
null
|
Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. |
errorHandler
|
null
|
*Camel 2.8.2, 2.9:* Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message . By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. From Camel 2.9.1: onwards you can configure logging level and whether stack traces should be logged using the below two options. This makes it much easier to configure, than having to code a custom errorHandler .
|
errorHandlerLoggingLevel
|
WARN
|
*Camel 2.9.1:* Allows to configure the default errorHandler logging level for logging uncaught exceptions.
|
errorHandlerLogStackTrace
|
true
|
*Camel 2.9.1:* Allows to control whether stacktraces should be logged or not, by the default errorHandler .
|
explicitQosEnabled
|
false
|
Set if the deliveryMode , priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring's JmsTemplate . The deliveryMode , priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.
|
exposeListenerSession
|
true
|
Specifies whether the listener session should be exposed when consuming messages. |
forceSendOriginalMessage
|
false
|
*Camel 2.7:* When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.
|
idleTaskExecutionLimit
|
1
|
Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting).
|
idleConsumerLimit
|
1
|
*Camel 2.8.2, 2.9:* Specify the limit for the number of consumers that are allowed to be idle at any given time. |
includeSentJMSMessageID
|
false
|
*Camel 2.10.3:* Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. |
jmsMessageType
|
null
|
Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes , Map , Object , Stream , Text . By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.
|
jmsKeyFormatStrategy
|
default
|
Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough . The default strategy will safely marshal dots and hyphens (. and \- ). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the \# notation.
|
jmsOperations
|
null
|
Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose, but not used much as stated in the spring API docs.
|
lazyCreateTransactionManager
|
true
|
If true , Camel will create a JmsTransactionManager , if there is no transactionManager injected when option transacted=true .
|
listenerConnectionFactory
|
null
|
The JMS connection factory used for consuming messages. |
mapJmsMessage
|
true
|
Specifies whether Camel should auto map the received JMS message to an appropiate payload type, such as javax.jms.TextMessage to a String etc. See section about how mapping works below for more details.
|
maximumBrowseSize
|
\-1
|
Limits the number of messages fetched at most, when browsing endpoints using Browse or JMX API. |
messageConverter
|
null
|
To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be 100% in control how to map to/from a javax.jms.Message .
|
messageIdEnabled
|
true
|
When sending, specifies whether message IDs should be added. |
messageListenerContainerFactoryRef
|
null
|
*Camel 2.10.2, 2.11:* Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom .
|
messageTimestampEnabled
|
true
|
Specifies whether timestamps should be enabled by default on sending messages. |
password
|
null
|
The password for the connector factory. |
priority
|
4
|
Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.
|
pubSubNoLocal
|
false
|
Specifies whether to inhibit the delivery of messages published by its own connection. |
receiveTimeout
|
_None_ | The timeout for receiving messages (in milliseconds). |
recoveryInterval
|
5000
|
Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. |
replyToCacheLevelName
|
CACHE_CONSUMER |
*Camel 2.9.1:* Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName . And CACHE_SESSION for shared without replyToSelectorName . Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work.
|
replyToDestinationSelectorName
|
null
|
Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue). |
replyToDeliveryPersistent
|
true
|
Specifies whether to use persistent delivery by default for replies. |
requestTimeoutCheckerInterval
|
1000
|
*Camel 2.9.2:* Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS.By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. |
subscriptionDurable
|
false
|
*@deprecated:* Enabled by default, if you specify a durableSubscriberName and a clientId .
|
taskExecutor
|
null
|
Allows you to specify a custom task executor for consuming messages. |
taskExecutorSpring2
|
null
|
*Camel 2.6:* To use when using Spring 2.x with Camel. Allows you to specify a custom task executor for consuming messages. |
templateConnectionFactory
|
null
|
The JMS connection factory used for sending messages. |
transactedInOut
|
false
|
*@deprecated:* Specifies whether to use transacted mode for sending messages using the InOut Exchange Pattern. Applies only to producer endpoints. See section Enabling Transacted Consumption for more details. |
transactionManager
|
null
|
The Spring transaction manager to use. |
transactionName
|
"JmsConsumer[destinationName]"
|
The name of the transaction to use. |
transactionTimeout
|
null
|
The timeout value of the transaction (in seconds), if using transacted mode. |
transferException
|
false
|
If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage . If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer.
|
transferExchange
|
false
|
You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload.
|
username
|
null
|
The username for the connector factory. |
useMessageIDAsCorrelationID
|
false
|
Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.
|
useVersion102
|
false
|
*@deprecated (removed from Camel 2.5 onwards):* Specifies whether the old JMS API should be used. |
Message Mapping between JMS and Camel Copier lienLien copié sur presse-papiers!
javax.jms.Message
and org.apache.camel.Message
.
Body Type | JMS Message | Comment |
---|---|---|
String
|
javax.jms.TextMessage
|
|
org.w3c.dom.Node
|
javax.jms.TextMessage
|
The DOM will be converted to String .
|
Map
|
javax.jms.MapMessage
|
|
java.io.Serializable
|
javax.jms.ObjectMessage
|
|
byte[]
|
javax.jms.BytesMessage
|
|
java.io.File
|
javax.jms.BytesMessage
|
|
java.io.Reader
|
javax.jms.BytesMessage
|
|
java.io.InputStream
|
javax.jms.BytesMessage
|
|
java.nio.ByteBuffer
|
javax.jms.BytesMessage
|
JMS Message | Body Type |
---|---|
javax.jms.TextMessage
|
String
|
javax.jms.BytesMessage
|
byte[]
|
javax.jms.MapMessage
|
Map<String, Object>
|
javax.jms.ObjectMessage
|
Object
|
Disabling auto-mapping of JMS messages Copier lienLien copié sur presse-papiers!
mapJmsMessage
option to disable the auto-mapping above. If disabled, Camel will not try to map the received JMS message, but instead uses it directly as the payload. This allows you to avoid the overhead of mapping and let Camel just pass through the JMS message. For instance, it even allows you to route javax.jms.ObjectMessage
JMS messages with classes you do not have on the classpath.
Using a custom MessageConverter Copier lienLien copié sur presse-papiers!
messageConverter
option to do the mapping yourself in a Spring org.springframework.jms.support.converter.MessageConverter
class.
from("file://inbox/order").to("jms:queue:order?messageConverter=#myMessageConverter");
from("file://inbox/order").to("jms:queue:order?messageConverter=#myMessageConverter");
Controlling the mapping strategy selected Copier lienLien copié sur presse-papiers!
javax.jms.TextMessage
as we have forced the JMS producer endpoint to use text messages:
from("file://inbox/order").to("jms:queue:order?jmsMessageType=Text");
from("file://inbox/order").to("jms:queue:order?jmsMessageType=Text");
CamelJmsMessageType
. For example:
from("file://inbox/order").setHeader("CamelJmsMessageType", JmsMessageType.Text).to("jms:queue:order");
from("file://inbox/order").setHeader("CamelJmsMessageType", JmsMessageType.Text).to("jms:queue:order");
enum
class, org.apache.camel.jms.JmsMessageType
.
Message format when sending Copier lienLien copié sur presse-papiers!
exchange.in.header
the following rules apply for the header keys:
- Keys starting with
JMS
orJMSX
are reserved. exchange.in.headers
keys must be literals and all be valid Java identifiers (do not use dots in the key name).- Camel replaces dots & hyphens and the reverse when when consuming JMS messages:
.
is replaced by\_DOT\_
and the reverse replacement when Camel consumes the message.\-
is replaced by\_HYPHEN\_
and the reverse replacement when Camel consumes the message. - See also the option
jmsKeyFormatStrategy
, which allows use of your own custom strategy for formatting keys.
exchange.in.header
, the following rules apply for the header values:
- The values must be primitives or their counter objects (such as
Integer
,Long
,Character
). The types,String
,CharSequence
,Date
,BigDecimal
andBigInteger
are all converted to theirtoString()
representation. All other types are dropped.
org.apache.camel.component.jms.JmsBinding
at DEBUG level if it drops a given header value. For example:
2008-07-09 06:43:04,046 [main ] DEBUG JmsBinding - Ignoring non primitive header: order of class: org.apache.camel.component.jms.issues.DummyOrder with value: DummyOrder{orderId=333, itemId=4444, quantity=2}
2008-07-09 06:43:04,046 [main ] DEBUG JmsBinding
- Ignoring non primitive header: order of class: org.apache.camel.component.jms.issues.DummyOrder with value: DummyOrder{orderId=333, itemId=4444, quantity=2}
Message format when receiving Copier lienLien copié sur presse-papiers!
Exchange
when it receives a message:
Property | Type | Description |
---|---|---|
org.apache.camel.jms.replyDestination
|
javax.jms.Destination
|
The reply destination. |
Header | Type | Description |
---|---|---|
JMSCorrelationID
|
String
|
The JMS correlation ID. |
JMSDeliveryMode
|
int
|
The JMS delivery mode. |
JMSDestination
|
javax.jms.Destination
|
The JMS destination. |
JMSExpiration
|
long
|
The JMS expiration. |
JMSMessageID
|
String
|
The JMS unique message ID. |
JMSPriority
|
int
|
The JMS priority (with 0 as the lowest priority and 9 as the highest). |
JMSRedelivered
|
boolean
|
Is the JMS message redelivered. |
JMSReplyTo
|
javax.jms.Destination
|
The JMS reply-to destination. |
JMSTimestamp
|
long
|
The JMS timestamp. |
JMSType
|
String
|
The JMS type. |
JMSXGroupID
|
String
|
The JMS group ID. |
About using Camel to send and receive messages and JMSReplyTo Copier lienLien copié sur presse-papiers!
JMSProducer
, it checks the following conditions:
- The message exchange pattern,
- Whether a
JMSReplyTo
was set in the endpoint or in the message headers, - Whether any of the following options have been set on the JMS endpoint:
disableReplyTo
,preserveMessageQos
,explicitQosEnabled
.
JmsProducer Copier lienLien copié sur presse-papiers!
JmsProducer
behaves as follows, depending on configuration:
Exchange Pattern | Other options | Description |
---|---|---|
_InOut_ | \- |
Camel will expect a reply, set a temporary JMSReplyTo , and after sending the message, it will start to listen for the reply message on the temporary queue.
|
_InOut_ |
JMSReplyTo is set
|
Camel will expect a reply and, after sending the message, it will start to listen for the reply message on the specified JMSReplyTo queue.
|
_InOnly_ | \- | Camel will send the message and not expect a reply. |
_InOnly_ |
JMSReplyTo is set
|
By default, Camel discards the JMSReplyTo destination and clears the JMSReplyTo header before sending the message. Camel then sends the message and does not expect a reply. Camel logs this in the log at WARN level (changed to DEBUG level from Camel 2.6 onwards. You can use preserveMessageQuo=true to instruct Camel to keep the JMSReplyTo . In all situations the JmsProducer does not expect any reply and thus continue after sending the message.
|
JmsConsumer Copier lienLien copié sur presse-papiers!
JmsConsumer
behaves as follows, depending on configuration:
Exchange Pattern | Other options | Description |
---|---|---|
_InOut_ | \- |
Camel will send the reply back to the JMSReplyTo queue.
|
_InOnly_ | \- | Camel will not send a reply back, as the pattern is InOnly. |
\- |
disableReplyTo=true
|
This option suppresses replies. |
InOnly
message to a JMS topic:
from("activemq:queue:in") .to("bean:validateOrder") .to(ExchangePattern.InOnly, "activemq:topic:order") .to("bean:handleOrder");
from("activemq:queue:in")
.to("bean:validateOrder")
.to(ExchangePattern.InOnly, "activemq:topic:order")
.to("bean:handleOrder");
Reuse endpoint and send to different destinations computed at runtime Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelJmsDestination
|
javax.jms.Destination
|
A destination object. |
CamelJmsDestinationName
|
String
|
The destination name. |
from("file://inbox") .to("bean:computeDestination") .to("activemq:queue:dummy");
from("file://inbox")
.to("bean:computeDestination")
.to("activemq:queue:dummy");
dummy
, is just a placeholder. It must be provided as part of the JMS endpoint URL, but it will be ignored in this example.
computeDestination
bean, specify the real destination by setting the CamelJmsDestinationName
header as follows:
public void setJmsHeader(Exchange exchange) { String id = .... exchange.getIn().setHeader("CamelJmsDestinationName", "order:" + id"); }
public void setJmsHeader(Exchange exchange) {
String id = ....
exchange.getIn().setHeader("CamelJmsDestinationName", "order:" + id");
}
activemq:queue:order:2
, assuming the id
value was 2.
CamelJmsDestination
and the CamelJmsDestinationName
headers are set, CamelJmsDestination
takes priority.
Configuring different JMS providers Copier lienLien copié sur presse-papiers!
id
*attribute*. The preceding example configures an activemq
component. You could do the same to configure MQSeries, TibCo, BEA, Sonic and so on.
activemq
, you can then refer to destinations using the URI format, activemq:[queue:|topic:]destinationName
. You can use the same approach for all other JMS providers.
Using JNDI to find the ConnectionFactory Copier lienLien copié sur presse-papiers!
ConnectionFactory
rather than use the usual <bean>
mechanism in Spring. You can do this using Spring's factory bean or the new Spring XML namespace. For example:
Concurrent Consuming Copier lienLien copié sur presse-papiers!
concurrentConsumers
option to specify the number of threads servicing the JMS endpoint, as follows:
from("jms:SomeQueue?concurrentConsumers=20"). bean(MyClass.class);
from("jms:SomeQueue?concurrentConsumers=20").
bean(MyClass.class);
- On the
JmsComponent
, - On the endpoint URI or,
- By invoking
setConcurrentConsumers()
directly on theJmsEndpoint
.
Request-reply over JMS Copier lienLien copié sur presse-papiers!
InOut
when you send a message to a JMS queue.
Option | Performance | Cluster | Description |
---|---|---|---|
Temporary
|
Fast | Yes |
A temporary queue is used as reply queue, and automatic created by Camel. To use this do not specify a replyTo queue name. And you can optionally configure replyToType=Temporary to make it stand out that temporary queues are in use.
|
Shared
|
Slow | Yes |
A shared persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you can optionally configure replyToType=Shared to make it stand out that shared queues are in use. A shared queue can be used in a clustered environment with multiple nodes running this Camel application at the same time. All using the same shared reply queue. This is possible because JMS Message selectors are used to correlate expected reply messages; this impacts performance though. JMS Message selectors is slower, and therefore not as fast as Temporary or Exclusive queues. See further below how to tweak this for better performance.
|
Exclusive
|
Fast | No |
An exclusive persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you must configure replyToType=Exclusive to instruct Camel to use exclusive queues, as Shared is used by default, if a replyTo queue name was configured. When using exclusive reply queues, then JMS Message selectors are not in use, and therefore other applications must not use this queue as well. An exclusive queue cannot be used in a clustered environment with multiple nodes running this Camel application at the same time; as we do not have control if the reply queue comes back to the same node that sent the request message; that is why shared queues use JMS Message selectors to make sure of this.
|
JmsProducer
detects the InOut
and provides a JMSReplyTo
header with the reply destination to be used. By default Camel uses a temporary queue, but you can use the replyTo
option on the endpoint to specify a fixed reply queue (see more below about fixed reply queue).
DefaultMessageListenerContainer
which listen for replies. However it's fixed to 1 concurrent consumer. That means replies will be processed in sequence as there are only 1 thread to process the replies. If you want to process replies faster, then we need to use concurrency. But not using the concurrentConsumer
option. We should use the threads
from the Camel DSL instead, as shown in the route below:
Request-reply over JMS and using an exclusive fixed reply queue Copier lienLien copié sur presse-papiers!
JMSSelector
to only consume reply messages which it expects. However there is a drawback doing this as JMS selectos is slower. Also the consumer on the reply queue is slower to update with new JMS selector ids. In fact it only updates when the receiveTimeout
option times out, which by default is 1 second. So in theory the reply messages could take up till about 1 sec to be detected. On the other hand if the fixed reply queue is exclusive to the Camel reply consumer, then we can avoid using the JMS selectors, and thus be more performant. In fact as fast as using temporary queues. So in Camel 2.9 onwards we introduced the ReplyToType
option which you can configure to Exclusive
to tell Camel that the reply queue is exclusive as shown in the example below:
from(xxx) .inOut().to("activemq:queue:foo?replyTo=bar&replyToType=Exclusive") .to(yyy)
from(xxx)
.inOut().to("activemq:queue:foo?replyTo=bar&replyToType=Exclusive")
.to(yyy)
Synchronizing clocks between senders and receivers Copier lienLien copié sur presse-papiers!
About time to live Copier lienLien copié sur presse-papiers!
requestTimeout
option. You can control this by setting a higher/lower value. However the time to live value is still set on the JMS message being send. So that requires the clocks to be synchronized between the systems. If they are not, then you may want to disable the time to live value being set. This is now possible using the disableTimeToLive
option from Camel 2.8 onwards. So if you set this option to disableTimeToLive=true
, then Camel does not set any time to live value when sending JMS messages. But the request timeout is still active. So for example if you do request/reply over JMS and have disabled time to live, then Camel will still use a timeout by 20 seconds (the requestTimeout
option). That option can of course also be configured. So the two options requestTimeout
and disableTimeToLive
gives you fine grained control when doing request/reply.
timeToLive
option. For example to indicate a 5 sec., you set timeToLive=5000
. The option disableTimeToLive
can be used to force disabling the time to live, also for InOnly messaging. The requestTimeout
option is not being used for InOnly messaging.
Enabling Transacted Consumption Copier lienLien copié sur presse-papiers!
transacted
= truetransactionManager
= a Transsaction Manager \- typically theJmsTransactionManager
transacted
= truelazyCreateTransactionManager
= false
Using JMSReplyTo for late replies Copier lienLien copié sur presse-papiers!
javax.jms.Destination
object, having the key ReplyTo
. You can obtain this Destination
as follows:
Destination replyDestination = exchange.getIn().getHeader(JmsConstants.JMS_REPLY_DESTINATION, Destination.class);
Destination replyDestination = exchange.getIn().getHeader(JmsConstants.JMS_REPLY_DESTINATION, Destination.class);
// we need to pass in the JMS component, and in this sample we use ActiveMQ JmsEndpoint endpoint = JmsEndpoint.newInstance(replyDestination, activeMQComponent); // now we have the endpoint we can use regular Camel API to send a message to it template.sendBody(endpoint, "Here is the late reply.");
// we need to pass in the JMS component, and in this sample we use ActiveMQ
JmsEndpoint endpoint = JmsEndpoint.newInstance(replyDestination, activeMQComponent);
// now we have the endpoint we can use regular Camel API to send a message to it
template.sendBody(endpoint, "Here is the late reply.");
replyDestination
object in the same Exchange property when sending. Camel will then pick up this property and use it for the real destination. The endpoint URI must include a dummy destination, however. For example:
Using a request timeout Copier lienLien copié sur presse-papiers!
requestBody
method = InOut
) to the slow queue for further processing in Camel and we wait for a return reply:
// send a in-out with a timeout for 5 sec Object out = template.requestBody("activemq:queue:slow?requestTimeout=5000", "Hello World");
// send a in-out with a timeout for 5 sec
Object out = template.requestBody("activemq:queue:slow?requestTimeout=5000", "Hello World");
Samples Copier lienLien copié sur presse-papiers!
Receiving from JMS Copier lienLien copié sur presse-papiers!
from("jms:queue:foo"). to("bean:myBusinessLogic");
from("jms:queue:foo").
to("bean:myBusinessLogic");
from("jms:topic:OrdersTopic"). filter().method("myBean", "isGoldCustomer"). to("jms:queue:BigSpendersQueue");
from("jms:topic:OrdersTopic").
filter().method("myBean", "isGoldCustomer").
to("jms:queue:BigSpendersQueue");
Sending to a JMS Copier lienLien copié sur presse-papiers!
TextMessage
instead of a BytesMessage
, we need to convert the body to a String
:
from("file://orders"). convertBodyTo(String.class). to("jms:topic:OrdersTopic");
from("file://orders").
convertBodyTo(String.class).
to("jms:topic:OrdersTopic");
Using Annotations Copier lienLien copié sur presse-papiers!
Spring DSL sample Copier lienLien copié sur presse-papiers!
Other samples Copier lienLien copié sur presse-papiers!
Using JMS as a Dead Letter Queue storing Exchange Copier lienLien copié sur presse-papiers!
javax.jms.ObjectMessage
that holds a org.apache.camel.impl.DefaultExchangeHolder
. This allows you to consume from the Dead Letter Queue and retrieve the caused exception from the Exchange property with the key Exchange.EXCEPTION_CAUGHT
. The demo below illustrates this:
// setup error handler to use JMS as queue and store the entire Exchange errorHandler(deadLetterChannel("jms:queue:dead?transferExchange=true"));
// setup error handler to use JMS as queue and store the entire Exchange
errorHandler(deadLetterChannel("jms:queue:dead?transferExchange=true"));
Using JMS as a Dead Letter Channel storing error only Copier lienLien copié sur presse-papiers!
Sending an InOnly message and keeping the JMSReplyTo header Copier lienLien copié sur presse-papiers!
preserveMessageQos=true
to instruct Camel to keep the JMSReplyTo header.
Setting JMS provider options on the destination Copier lienLien copié sur presse-papiers!
... .setHeader("CamelJmsDestinationName", constant("queue:///MY_QUEUE?targetClient=1")) .to("wmq:queue:MY_QUEUE?useMessageIDAsCorrelationID=true");
...
.setHeader("CamelJmsDestinationName", constant("queue:///MY_QUEUE?targetClient=1"))
.to("wmq:queue:MY_QUEUE?useMessageIDAsCorrelationID=true");
com.ibm.msg.client.jms.DetailedJMSException: JMSCC0005: The specified value 'MY_QUEUE?targetClient=1' is not allowed for 'XMSC_DESTINATION_NAME'
Chapter 54. JMX Copier lienLien copié sur presse-papiers!
JMX Component Copier lienLien copié sur presse-papiers!
Notification
object directly through the exchange or serializing it to XML according to the schema provided within this project. This is a consumer-only component. Exceptions are thrown if you attempt to create a producer for it.
URI Format Copier lienLien copié sur presse-papiers!
jmx://platform?options
jmx://platform?options
jmx:
scheme prefix, as follows:
jmx:service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi?options
jmx:service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi?options
?option=value&option=value&...
.
URI Options Copier lienLien copié sur presse-papiers!
Property | Required | Default | Description |
---|---|---|---|
format
|
xml
|
Format for the message body. Either xml or raw . If xml , the notification is serialized to XML. If raw , the raw java object is set as the body.
|
|
password
|
Credentials for making a remote connection. | ||
objectDomain
|
Yes | The domain of the MBean you are connecting to. | |
objectName
|
The name key for the MBean you are connecting to. Either this property of a list of keys must be provided (but not both). For more details, see the section called “ObjectName Construction”. | ||
notificationFilter
|
Reference to a bean that implements the NotificationFilter interface. The #beanID syntax should be used to reference the bean in the registry.
|
||
handback
|
Value to hand back to the listener when a notification is received. This value will be put into the jmx.handback message header.
|
||
testConnectionOnStartup
|
true
|
*Camel 2.11* If true, the consumer will throw an exception when unable to establish the JMX connection upon startup. If false, the consumer will attempt to establish the JMX connection every 'x' seconds until the connection is made - where 'x' is the configured reconnectDelay. | |
reconnectOnConnectionFailure
|
false
|
*Camel 2.11* If true, the consumer will attempt to reconnect to the JMX server when any connection failure occurs. The consumer will attempt to re-establish the JMX connection every 'x' seconds until the connection is made-- where 'x' is the configured reconnectDelay. | |
reconnectDelay
|
10
|
*Camel 2.11* The number of seconds to wait before retrying creation of the initial connection or before reconnecting a lost connection. |
ObjectName Construction Copier lienLien copié sur presse-papiers!
objectDomain
property. In addition, the URI must contain either objectName
or one or more properties that start with key
.
Domain with Name property Copier lienLien copié sur presse-papiers!
objectName
property is provided, the following constructor is used to build the ObjectName
instance for the MBean:
ObjectName(String domain, String key, String value)
ObjectName(String domain, String key, String value)
key
value in the preceding constructor must be name
and the value is the value of the objectName
property.
Domain with Hashtable Copier lienLien copié sur presse-papiers!
ObjectName(String domain, Hashtable<String,String> table)
ObjectName(String domain, Hashtable<String,String> table)
Hashtable
is constructed by extracting properties that start with key
. The properties will have the key
prefix stripped prior to building the Hashtable
. This allows the URI to contain a variable number of properties to identify the MBean.
Example Copier lienLien copié sur presse-papiers!
from("jmx:platform?objectDomain=jmxExample&key.name=simpleBean"). to("log:jmxEvent");
from("jmx:platform?objectDomain=jmxExample&key.name=simpleBean").
to("log:jmxEvent");
Full example Copier lienLien copié sur presse-papiers!
examples/camel-example-jmx
directory.
Monitor Type Consumer Copier lienLien copié sur presse-papiers!
Example Copier lienLien copié sur presse-papiers!
from("jmx:platform?objectDomain=myDomain&objectName=simpleBean&" + "monitorType=counter&observedAttribute=MonitorNumber&initThreshold=1&" + "granularityPeriod=500").to("mock:sink");
from("jmx:platform?objectDomain=myDomain&objectName=simpleBean&" +
"monitorType=counter&observedAttribute=MonitorNumber&initThreshold=1&" +
"granularityPeriod=500").to("mock:sink");
MonitorNumber
attribute on the simpleBean
. Additional types of monitor beans and options are detailed below. The newly deployed monitor bean is automatically undeployed when the consumer is stopped.
URI Options for Monitor Type Copier lienLien copié sur presse-papiers!
property | type | applies to | description |
---|---|---|---|
monitorType
|
enum
|
all | one of the counters, guage, string |
observedAttribute
|
string
|
all | the attribute being observed |
granularityPeriod
|
long
|
all | granularity period (in millis) for the attribute being observed. As per JMX, default is 10 seconds |
initThreshold
|
number
|
counter | initial threshold value |
offset
|
number
|
counter | offset value |
modulus
|
number
|
counter | modulus value |
differenceMode
|
boolean
|
counter, gauge | true if difference should be reported, false for actual value |
notifyHigh
|
boolean
|
gauge | high notification on/off switch |
notifyLow
|
boolean
|
gauge | low notification on/off switch |
highThreshold
|
number
|
gauge | threshold for reporting high notification |
lowThreshold
|
number
|
gauge | threshold for reporting low notificaton |
notifyDiffer
|
boolean
|
string | true to fire notification when string differs |
notifyMatch
|
boolean
|
string | true to fire notification when string matches |
stringToCompare
|
string
|
string | string to compare against the attribute value |
Chapter 55. JPA Copier lienLien copié sur presse-papiers!
JPA Component Copier lienLien copié sur presse-papiers!
Sending to the endpoint Copier lienLien copié sur presse-papiers!
Consuming from the endpoint Copier lienLien copié sur presse-papiers!
consumeDelete=false
on the URI. This will result in the entity being processed each poll.
URI format Copier lienLien copié sur presse-papiers!
jpa:[entityClassName][?options]
jpa:[entityClassName][?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
entityType
|
entityClassName | Overrides the entityClassName from the URI. |
persistenceUnit
|
camel
|
The JPA persistence unit used by default. |
consumeDelete
|
true
|
JPA consumer only: If true , the entity is deleted after it is consumed; if false , the entity is not deleted.
|
consumeLockEntity
|
true
|
JPA consumer only: Specifies whether or not to set an exclusive lock on each entity bean while processing the results from polling. |
flushOnSend
|
true
|
JPA producer only: Flushes the EntityManager after the entity bean has been persisted. |
maximumResults
|
-1
|
JPA consumer only: Set the maximum number of results to retrieve on the Query. |
transactionManager
|
null
|
Apache Camel 1.6.1/2.0: Specifies the transaction manager to use. If none provided, Apache Camel will use a JpaTransactionManager by default. Can be used to set a JTA transaction manager (for integration with an EJB container).
|
consumer.delay
|
500
|
JPA consumer only: Delay in milliseconds between each poll. |
consumer.initialDelay
|
1000
|
JPA consumer only: Milliseconds before polling starts. |
consumer.useFixedDelay
|
false
|
JPA consumer only: Set to true to use fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
|
maxMessagesPerPoll
|
0
|
Apache Camel 2.0:JPA consumer only: An integer value to define the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to avoid polling many thousands of messages when starting up the server. Set a value of 0 or negative to disable. |
consumer.query
|
JPA consumer only: To use a custom query when consuming data. | |
consumer.namedQuery
|
JPA consumer only: To use a named query when consuming data. | |
consumer.nativeQuery
|
JPA consumer only: To use a custom native query when consuming data. | |
consumer.resultClass
|
Camel 2.7: JPA consumer only: Defines the type of the returned payload (we will call entityManager.createNativeQuery(nativeQuery, resultClass) instead of entityManager.createNativeQuery(nativeQuery) ). Without this option, we will return an object array. Only has an affect when using in conjunction with native query when consuming data.
|
|
consumer.transacted
|
false
|
*Camel 2.7.5/2.8.3/2.9: JPA consumer only:* Whether to run the consumer in transacted mode, by which all messages will either commit or rollback, when the entire batch has been processed. The default behavior (false) is to commit all the previously successfully processed messages, and only rollback the last failed message. |
usePersist
|
false
|
Camel 2.5: JPA producer only: Indicates to use entityManager.persist(entity) instead of entityManager.merge(entity) . Note: entityManager.persist(entity) doesn't work for detached entities (where the EntityManager has to execute an UPDATE instead of an INSERT query)!
|
Message Headers Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelJpaTemplate
|
JpaTemplate
|
Apache Camel 2.0: The JpaTemplate object that is used to access the entity bean. You need this object in some situations, for instance in a type converter or when you are doing some custom processing.
|
Configuring EntityManagerFactory Copier lienLien copié sur presse-papiers!
EntityManagerFactory
instance. If you do not do so, each JpaEndpoint
will auto-create its own EntityManagerFactory
instance.For example, you can instantiate a JPA component that references the myEMFactory
entity manager factory, as follows:
<bean id="jpa" class="org.apache.camel.component.jpa.JpaComponent"> <property name="entityManagerFactory" ref="myEMFactory"/> </bean>
<bean id="jpa" class="org.apache.camel.component.jpa.JpaComponent">
<property name="entityManagerFactory" ref="myEMFactory"/>
</bean>
JpaComponent
will auto lookup the EntityManagerFactory
from the Registry which means you do not need to configure this on the JpaComponent
as shown above. You only need to do so if there is ambiguity, in which case Camel will log a WARN.
Configuring TransactionManager Copier lienLien copié sur presse-papiers!
TransactionManager
instance used by the JPA component. If you do not do so, each JpaEndpoint
will auto-create its own instance of TransactionManager
. For example, you can instantiate a JPA component that references the myTransactionManager
transaction manager, as follows:
<bean id="jpa" class="org.apache.camel.component.jpa.JpaComponent"> <property name="entityManagerFactory" ref="myEMFactory"/> <property name="transactionManager" ref="myTransactionManager"/> </bean>
<bean id="jpa" class="org.apache.camel.component.jpa.JpaComponent">
<property name="entityManagerFactory" ref="myEMFactory"/>
<property name="transactionManager" ref="myTransactionManager"/>
</bean>
JpaComponent
will auto lookup the TransactionManager
from the Registry which means you do not need to configure this on the JpaComponent
as shown above. You only need to do so if there is ambiguity, in which case Camel will log a WARN.
Using a consumer with a named query Copier lienLien copié sur presse-papiers!
consumer.namedQuery
URI query option. First, you have to define the named query in the JPA Entity class:
@Entity @NamedQuery(name = "step1", query = "select x from MultiSteps x where x.step = 1") public class MultiSteps { ... }
@Entity
@NamedQuery(name = "step1", query = "select x from MultiSteps x where x.step = 1")
public class MultiSteps {
...
}
from("jpa://org.apache.camel.examples.MultiSteps?consumer.namedQuery=step1") .to("bean:myBusinessLogic");
from("jpa://org.apache.camel.examples.MultiSteps?consumer.namedQuery=step1")
.to("bean:myBusinessLogic");
Using a consumer with a query Copier lienLien copié sur presse-papiers!
consumer.query
URI query option. You only have to define the query option:
from("jpa://org.apache.camel.examples.MultiSteps?consumer.query=select o from org.apache.camel.examples.MultiSteps o where o.step = 1") .to("bean:myBusinessLogic");
from("jpa://org.apache.camel.examples.MultiSteps?consumer.query=select o from org.apache.camel.examples.MultiSteps o where o.step = 1")
.to("bean:myBusinessLogic");
Using a consumer with a native query Copier lienLien copié sur presse-papiers!
consumer.nativeQuery
URI query option. You only have to define the native query option:
from("jpa://org.apache.camel.examples.MultiSteps?consumer.nativeQuery=select * from MultiSteps where step = 1") .to("bean:myBusinessLogic");
from("jpa://org.apache.camel.examples.MultiSteps?consumer.nativeQuery=select * from MultiSteps where step = 1")
.to("bean:myBusinessLogic");
Example Copier lienLien copié sur presse-papiers!
Using the JPA based idempotent repository Copier lienLien copié sur presse-papiers!
persistence-unit
in the persistence.xml file:
org.springframework.orm.jpa.JpaTemplate
which is used by the org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository
:
org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository
:
Chapter 56. Jsch Copier lienLien copié sur presse-papiers!
Jsch Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
scp://host[:port]/destination[?options]
scp://host[:port]/destination[?options]
?option=value&option=value&...
Exchange.FILE_NAME
if used in code).
Options Copier lienLien copié sur presse-papiers!
Name | Description | Example | Default Value |
---|---|---|---|
username
|
Specifies the username to use to log in to the remote file system. |
null
|
|
password
|
Specifies the password to use to log in to the remote file system. |
null
|
|
knownHostsFile
|
Sets the known_hosts file, so that the scp endpoint can do host key verification.
|
null
|
|
strictHostKeyChecking
|
Sets whether to use strict host key checking. Possible values are: no , yes
|
no
|
|
chmod
|
Allows you to set chmod on the stored file. For example chmod=664 .
|
null
|
Limitations Copier lienLien copié sur presse-papiers!
Chapter 57. JT400 Copier lienLien copié sur presse-papiers!
JT/400 Component Copier lienLien copié sur presse-papiers!
jt400
component allows you to exchanges messages with an AS/400 system using data queues.
URI format Copier lienLien copié sur presse-papiers!
jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/QUEUE.DTAQ[?options]
jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/QUEUE.DTAQ[?options]
jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/program.PGM[?options]
jt400://user:password@system/QSYS.LIB/LIBRARY.LIB/program.PGM[?options]
?option=value&option=value&...
URI options Copier lienLien copié sur presse-papiers!
Name | Default value | Description |
---|---|---|
ccsid
|
default system CCSID | Specifies the CCSID to use for the connection with the AS/400 system. |
format
|
text
|
Specifies the data format for sending messages valid options are: text (represented by String ) and binary (represented by byte[] )
|
consumer.delay
|
500
|
Delay in milliseconds between each poll. |
consumer.initialDelay
|
1000
|
Milliseconds before polling starts. |
consumer.userFixedDelay
|
false
|
true to use fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
|
guiAvailable
|
false
|
Camel 2.8: Specifies whether AS/400 prompting is enabled in the environment running Camel. |
keyed
|
false
|
*Camel 2.10:* Whether to use keyed or non-keyed data queues. |
searchKey
|
null
|
*Camel 2.10:* Search key for keyed data queues. |
searchType
|
EQ
|
*Camel 2.10:* Search type which can be a value of EQ , NE , LT , LE , GT , or GE .
|
connectionPool
|
AS400ConnectionPool instance
|
*Camel 2.10:* Reference to an com.ibm.as400.access.AS400ConnectionPool instance in the Registry. This is used for obtaining connections to the AS/400 system. The look up notation ('#' character) should be used. |
Name | Default value | Description |
---|---|---|
outputFieldsIdx
|
Specifies which fields (program parameters) are output parameters. | |
fieldsLength
|
Specifies the fields (program parameters) length as in the AS/400 program definition. | |
format
|
text
|
*Camel 2.10:* Specifies the data format for sending messages valid options are: text (represented by String ) and binary (represented by byte[] )
|
guiAvailable
|
false
|
*Camel 2.8:* Specifies whether AS/400 prompting is enabled in the environment running Camel. |
connectionPool
|
AS400ConnectionPool instance
|
*Camel 2.10:* Reference to an com.ibm.as400.access.AS400ConnectionPool instance in the Registry. This is used for obtaining connections to the AS/400 system. The look up notation ('#' character) should be used. |
Usage Copier lienLien copié sur presse-papiers!
Exchange
is sent with the entry's data in the In message's body, formatted either as a String
or a byte[]
, depending on the format. For a provider endpoint, the In message body contents will be put on the data queue as either raw bytes or text.
Connection pool Copier lienLien copié sur presse-papiers!
Remote program call (Camel 2.7) Copier lienLien copié sur presse-papiers!
String
array or byte[]
array with the values as they were returned by the program (the input only parameters will contain the same data as the beginning of the invocation) This endpoint does not implement a provider endpoint!
Example Copier lienLien copié sur presse-papiers!
direct:george
endpoint will be put in the data queue PENNYLANE
in library BEATLES
on a system named LIVERPOOL
. Another user connects to the same data queue to receive the information from the data queue and forward it to the mock:ringo
endpoint.
Remote program call example (Camel 2.7) Copier lienLien copié sur presse-papiers!
Writing to keyed data queues Copier lienLien copié sur presse-papiers!
from("jms:queue:input") .to("jt400://username:password@system/lib.lib/MSGINDQ.DTAQ?keyed=true");
from("jms:queue:input")
.to("jt400://username:password@system/lib.lib/MSGINDQ.DTAQ?keyed=true");
Reading from keyed data queues Copier lienLien copié sur presse-papiers!
from("jt400://username:password@system/lib.lib/MSGOUTDQ.DTAQ?keyed=true&searchKey=MYKEY&searchType=GE") .to("jms:queue:output");
from("jt400://username:password@system/lib.lib/MSGOUTDQ.DTAQ?keyed=true&searchKey=MYKEY&searchType=GE")
.to("jms:queue:output");
Chapter 58. Kestrel Copier lienLien copié sur presse-papiers!
Kestrel Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
kestrel://[addresslist/]queuename[?options]
kestrel://[addresslist/]queuename[?options]
host:port
pairs. For example, to connect to the queue foo
on kserver01:22133
, use:
kestrel://kserver01:22133/foo
kestrel://kserver01:22133/foo
localhost:22133
is assumed, i.e.:
kestrel://foo
kestrel://foo
host:port
pair in addresslist, the default port 22133 is assumed, i.e.:
kestrel://kserver01/foo
kestrel://kserver01/foo
kestrel://kserver01:22133,kserver02:22133,kserver03:22133/massive
kestrel://kserver01:22133,kserver02:22133,kserver03:22133/massive
kestrel://kserver03:22133/massive?concurrentConsumers=25&waitTimeMs=500
kestrel://kserver03:22133/massive?concurrentConsumers=25&waitTimeMs=500
Options Copier lienLien copié sur presse-papiers!
?parameters
portion of the endpoint URI. Any ?parameters
that are omitted will default to what is configured on the KestrelComponent's base KestrelConfiguration. The following properties may be set on KestrelConfiguration and/or each individual endpoint:
Option | Default Value | Description |
---|---|---|
concurrentConsumers
|
1
|
Specifies the number of concurrent consumer threads. |
waitTimeMs
|
100
|
Specifies the /t=... wait time passed to Kestrel on GET requests.
|
/t=...
specifier does not get passed to the server on GET requests. When a queue is empty, the GET call returns immediately with no value. In order to prevent "tight looping" in the polling phase, this component will do a Thread.sleep(100)
whenever nothing is returned from the GET request (only when nothing is returned). You are highly encouraged to configure a positive non-zero value for waitTimeMs.
Configuring the Kestrel component using Spring XML Copier lienLien copié sur presse-papiers!
localhost:22133
, 100ms wait time, and a single non-concurrent consumer by default.
?properties
are not specified), you can set up a KestrelConfiguration POJO as follows:
Usage Examples Copier lienLien copié sur presse-papiers!
Example 1: Consuming Copier lienLien copié sur presse-papiers!
from("kestrel://kserver02:22133/massive?concurrentConsumers=10&waitTimeMs=500") .bean("myConsumer", "onMessage");
from("kestrel://kserver02:22133/massive?concurrentConsumers=10&waitTimeMs=500")
.bean("myConsumer", "onMessage");
Example 2: Producing Copier lienLien copié sur presse-papiers!
Example 3: Spring XML Configuration Copier lienLien copié sur presse-papiers!
Dependencies Copier lienLien copié sur presse-papiers!
spymemcached
2.5 (or greater)
spymemcached Copier lienLien copié sur presse-papiers!
spymemcached
jar on your classpath. Here is a snippet you can use in your pom.xml:
/t=...
extension (i.e. if you're using the waitTimeMs
option on an endpoint URI, which is highly encouraged).
enableAssertions
to false
. Please refer to the surefire:test reference for details.
Chapter 59. Krati Copier lienLien copié sur presse-papiers!
Krati Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
krati:[the path of the datastore][?options]
krati:[the path of the datastore][?options]
?option=value&option=value&...
Krati URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
operation
|
CamelKratiPut | *Producer Only*. Specifies the type of operation that will be performed to the datastore. Allowed values are CamelKratiPut, CamelKratiGet, CamelKratiDelete & CamelKratiDeleteAll. |
initialCapacity
|
100 | The inital capcity of the store. |
keySerializer
|
KratiDefaultSerializer | The serializer serializer that will be used to serialize the key. |
valueSerializer
|
KratiDefaultSerializer | The serializer serializer that will be used to serialize the value. |
segmentFactory
|
ChannelSegmentFactory | The segment factory to use. Allowed instance classes: ChannelSegmentFactory,MemorySegmentFactory, MappedSegmentFactory & WriteBufferSegmentFactory. |
hashFunction
|
FnvHashFunction | The hash function to use. Allowed instance classes: FnvHashFunction,Fnv1Hash32,FnvHash64,Fnv1aHash32,Fnv1aHash64, JenkisHashFunction, MurmurHashFunctiom |
Message Headers for datastore Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelKratiOperation
|
The operation to be performed on the datastore. The valid options are
|
CamelKratiKey
|
The key. |
CamelKratiValue
|
The value. |
Usage Samples Copier lienLien copié sur presse-papiers!
Example 1: Putting to the datastore. Copier lienLien copié sur presse-papiers!
from("direct:put").to("krati:target/test/producertest");
from("direct:put").to("krati:target/test/producertest");
<route> <from uri="direct:put"/> <to uri="krati:target/test/producerspringtest"/> </route>
<route>
<from uri="direct:put"/>
<to uri="krati:target/test/producerspringtest"/>
</route>
Example 2: Getting/Reading from a datastore Copier lienLien copié sur presse-papiers!
from("direct:get") .setHeader(KratiConstants.KRATI_OPERATION, constant(KratiConstants.KRATI_OPERATION_GET)) .to("krati:target/test/producertest");
from("direct:get")
.setHeader(KratiConstants.KRATI_OPERATION, constant(KratiConstants.KRATI_OPERATION_GET))
.to("krati:target/test/producertest");
<route> <from uri="direct:get"/> <to uri="krati:target/test/producerspringtest?operation=CamelKratiGet"/> </route>
<route>
<from uri="direct:get"/>
<to uri="krati:target/test/producerspringtest?operation=CamelKratiGet"/>
</route>
Example 3: Consuming from a datastore Copier lienLien copié sur presse-papiers!
from("krati:target/test/consumertest") .to("direct:next");
from("krati:target/test/consumertest")
.to("direct:next");
<route> <from uri="krati:target/test/consumerspringtest"/> <to uri="mock:results"/> </route>
<route>
<from uri="krati:target/test/consumerspringtest"/>
<to uri="mock:results"/>
</route>
Idempotent Repository Copier lienLien copié sur presse-papiers!
from("direct://in").idempotentConsumer(header("messageId"), new KratiIdempotentRepositroy("/tmp/idempotent").to("log://out");
from("direct://in").idempotentConsumer(header("messageId"), new KratiIdempotentRepositroy("/tmp/idempotent").to("log://out");
See also Copier lienLien copié sur presse-papiers!
Chapter 60. Language Copier lienLien copié sur presse-papiers!
Language Copier lienLien copié sur presse-papiers!
language
endpoints where the script is dynamic defined as well.
camel-core
and hence no additional JARs is needed. You only have to include additional Camel components if the language of choice mandates it, such as using Groovy or JavaScript languages.
URI format Copier lienLien copié sur presse-papiers!
language://languageName[:script][?options]
language://languageName[:script][?options]
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Type | Description |
---|---|---|---|
languageName
|
null
|
String
|
The name of the Language to use, such as simple , groovy , javascript etc. This option is mandatory.
|
script
|
null
|
String
|
The script to execute. |
transform
|
true
|
boolean
|
Whether or not the result of the script should be used as the new message body. By setting to false the script is executed but the result of the script is discarded.
|
contentCache
|
true
|
boolean
|
*Camel 2.9:* Whether to cache the script if loaded from a resource. |
Message Headers Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelLanguageScript
|
The script to execute provided in the header. Takes precedence over script configured on the endpoint. |
Examples Copier lienLien copié sur presse-papiers!
String script = URLEncoder.encode("Hello ${body}", "UTF-8"); from("direct:start").to("language:simple:" + script).to("mock:result");
String script = URLEncoder.encode("Hello ${body}", "UTF-8");
from("direct:start").to("language:simple:" + script).to("mock:result");
String script = URLEncoder.encode("${mandatoryBodyAs(String)}", "UTF-8"); from("direct:start").to("language:simple:" + script).to("mock:result");
String script = URLEncoder.encode("${mandatoryBodyAs(String)}", "UTF-8");
from("direct:start").to("language:simple:" + script).to("mock:result");
from("direct:start").to("language:groovy:request.body * 2").to("mock:result");
from("direct:start").to("language:groovy:request.body * 2").to("mock:result");
<foo>
tag.
Object out = producer.requestBodyAndHeader("language:xpath", "<foo>Hello World</foo>", Exchange.LANGUAGE_SCRIPT, "/foo/text()"); assertEquals("Hello World", out);
Object out = producer.requestBodyAndHeader("language:xpath", "<foo>Hello World</foo>", Exchange.LANGUAGE_SCRIPT, "/foo/text()");
assertEquals("Hello World", out);
Loading scripts from resources Copier lienLien copié sur presse-papiers!
Exchange.LANGUAGE_SCRIPT
header. The uri must start with one of the following schemes: file:, classpath:, or http:
from("direct:start") // load the script from the classpath .to("language:simple:classpath:org/apache/camel/component/language/mysimplescript.txt") .to("mock:result");
from("direct:start")
// load the script from the classpath
.to("language:simple:classpath:org/apache/camel/component/language/mysimplescript.txt")
.to("mock:result");
contentCache
option and have the script loaded on each evaluation. For example if the file myscript.txt is changed on disk, then the updated script is used:
from("direct:start") // the script will be loaded on each message, as we disabled cache .to("language:simple:file:target/script/myscript.txt?contentCache=false") .to("mock:result");
from("direct:start")
// the script will be loaded on each message, as we disabled cache
.to("language:simple:file:target/script/myscript.txt?contentCache=false")
.to("mock:result");
- Routing SlipRouting Slip
- Dynamic RouterDynamic Router
Chapter 61. LDAP Copier lienLien copié sur presse-papiers!
LDAP Component Copier lienLien copié sur presse-papiers!
javax.naming
package) to access the server.
URI format Copier lienLien copié sur presse-papiers!
ldap:ldapServerBean[?options]
ldap:ldapServerBean[?options]
ldap
URI cannot appear in the from
at the start of a route.
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
base
|
ou=system
|
The base DN for searches. |
scope
|
subtree
|
Specifies how deeply to search the tree of entries, starting at the base DN. Value can be object , onelevel , or subtree .
|
pageSize
|
No paging used. |
When specified the LDAP module uses paging to retrieve all results (most LDAP Servers throw an exception when trying to retrieve more than 1000 entries in one query). To be able to use this, an LdapContext (subclass of DirContext ) has to be passed in as ldapServerBean (otherwise an exception is thrown)
|
returnedAttributes
|
Depends on LDAP Server (could be all or none) . | Comma-separated list of attributes that should be set in each entry of the result |
Result Copier lienLien copié sur presse-papiers!
ArrayList<javax.naming.directory.SearchResult>
object.
DirContext Copier lienLien copié sur presse-papiers!
ldap:ldapserver
, references a Spring bean with the ID, ldapserver
. The ldapserver
bean may be defined as follows:
DirContext
that connects anonymously to a locally hosted LDAP server.
DirContext
objects are not required to support concurrency by contract. It is therefore important that the directory context is declared with the setting, scope="prototype"
, in the bean
definition or that the context supports concurrency. In the Spring framework, prototype
scoped objects are instantiated each time they are looked up.
Samples Copier lienLien copié sur presse-papiers!
(cn=*)
(cn=*)
Binding using credentials Copier lienLien copié sur presse-papiers!
Chapter 62. List Copier lienLien copié sur presse-papiers!
List Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
list:someName
list:someName
Sample Copier lienLien copié sur presse-papiers!
from("activemq:order.in").to("list:orderReceived").to("bean:processOrder");
from("activemq:order.in").to("list:orderReceived").to("bean:processOrder");
Chapter 63. Log Copier lienLien copié sur presse-papiers!
Log Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
log:loggingCategory[?options]
log:loggingCategory[?options]
?option=value&option=value&...
level
option, as follows:
log:org.apache.camel.example?level=DEBUG
log:org.apache.camel.example?level=DEBUG
Throughput
logger, which is used whenever the groupSize
option is specified.
log
directly in the DSL, but it has a different purpose. Its meant for lightweight and human logs. See more details at section "LogEIP" in "Implementing Enterprise Integration Patterns".
Options Copier lienLien copié sur presse-papiers!
Option | Default | Type | Description |
---|---|---|---|
level
|
INFO
|
String
|
Logging level to use. Possible values: ERROR , WARN , INFO , DEBUG , TRACE , OFF
|
marker
|
null
|
String
|
*Camel 2.9:* An optional Marker name to use. |
groupSize
|
null
|
Integer
|
An integer that specifies a group size for throughput logging. |
groupInterval
|
null
|
Integer
|
Camel 2.6: If specified will group message stats by this time interval (in millis) |
groupDelay
|
0
|
Integer
|
Camel 2.6: Set the initial delay for stats (in millis) |
groupActiveOnly
|
true
|
boolean
|
Camel 2.6: If true, will hide stats when no new messages have been received for a time interval, if false, show stats regardless of message traffic |
Formatting Copier lienLien copié sur presse-papiers!
LogFormatter
to format the log output, where LogFormatter
has the following options:
Option | Default | Description |
---|---|---|
showAll
|
false
|
Quick option for turning all options on (multiline, maxChars has to be manually set if to be used). |
showExchangeId
|
false
|
Show the unique exchange ID. |
showExchangePattern
|
true
|
Camel 2.3: Shows the Message Exchange Pattern (or MEP for short). |
showProperties
|
false
|
Show the exchange properties. |
showHeaders
|
false
|
Show the In message headers. |
showBodyType
|
true
|
Show the In body Java type. |
showBody
|
true
|
Show the In body. |
showOut
|
false
|
If the exchange has an Out message, show the Out message. |
showException
|
false
|
Apache Camel 2.0: If the exchange has an exception, show the exception message (no stack trace). |
showCaughtException
|
false
|
Apache Camel 2.0: If the exchange has a caught exception, show the exception message (no stack trace). A caught exception is stored as a property on the exchange and for instance a doCatch can catch exceptions. See Try Catch Finally.
|
showStackTrace
|
false
|
Apache Camel 2.0: Show the stack trace, if an exchange has an exception. Only effective if one of showAll , showException or showCaughtException are enabled.
|
showFiles
|
false
|
*Camel 2.9:* Whether Camel should show file bodies or not (eg such as java.io.File). |
showFuture
|
false
|
Camel 2.1: Whether Camel should show java.util.concurrent.Future bodies or not. If enabled Camel could potentially wait until the Future task is done. Will by default not wait.
|
showStreams
|
false
|
Camel 2.8: Whether Camel should show stream bodies or not (eg such as java.io.InputStream). Beware if you enable this option then you may not be able later to access the message body as the stream have already been read by this logger. To remedy this you have to use Stream Caching. |
multiline
|
false
|
If true , each piece of information is logged on a new line.
|
maxChars
|
Limits the number of characters logged per line. The default value is 10000 from Camel 2.9 onwards.
|
camelContext.getProperties().put(Exchange.LOG_DEBUG_BODY_STREAMS, true);
camelContext.getProperties().put(Exchange.LOG_DEBUG_BODY_STREAMS, true);
Regular logger sample Copier lienLien copié sur presse-papiers!
DEBUG
level before the order is processed:
from("activemq:orders").to("log:com.mycompany.order?level=DEBUG").to("bean:processOrder");
from("activemq:orders").to("log:com.mycompany.order?level=DEBUG").to("bean:processOrder");
<route> <from uri="activemq:orders"/> <to uri="log:com.mycompany.order?level=DEBUG"/> <to uri="bean:processOrder"/> </route>
<route>
<from uri="activemq:orders"/>
<to uri="log:com.mycompany.order?level=DEBUG"/>
<to uri="bean:processOrder"/>
</route>
Regular logger with formatter sample Copier lienLien copié sur presse-papiers!
INFO
level before the order is processed.
from("activemq:orders"). to("log:com.mycompany.order?showAll=true&multiline=true").to("bean:processOrder");
from("activemq:orders").
to("log:com.mycompany.order?showAll=true&multiline=true").to("bean:processOrder");
Throughput logger with groupSize sample Copier lienLien copié sur presse-papiers!
DEBUG
level grouped by 10 messages.
from("activemq:orders"). to("log:com.mycompany.order?level=DEBUG&groupSize=10").to("bean:processOrder");
from("activemq:orders").
to("log:com.mycompany.order?level=DEBUG&groupSize=10").to("bean:processOrder");
Throughput logger with groupInterval sample Copier lienLien copié sur presse-papiers!
from("activemq:orders") .to("log:com.mycompany.order?level=DEBUG&groupInterval=10000&groupDelay=60000&groupActiveOnly=false") .to("bean:processOrder");
from("activemq:orders")
.to("log:com.mycompany.order?level=DEBUG&groupInterval=10000&groupDelay=60000&groupActiveOnly=false")
.to("bean:processOrder");
"Received: 1000 new messages, with total 2000 so far. Last group took: 10000 millis which is: 100 messages per second. average: 100"
"Received: 1000 new messages, with total 2000 so far. Last group took: 10000 millis which is: 100 messages per second. average: 100"
Chapter 64. Lucene Copier lienLien copié sur presse-papiers!
Lucene (Indexer and Search) Component Copier lienLien copié sur presse-papiers!
- builds a searchable index of documents when payloads are sent to the Lucene Endpoint
- facilitates performing of indexed searches in Apache Camel
URI format Copier lienLien copié sur presse-papiers!
lucene:searcherName:insert[?options] lucene:searcherName:query[?options]
lucene:searcherName:insert[?options]
lucene:searcherName:query[?options]
?option=value&option=value&...
Insert Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
analyzer
|
StandardAnalyzer
|
An Analyzer builds TokenStreams, which analyze text. It thus represents a policy for extracting index terms from text. The value for analyzer can be any class that extends the abstract class org.apache.lucene.analysis.Analyzer. Lucene also offers a rich set of analyzers out of the box |
indexDir
|
./indexDirectory
|
A file system directory in which index files are created upon analysis of the document by the specified analyzer |
srcDir
|
null
|
An optional directory containing files to be used to be analyzed and added to the index at producer startup. |
Query Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
analyzer
|
StandardAnalyzer
|
An Analyzer builds TokenStreams, which analyze text. It thus represents a policy for extracting index terms from text. The value for analyzer can be any class that extends the abstract class org.apache.lucene.analysis.Analyzer. Lucene also offers a rich set of analyzers out of the box |
indexDir
|
./indexDirectory
|
A file system directory in which index files are created upon analysis of the document by the specified analyzer |
maxHits
|
10
|
An integer value that limits the result set of the search operation |
Message Headers Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
QUERY
|
The Lucene Query to performed on the index. The query may include wildcards and phrases |
Lucene Producers Copier lienLien copié sur presse-papiers!
- insert - The insert producer builds a searchable index by analyzing the body in incoming exchanges and associating it with a token ("content").
- query - The query producer performs searches on a pre-created index. The query uses the searchable index to perform score & relevance based searches. Queries are sent via the incoming exchange contains a header property name called 'QUERY'. The value of the header property 'QUERY' is a Lucene Query. For more details on how to create Lucene Queries check out http://lucene.apache.org/java/3_0_0/queryparsersyntax.html
Lucene Processor Copier lienLien copié sur presse-papiers!
Example 1: Creating a Lucene index Copier lienLien copié sur presse-papiers!
Example 2: Loading properties into the JNDI registry in the Camel Context Copier lienLien copié sur presse-papiers!
Example 2: Performing searches using a Query Producer Copier lienLien copié sur presse-papiers!
Example 3: Performing searches using a Query Processor Copier lienLien copié sur presse-papiers!
Chapter 65. Mail Copier lienLien copié sur presse-papiers!
Mail Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
.jar
(v1.6) has a bug when polling mails with attachments. It cannot correctly identify the Content-Type
. So, if you attach a .jpeg
file to a mail and you poll it, the Content-Type
is resolved as text/plain
and not as image/jpeg
. For that reason, we have added an org.apache.camel.component.ContentTypeResolver
SPI interface which enables you to provide your own implementation and fix this bug by returning the correct Mime type based on the file name. So if the file name ends with jpeg/jpg
, you can return image/jpeg
.
MailComponent
instance or on the MailEndpoint
instance.
URI format Copier lienLien copié sur presse-papiers!
smtp://[username@]host[:port][?options] pop3://[username@]host[:port][?options] imap://[username@]host[:port][?options]
smtp://[username@]host[:port][?options]
pop3://[username@]host[:port][?options]
imap://[username@]host[:port][?options]
s
to the scheme:
smtps://[username@]host[:port][?options] pop3s://[username@]host[:port][?options] imaps://[username@]host[:port][?options]
smtps://[username@]host[:port][?options]
pop3s://[username@]host[:port][?options]
imaps://[username@]host[:port][?options]
?option=value&option=value&...
Sample endpoints Copier lienLien copié sur presse-papiers!
smtp://[username@]host[:port][?password=somepwd]
smtp://[username@]host[:port][?password=somepwd]
smtp://host[:port]?password=somepwd&username=someuser
smtp://host[:port]?password=somepwd&username=someuser
smtp://mycompany.mailserver:30?password=tiger&username=scott
smtp://mycompany.mailserver:30?password=tiger&username=scott
Default ports Copier lienLien copié sur presse-papiers!
Protocol | Default Port Number |
---|---|
SMTP
|
25
|
SMTPS
|
465
|
POP3
|
110
|
POP3S
|
995
|
IMAP
|
143
|
IMAPS
|
993
|
Options Copier lienLien copié sur presse-papiers!
Property | Default | Description |
---|---|---|
host
|
The host name or IP address to connect to. | |
port
|
See DefaultPorts | The TCP port number to connect on. |
username
|
The user name on the email server. | |
password
|
null
|
The password on the email server. |
ignoreUriScheme
|
false
|
If false , Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.)
|
defaultEncoding
|
null
|
The default encoding to use for Mime Messages. |
contentType
|
text/plain
|
The mail message content type. Use text/html for HTML mails.
|
folderName
|
INBOX
|
The folder to poll. |
destination
|
username@host
|
*@deprecated* Use the to option instead. The TO recipients (receivers of the email).
|
to
|
username@host
|
The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma. |
replyTo
|
alias@host
|
As of Camel 2.8.4, 2.9.1\+, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma. |
CC
|
null
|
The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma. |
BCC
|
null
|
The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma. |
from
|
camel@localhost
|
The FROM email address. |
subject
|
As of Camel 2.3, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option. | |
delete
|
false
|
Deletes the messages after they have been processed. This is done by setting the DELETED flag on the mail message. If false , the SEEN flag is set instead. As of Camel 2.10 you can override this configuration option by setting a header with the key delete to determine if the mail should be deleted or not.
|
unseen
|
true
|
It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of true will filter to only unseen messages. POP3 does not support the SEEN flag, so this option is not supported in POP3; use IMAP instead.
|
copyTo
|
null
|
*Camel 2.10:* Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this configuration value, with a header with the key copyTo , allowing you to copy messages to folder names configured at runtime.
|
fetchSize
|
\-1
|
Sets the maximum number of messages to consume during a poll. This can be used to avoid overloading a mail server, if a mailbox folder contains a lot of messages. Default value of \-1 means no fetch size and all messages will be consumed. Setting the value to 0 is a special corner case, where Camel will not consume any messages at all.
|
alternativeBodyHeader
|
CamelMailAlternativeBody
|
Specifies the key to an IN message header that contains an alternative email body. For example, if you send emails in text/html format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header.
|
debugMode
|
false
|
Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to System.out by default.
|
connectionTimeout
|
30000
|
The connection timeout in milliseconds. Default is 30 seconds. |
consumer.initialDelay
|
1000
|
Milliseconds before the polling starts. |
consumer.delay
|
60000
|
Camel will poll the mailbox only once a minute by default to avoid overloading the mail server. |
consumer.useFixedDelay
|
false
|
Set to true to use a fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
|
disconnect
|
false
|
*Camel 2.8.3/2.9:* Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll. |
mail.XXX
|
null
|
Set any additional java mail properties. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: mail.pop3.forgettopheaders=true . You can set multiple such options, for example: mail.pop3.forgettopheaders=true&mail.mime.encodefilename=true .
|
mapMailMessage
|
true
|
*Camel 2.8:* Specifies whether Camel should map the received mail message to Camel body/headers. If set to true, the body of the mail message is mapped to the body of the Camel IN message and the mail headers are mapped to IN headers. If this option is set to false then the IN message contains a raw javax.mail.Message . You can retrieve this raw message by calling exchange.getIn().getBody(javax.mail.Message.class) .
|
maxMessagesPerPoll
|
0
|
Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when the server starts up. Set a value of 0 or negative to disable this option. |
javaMailSender
|
null
|
Specifies a pluggable org.springframework.mail.javamail.JavaMailSender instance in order to use a custom email implementation. If none provided, Camel uses the default org.springframework.mail.javamail.JavaMailSenderImpl .
|
ignoreUnsupportedCharset
|
false
|
Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then charset=XXX (where XXX represents the unsupported charset) is removed from the content-type and it relies on the platform default instead.
|
sslContextParameters
|
null
|
*Camel 2.10:* Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
|
SSL support Copier lienLien copié sur presse-papiers!
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
Programmatic configuration of the endpoint Copier lienLien copié sur presse-papiers!
Spring DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
Configuring JavaMail Directly Copier lienLien copié sur presse-papiers!
SSLNOTES.txt
in JavaMail for details).
Mail Message Content Copier lienLien copié sur presse-papiers!
String.class
.
from("direct:a").setHeader("subject", constant(subject)).to("smtp://james2@localhost");
from("direct:a").setHeader("subject", constant(subject)).to("smtp://james2@localhost");
To
:
Headers take precedence over pre-configured recipients Copier lienLien copié sur presse-papiers!
davsclaus@apache.org
, because it takes precedence over the pre-configured recipient, info@mycompany.com
. Any CC
and BCC
settings in the endpoint URI are also ignored and those recipients will not receive any mail. The choice between headers and pre-configured settings is all or nothing: the mail component either takes the recipients exclusively from the headers or exclusively from the pre-configured settings. It is not possible to mix and match headers and pre-configured settings.
Map<String, Object> headers = new HashMap<String, Object>(); headers.put("to", "davsclaus@apache.org"); template.sendBodyAndHeaders("smtp://admin@localhost?to=info@mycompany.com", "Hello World", headers);
Map<String, Object> headers = new HashMap<String, Object>();
headers.put("to", "davsclaus@apache.org");
template.sendBodyAndHeaders("smtp://admin@localhost?to=info@mycompany.com", "Hello World", headers);
Multiple recipients for easier configuration Copier lienLien copié sur presse-papiers!
Map<String, Object> headers = new HashMap<String, Object>(); headers.put("to", "davsclaus@apache.org ; jstrachan@apache.org ; ningjiang@apache.org");
Map<String, Object> headers = new HashMap<String, Object>();
headers.put("to", "davsclaus@apache.org ; jstrachan@apache.org ; ningjiang@apache.org");
;
, as the separator character.
Setting sender name and email Copier lienLien copié sur presse-papiers!
name <email>
, to include both the name and the email address of the recipient.
Map headers = new HashMap(); map.put("To", "Claus Ibsen <davsclaus@apache.org>"); map.put("From", "James Strachan <jstrachan@apache.org>"); map.put("Subject", "Camel is cool");
Map headers = new HashMap();
map.put("To", "Claus Ibsen <davsclaus@apache.org>");
map.put("From", "James Strachan <jstrachan@apache.org>");
map.put("Subject", "Camel is cool");
SUN JavaMail Copier lienLien copié sur presse-papiers!
- And generally about the MAIL Flags
Samples Copier lienLien copié sur presse-papiers!
admin
account on mymailserver.com
.
from("jms://queue:subscription").to("smtp://admin@mymailserver.com?password=secret");
from("jms://queue:subscription").to("smtp://admin@mymailserver.com?password=secret");
consumer
option for setting the poll interval, consumer.delay
, as 60000 milliseconds = 60 seconds.
from("imap://admin@mymailserver.com password=secret&unseen=true&consumer.delay=60000") .to("seda://mails");
from("imap://admin@mymailserver.com
password=secret&unseen=true&consumer.delay=60000")
.to("seda://mails");
Sending mail with attachment sample Copier lienLien copié sur presse-papiers!
SSL sample Copier lienLien copié sur presse-papiers!
from("imaps://imap.gmail.com?username=YOUR_USERNAME@gmail.com&password=YOUR_PASSWORD" + "&delete=false&unseen=true&consumer.delay=60000").to("log:newmail");
from("imaps://imap.gmail.com?username=YOUR_USERNAME@gmail.com&password=YOUR_PASSWORD"
+ "&delete=false&unseen=true&consumer.delay=60000").to("log:newmail");
newmail
logger category. Running the sample with DEBUG
logging enabled, we can monitor the progress in the logs:
Consuming mails with attachment sample Copier lienLien copié sur presse-papiers!
from("imaps://imap.gmail.com?username=YOUR_USERNAME@gmail.com&password=YOUR_PASSWORD" + "&delete=false&unseen=true&consumer.delay=60000").process(new MyMailProcessor());
from("imaps://imap.gmail.com?username=YOUR_USERNAME@gmail.com&password=YOUR_PASSWORD"
+ "&delete=false&unseen=true&consumer.delay=60000").process(new MyMailProcessor());
javax.activation.DataHandler
so you can handle the attachments using standard API.
How to split a mail message with attachments Copier lienLien copié sur presse-papiers!
camel-mail
component. The code is in the class: org.apache.camel.component.mail.SplitAttachmentsExpression
, which you can find the source code here
<split> <method beanType="org.apache.camel.component.mail.SplitAttachmentsExpression"/> <to uri="mock:split"/> </split>
<split>
<method beanType="org.apache.camel.component.mail.SplitAttachmentsExpression"/>
<to uri="mock:split"/>
</split>
Chapter 66. Master Component Copier lienLien copié sur presse-papiers!
Abstract
master:ClusterID:
.
Dependencies Copier lienLien copié sur presse-papiers!
fabric-camel
feature is installed. If necessary, you can install it using the following console command:
karaf@root> features:install fabric-camel
karaf@root> features:install fabric-camel
fabric-camel
feature is installed by including it in your feature definition. For example:
URI format Copier lienLien copié sur presse-papiers!
master:ClusterID:PublishedURI[?Options]
master:ClusterID:PublishedURI[?Options]
PublishedURI
, is published in the fabric registry and associated with the ClusterId
cluster.
URI options Copier lienLien copié sur presse-papiers!
- Server-only options—options that are applicable only to the server are applied to the server endpoint (consumer endpoint) at run time.
- Client-only options—options that are applicable only to the client are applied to the client endpoint (producer endpoint) at run time.
- Common options—options common to the client and the server are applied to both.
Master-slave failover cluster Copier lienLien copié sur presse-papiers!
Figure 66.1. Failover Cluster with Master Endpoints
master:FD:jetty:http://0.0.0.0:9090
and master:FD:jetty:http://0.0.0.0:9191
. When the servers are created, they compete to grab a lock on the FD
entry in the fabric registry. Whichever server manages to get the lock (in this example, the server listening on port 9090
) becomes the master, registering its URI under the cluster ID, FD
, and activating its route. The other servers remain slaves: they are not able to register their URIs under the FD
cluster ID, their routes do not get activated, and they continue to try the lock on the FD
registry entry, in case the master server should fail.
FD
, to find the master's endpoint URI, and then connects to the master server.
- Now that the master has died, the lock is free again. One of the slaves will succeed in grabbing the lock and become the new master.
- The new master registers its URI under the
FD
cluster ID, replacing the URI of the old master. - The auto-reconnect capability of the Fabric endpoint in the client is activated. The client detects that the master has died, goes back to the fabric registry to obtain the URI of the new master, and then connects to the new master.
Creating a failover cluster Copier lienLien copié sur presse-papiers!
Example 66.1. Server Template for a Failover Cluster
org.fusesource.fabric.zookeeper.IZKClient
OSGi service is created using the reference
element. This reference is needed, because the Master component implicitly looks for an IZKClient
object in the bean registry and uses this object to connect to the underlying fabric.
from
command that specifies a Master endpoint URI. The Master endpoint registers the given Jetty URI under the FailoverDemo
cluster ID, which effectively means that the server joins the FailoverDemo
failover cluster.
masterCamel
persistent ID. A persistent ID in the OSGi Config Admin service identifies a collection of related property settings. After initializing the property placeholder, you can access any property values from the masterCamel
persistent ID using the syntax, {{PropName}}
.
{{portNumber}}
, at run time. At deploy time, you can specify the value of the portName
property. For example, if using a custom feature, you could specify the property in the feature definition (see Add OSGi configurations to the feature). Alternatively, you can specify configuration properties when defining deployment profiles in the Fuse Management Console.
Looking up an endpoint URI Copier lienLien copié sur presse-papiers!
fabric:ClusterID
. This syntax is used in a producer endpoint (for example, an endpoint that appears in a to
DSL command).
FailoverDemo
, in the fabric registry.
Example 66.2. Looking up a URI
org.fusesource.fabric.zookeeper.IZKClient
OSGi service, which the Fabric component uses to connect to the underlying fabric.
src/main/resources/OSGI-INF/blueprint
directory of a Maven project.
OSGi bundle plug-in configuration Copier lienLien copié sur presse-papiers!
Import-Package
bundle header must be configured to import the following Java packages:
org.fusesource.fabric.zookeeper.spring org.fusesource.fabric.zookeeper
org.fusesource.fabric.zookeeper.spring
org.fusesource.fabric.zookeeper
Example 66.3. Maven Bundle Plug-In Configuration
Chapter 67. MINA Copier lienLien copié sur presse-papiers!
MINA Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
mina:tcp://hostname[:port][?options] mina:udp://hostname[:port][?options] mina:vm://hostname[:port][?options]
mina:tcp://hostname[:port][?options]
mina:udp://hostname[:port][?options]
mina:vm://hostname[:port][?options]
textline
flag is used to determine if text line based codec or object serialization should be used instead. By default the object serialization is used.
ByteBuffer
based codec.
camel-mina
only supports marshalling the body content—essage headers and exchange properties are not sent. However, the option, transferExchange, does allow you to transfer the exchange itself over the wire. See options below.
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Option | Default Value | Description |
---|---|---|
codec
|
null
|
You can refer to a named ProtocolCodecFactory instance in your Registry such as your Spring ApplicationContext , which is then used for the marshalling.
|
codec
|
null
|
Apache Camel 2.0: You must use the # notation to look up your codec in the Registry. For example, use #myCodec to look up a bean with the id value, myCodec .
|
disconnect
|
false
|
Camel 2.3: Whether or not to disconnect(close) from Mina session right after use. Can be used for both consumer and producer. |
textline
|
false
|
Only used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not specified or the value is false , then Object Serialization is assumed over TCP.
|
textlineDelimiter
|
DEFAULT
|
Only used for TCP and if textline=true. Sets the text line delimiter to use. Possible values are: DEFAULT , AUTO , WINDOWS , UNIX or MAC . If none provided, Apache Camel will use DEFAULT . This delimiter is used to mark the end of text.
|
sync
|
true
|
You can configure the exchange pattern to be either InOnly (default) or InOut. Setting sync=true means a synchronous exchange (InOut), where the client can read the response from MINA (the exchange Out message). The default value has changed in Apache Camel 1.5 to true . In older releases, the default value is false .
|
lazySessionCreation
|
See description |
Sessions can be lazily created to avoid exceptions, if the remote server is not up and running when the Apache Camel producer is started. From Apache Camel 2.0 onwards, the default is true . In Apache Camel 1.x, the default is false .
|
timeout
|
3000
|
You can configure the timeout that specifies how long to wait for a response from a remote server. The timeout unit is in milliseconds, so 60000 is 60 seconds. The timeout is only used for Mina producer. |
encoding
|
JVM Default | You can configure the encoding (a charset name) to use for the TCP textline codec and the UDP protocol. If not provided, Apache Camel will use the JVM default Charset. |
transferExchange
|
false
|
Only used for TCP. You can transfer the exchange over the wire instead of just the body. The following fields are transferred: In body, Out body, fault body, In headers, Out headers, fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Apache Camel will exclude any non-serializable objects and log it at WARN level.
|
minaLogger
|
false
|
You can enable the Apache MINA logging filter. Apache MINA uses slf4j logging at INFO level to log all input and output.
|
filters
|
null
|
As of 2.0, you can set a list of Mina IoFilters to register. The
filters value must be one of the following:
|
encoderMaxLineLength
|
-1
|
As of 2.1, you can set the textline protocol encoder max line length. By default the default value of Mina itself is used which are Integer.MAX_VALUE .
|
decoderMaxLineLength
|
-1
|
As of 2.1, you can set the textline protocol decoder max line length. By default the default value of Mina itself is used which are 1024. |
allowDefaultCodec
|
true
|
The mina component installs a default codec if both, codec is null and textline is false . Setting allowDefaultCodec to false prevents the mina component from installing a default codec as the first element in the filter chain. This is useful in scenarios where another filter must be the first in the filter chain, like the SSL filter.
|
disconnectOnNoReply
|
true
|
Camel 2.3: If sync is enabled then this option dictates MinaConsumer if it should disconnect where there is no reply to send back. |
noReplyLogLevel
|
WARN
|
Camel 2.3: If sync is enabled this option dictates MinaConsumer which logging level to use when logging a there is no reply to send back. Values are: FATAL, ERROR, INFO, DEBUG, OFF .
|
Using a custom codec Copier lienLien copié sur presse-papiers!
camel-mina
, you should register your codec in the Registry; for example, by creating a bean in the Spring XML file. Then use the codec
option to specify the bean ID of your codec. See HL7 that has a custom codec.
Sample with sync=false Copier lienLien copié sur presse-papiers!
from("mina:tcp://localhost:6200?textline=true&sync=false").to("mock:result");
from("mina:tcp://localhost:6200?textline=true&sync=false").to("mock:result");
Sample with sync=true Copier lienLien copié sur presse-papiers!
sync
option to true
on the consumer.
template.requestBody()
method. As we know the response is a String
, we cast it to String
and can assert that the response is, in fact, something we have dynamically set in our processor code logic.
String response = (String)template.requestBody("mina:tcp://localhost:6201?textline=true&sync=true", "World"); assertEquals("Bye World", response);
String response = (String)template.requestBody("mina:tcp://localhost:6201?textline=true&sync=true", "World");
assertEquals("Bye World", response);
Sample with Spring DSL Copier lienLien copié sur presse-papiers!
<route> <from uri="mina:tcp://localhost:5555?textline=true"/> <to uri="bean:myTCPOrderHandler"/> </route>
<route>
<from uri="mina:tcp://localhost:5555?textline=true"/>
<to uri="bean:myTCPOrderHandler"/>
</route>
myTCPOrderHandler
, handle the request and return a reply. For instance, the handler bean could be implemented as follows:
public String handleOrder(String payload) { ... return "Order: OK" }
public String handleOrder(String payload) {
...
return "Order: OK"
}
Configuring Mina endpoints using Spring bean style Copier lienLien copié sur presse-papiers!
MinaComponent
as a Spring factory bean to configure this for us. If you really need to configure this yourself, there are setters on the MinaEndpoint
to set these when needed.
<route> <!-- here we route from or mina endpoint we have defined above --> <from ref="myMinaEndpoint"/> <to uri="mock:result"/> </route>
<route>
<!-- here we route from or mina endpoint we have defined above -->
<from ref="myMinaEndpoint"/>
<to uri="mock:result"/>
</route>
Closing Session When Complete Copier lienLien copié sur presse-papiers!
CamelMinaCloseSessionWhenComplete
set to a boolean true
value.
bye
message back to the client:
Get the IoSession for message Copier lienLien copié sur presse-papiers!
MinaEndpoint.HEADER_MINA_IOSESSION
, and also get the local host address with the key MinaEndpoint.HEADER_LOCAL_ADDRESS
and remote host address with the key MinaEndpoint.HEADER_REMOTE_ADDRESS
.
Configuring Mina filters Copier lienLien copié sur presse-papiers!
SslFilter
. You can also implement some customized filters. Please note that codec
and logger
are also implemented as Mina filters of type, IoFilter
. Any filters you may define are appended to the end of the filter chain; that is, after codec
and logger
.
220
message with a greeting (220 Welcome to Pure-FTPd
). If you don't drop the message, your request-reply scheme will be broken.
Chapter 68. Mock Copier lienLien copié sur presse-papiers!
Mock Component Copier lienLien copié sur presse-papiers!
- The correct number of messages are received on each endpoint,
- The correct payloads are received, in the right order,
- Messages arrive on an endpoint in order, using some Expression to create an order testing function,
- Messages arrive match some kind of Predicate such as that specific headers have certain values, or that parts of the messages match some predicate, such as by evaluating an XPath or XQuery Expression.
retainFirst
, and retainLast
that can be used to limit the number of messages the Mock endpoints keep in memory.
URI format Copier lienLien copié sur presse-papiers!
mock:someName[?options]
mock:someName[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
reportGroup
|
null
|
A size to use a throughput logger for reporting |
Simple Example Copier lienLien copié sur presse-papiers!
assertIsSatisfied()
is invoked. This can be configured by setting the setResultWaitTime(millis)
method.
Using assertPeriod Copier lienLien copié sur presse-papiers!
assertIsSatisfied
method. That means if a new message arrives on the mock endpoint, just a bit later, that arrival will not affect the outcome of the assertion. Suppose you do want to test that no new messages arrives after a period thereafter, then you can do that by setting the setAssertPeriod
method, for example:
Setting expectations Copier lienLien copié sur presse-papiers!
Method | Description |
---|---|
expectedMessageCount(int) | To define the expected message count on the endpoint. |
expectedMinimumMessageCount(int) | To define the minimum number of expected messages on the endpoint. |
expectedBodiesReceived(...) | To define the expected bodies that should be received (in order). |
expectedHeaderReceived(...) | To define the expected header that should be received |
expectsAscending(Expression) | To add an expectation that messages are received in order, using the given Expression to compare messages. |
expectsDescending(Expression) | To add an expectation that messages are received in order, using the given Expression to compare messages. |
expectsNoDuplicates(Expression) |
To add an expectation that no duplicate messages are received; using an Expression to calculate a unique identifier for each message. This could be something like the JMSMessageID if using JMS, or some unique reference number within the message.
|
resultEndpoint.expectedBodiesReceived("firstMessageBody", "secondMessageBody", "thirdMessageBody");
resultEndpoint.expectedBodiesReceived("firstMessageBody", "secondMessageBody", "thirdMessageBody");
Adding expectations to specific messages Copier lienLien copié sur presse-papiers!
java.util.List
), you can use the following code:
resultEndpoint.message(0).header("foo").isEqualTo("bar");
resultEndpoint.message(0).header("foo").isEqualTo("bar");
Mocking existing endpoints Copier lienLien copié sur presse-papiers!
adviceWith
feature in Camel to mock all the endpoints in a given route from your unit test, as shown below:
mock:<endpoint>
, for example mock:direct:foo
. Camel logs at INFO
level the endpoints being mocked:
INFO Adviced endpoint [direct://foo] with mock endpoint [mock:direct:foo]
INFO Adviced endpoint [direct://foo] with mock endpoint [mock:direct:foo]
log
endpoints you do as shown:
Mocking existing endpoints using the camel-test component Copier lienLien copié sur presse-papiers!
adviceWith
to instruct Camel to mock endpoints, you can easily enable this behavior when using the camel-test
Test Kit. The same route can be tested as follows. Notice that we return "*"
from the isMockEndpoints
method, which tells Camel to mock all endpoints. If you only want to mock all log
endpoints you can return "log*"
instead.
Mocking existing endpoints with XML DSL Copier lienLien copié sur presse-papiers!
camel-test
component for unit testing (as shown above) you can use a different approach when using XML files for routes. The solution is to create a new XML file used by the unit test and then include the intended XML file which has the route you want to test.
camel-route.xml
file:
camel-route.xml
file and define a spring bean with the class org.apache.camel.impl.InterceptSendToMockEndpointStrategy
which tells Camel to mock all endpoints:
<!-- the Camel route is defined in another XML file --> <import resource="camel-route.xml"/> <!-- bean which enables mocking all endpoints --> <bean id="mockAllEndpoints" class="org.apache.camel.impl.InterceptSendToMockEndpointStrategy"/>
<!-- the Camel route is defined in another XML file -->
<import resource="camel-route.xml"/>
<!-- bean which enables mocking all endpoints -->
<bean id="mockAllEndpoints" class="org.apache.camel.impl.InterceptSendToMockEndpointStrategy"/>
test-camel-route.xml
) instead of camel-route.xml
.
<bean id="mockAllEndpoints" class="org.apache.camel.impl.InterceptSendToMockEndpointStrategy"> <constructor-arg index="0" value="log*"/> </bean>
<bean id="mockAllEndpoints" class="org.apache.camel.impl.InterceptSendToMockEndpointStrategy">
<constructor-arg index="0" value="log*"/>
</bean>
Mocking endpoints and skip sending to original endpoint Copier lienLien copié sur presse-papiers!
mockEndpointsAndSkip
method using AdviceWith or the Test Kit. The example below will skip sending to the two endpoints "direct:foo"
, and "direct:bar"
.
Limiting the number of messages to keep Copier lienLien copié sur presse-papiers!
retainFirst
and retainLast
that can be used to specify to only keep N'th of the first and/or last Exchanges.
getExchanges()
and getReceivedExchanges()
methods on the MockEndpoint
will return only the retained copies of the Exchanges. So in the example above, the list will contain 10 Exchanges; the first five, and the last five. The retainFirst
and retainLast
options also have limitations on which expectation methods you can use. For example the expectedXXX methods that work on message bodies, headers, etc. will only operate on the retained messages. In the example above they can test only the expectations on the 10 retained messages.
Testing with arrival times Copier lienLien copié sur presse-papiers!
Date time = exchange.getProperty(Exchange.RECEIVED_TIMESTAMP, Date.class);
Date time = exchange.getProperty(Exchange.RECEIVED_TIMESTAMP, Date.class);
arrives
DSL on the Mock endpoint.
mock.message(0).arrives().noLaterThan(2).seconds().beforeNext();
mock.message(0).arrives().noLaterThan(2).seconds().beforeNext();
mock.message(1).arrives().noLaterThan(2).seconds().afterPrevious();
mock.message(1).arrives().noLaterThan(2).seconds().afterPrevious();
mock.message(1).arrives().between(1, 4).seconds().afterPrevious();
mock.message(1).arrives().between(1, 4).seconds().afterPrevious();
mock.allMessages().arrives().noLaterThan(1).seconds().beforeNext();
mock.allMessages().arrives().noLaterThan(1).seconds().beforeNext();
seconds
as the time unit, but Camel offers milliseconds
, and minutes
as well.
Chapter 69. MongoDB Copier lienLien copié sur presse-papiers!
Camel MongoDB component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
mongodb:connectionBean?database=databaseName&collection=collectionName&operation=operationName[&moreOptions...]
mongodb:connectionBean?database=databaseName&collection=collectionName&operation=operationName[&moreOptions...]
Endpoint options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description | Producer | Tailable Cursor Consumer |
---|---|---|---|---|
database
|
none |
*Required.* The name of the database to which this endpoint will be bound. All operations will be executed against this database unless dynamicity is enabled and the CamelMongoDbDatabase header is set.
|
(/) | (/) |
collection
|
none |
*Required.* The name of the collection (within the specified database) to which this endpoint will be bound. ll operations will be executed against this database unless dynamicity is enabled and the CamelMongoDbDatabase header is set.
|
(/) | (/) |
operation
|
none |
*Required for producers.* The id of the operation this endpoint will execute. Pick from the following:
|
(/) | |
createCollection
|
true |
Determines whether the collection will be automatically created in the MongoDB database during endpoint initialisation if it doesn't exist already. If this option is false and the collection doesn't exist, an initialisation exception will be thrown.
|
(/) | |
invokeGetLastError
|
false (behaviour may be inherited from connections WriteConcern) |
Instructs the MongoDB Java driver to invoke getLastError() after every call. Default behaviour in version 2.7.2 of the MongoDB Java driver is that only network errors will cause the operation to fail, because the actual operation is executed asynchronously in the MongoDB server without holding up the client - to increase performance. The client can obtain the real result of the operation by explicitly invoking getLastError() on the WriteResult object returned or by setting the appropriate WriteConcern . If the backend operation has not finished yet, the client will block until the result is available. Setting this option to true will make the endpoint behave synchronously and return an Exception if the underlying operation failed.
|
(/) | |
writeConcern
|
none (driver's default) |
Set a WriteConcern on the operation out of MongoDB's parameterised values. See WriteConcern.valueOf(String).
|
(/) | |
writeConcernRef
|
none |
Sets a custom WriteConcern that exists in the Registry. Specify the bean name.
|
(/) | |
readPreference
|
none |
Sets a ReadPreference on the connection. Accepted values: the name of any inner subclass of ReadPreference. For example: PrimaryReadPreference , SecondaryReadPreference , TaggedReadPreference .
|
(/) | |
dynamicity
|
false |
If set to true, the endpoint will inspect the CamelMongoDbDatabase and CamelMongoDbCollection headers of the incoming message, and if any of them exists, the target collection and/or database will be overridden for that particular operation. Set to false by default to avoid triggering the lookup on every Exchange if the feature is not desired.
|
(/) | |
persistentTailTracking
|
false | Enables or disables persistent tail tracking for Tailable Cursor consumers. See below for more information. | (/) | |
persistentId
|
none | *Required if persistent tail tracking is enabled.* The id of this persistent tail tracker, to separate its records from the rest on the tail-tracking collection. | (/) | |
tailTrackingIncreasingField
|
none | *Required if persistent tail tracking is enabled.* Correlation field in the incoming record which is of increasing nature and will be used to position the tailing cursor every time it is generated. The cursor will be (re)created with a query of type: tailTrackIncreasingField > lastValue (where lastValue is possibly recovered from persistent tail tracking). Can be of type Integer, Date, String, etc. NOTE: No support for dot notation at the current time, so the field should be at the top level of the document. | (/) | |
cursorRegenerationDelay
|
1000ms | Establishes how long the endpoint will wait to regenerate the cursor after it has been killed by the MongoDB server (normal behaviour). | (/) | |
tailTrackDb
|
same as endpoint's | Database on which the persistent tail tracker will store its runtime information. | (/) | |
tailTrackCollection
|
camelTailTracking | Collection on which the persistent tail tracker will store its runtime information. | (/) | |
tailTrackField
|
lastTrackingValue | Field in which the persistent tail tracker will store the last tracked value. | (/) |
MongoDB operations - producer endpoints Copier lienLien copié sur presse-papiers!
Query operations Copier lienLien copié sur presse-papiers!
findById Copier lienLien copié sur presse-papiers!
from("direct:findById") .to("mongodb:myDb?database=flights&collection=tickets&operation&operation=findById") .to("mock:resultFindById");
from("direct:findById")
.to("mongodb:myDb?database=flights&collection=tickets&operation&operation=findById")
.to("mock:resultFindById");
findOneByQuery Copier lienLien copié sur presse-papiers!
DBObject
or convertible to DBObject
. It can be a JSON String or a Hashmap. See Type conversions for more info.
from("direct:findOneByQuery") .to("mongodb:myDb?database=flights&collection=tickets&operation&operation=findOneByQuery") .to("mock:resultFindOneByQuery");
from("direct:findOneByQuery")
.to("mongodb:myDb?database=flights&collection=tickets&operation&operation=findOneByQuery")
.to("mock:resultFindOneByQuery");
from("direct:findOneByQuery") .setBody().constant("{ \"name\": \"Raul Kripalani\" }") .to("mongodb:myDb?database=flights&collection=tickets&operation&operation=findOneByQuery") .to("mock:resultFindOneByQuery");
from("direct:findOneByQuery")
.setBody().constant("{ \"name\": \"Raul Kripalani\" }")
.to("mongodb:myDb?database=flights&collection=tickets&operation&operation=findOneByQuery")
.to("mock:resultFindOneByQuery");
findAll Copier lienLien copié sur presse-papiers!
findAll
operation returns all documents matching a query, or none at all, in which case all documents contained in the collection are returned. The query object is extracted from the IN message body, i.e. it should be of type DBObject
or convertible to DBObject
. It can be a JSON String or a Hashmap. See Type conversions for more info.
from("direct:findAll") .to("mongodb:myDb?database=flights&collection=tickets&operation=findAll") .to("mock:resultFindAll");
from("direct:findAll")
.to("mongodb:myDb?database=flights&collection=tickets&operation=findAll")
.to("mock:resultFindAll");
from("direct:findAll") .setBody().constant("{ \"name\": \"Raul Kripalani\" }") .to("mongodb:myDb?database=flights&collection=tickets&operation=findAll") .to("mock:resultFindAll");
from("direct:findAll")
.setBody().constant("{ \"name\": \"Raul Kripalani\" }")
.to("mongodb:myDb?database=flights&collection=tickets&operation=findAll")
.to("mock:resultFindAll");
Header key | Quick constant | Description (extracted from MongoDB API doc) | Expected type |
---|---|---|---|
CamelMongoDbNumToSkip
|
MongoDbConstants.NUM_TO_SKIP
|
Discards a given number of elements at the beginning of the cursor. | int/Integer |
CamelMongoDbLimit
|
MongoDbConstants.LIMIT
|
Limits the number of elements returned. | int/Integer |
CamelMongoDbBatchSize
|
MongoDbConstants.BATCH_SIZE
|
Limits the number of elements returned in one batch. A cursor typically fetches a batch of result objects and store them locally. If batchSize is positive, it represents the size of each batch of objects retrieved. It can be adjusted to optimize performance and limit data transfer. If batchSize is negative, it will limit of number objects returned, that fit within the max batch size limit (usually 4MB), and cursor will be closed. For example if batchSize is -10, then the server will return a maximum of 10 documents and as many as can fit in 4MB, then close the cursor. Note that this feature is different from limit() in that documents must fit within a maximum size, and it removes the need to send a request to close the cursor server-side. The batch size can be changed even after a cursor is iterated, in which case the setting will apply on the next batch retrieval. | int/Integer |
DBObject
describing your sorting in the CamelMongoDbSortBy
header, quick constant: MongoDbConstants.SORT_BY
.
findAll
operation will also return the following OUT headers to enable you to iterate through result pages if you are using paging:
Header key | Quick constant | Description (extracted from MongoDB API doc) | Data type |
---|---|---|---|
CamelMongoDbResultTotalSize
|
MongoDbConstants.RESULT_TOTAL_SIZE
|
Number of objects matching the query. This does not take limit/skip into consideration. | int/Integer |
CamelMongoDbResultPageSize
|
MongoDbConstants.RESULT_PAGE_SIZE
|
Number of objects matching the query. This does not take limit/skip into consideration. | int/Integer |
Specifying a fields filter Copier lienLien copié sur presse-papiers!
DBObject
(or type convertible to DBObject
, such as a JSON String, Map, etc.) on the CamelMongoDbFieldsFilter
header, constant shortcut: MongoDbConstants.FIELDS_FILTER
.
_id
and boringField
:
// route: from("direct:findAll").to("mongodb:myDb?database=flights&collection=tickets&operation=findAll") DBObject fieldFilter = BasicDBObjectBuilder.start().add("_id", 0).add("boringField", 0).get(); Object result = template.requestBodyAndHeader("direct:findAll", (Object) null, MongoDbConstants.FIELDS_FILTER, fieldFilter);
// route: from("direct:findAll").to("mongodb:myDb?database=flights&collection=tickets&operation=findAll")
DBObject fieldFilter = BasicDBObjectBuilder.start().add("_id", 0).add("boringField", 0).get();
Object result = template.requestBodyAndHeader("direct:findAll", (Object) null, MongoDbConstants.FIELDS_FILTER, fieldFilter);
Create/update operations Copier lienLien copié sur presse-papiers!
insert Copier lienLien copié sur presse-papiers!
DBObject
or a List
. Two modes are supported: single insert and multiple insert. For multiple insert, the endpoint will expect a List, Array or Collections of objects of any type, as long as they are - or can be converted to - DBObject
. All objects are inserted at once. The endpoint will intelligently decide which backend operation to invoke (single or multiple insert) depending on the input.
from("direct:insert") .to("mongodb:myDb?database=flights&collection=tickets&operation=insert");
from("direct:insert")
.to("mongodb:myDb?database=flights&collection=tickets&operation=insert");
WriteConcern
or the value of the invokeGetLastError
option, getLastError()
would have been called already or not. If you want to access the ultimate result of the write operation, you need to retrieve the CommandResult
by calling getLastError()
or getCachedLastError()
on the WriteResult
. Then you can verify the result by calling CommandResult.ok()
, CommandResult.getErrorMessage()
and/or CommandResult.getException()
.
_id
must be unique in the collection. If you don't specify the value, MongoDB will automatically generate one for you. But if you do specify it and it is not unique, the insert operation will fail (and for Camel to notice, you will need to enable invokeGetLastError or set a WriteConcern that waits for the write result).
_id
, you are expected to ensure at the application level that is unique (and this is a good practice too).
save Copier lienLien copié sur presse-papiers!
- perform a query to retrieve the entire object first along with all its fields (may not be efficient), alter it inside Camel and then save it.
- use the update operation with $modifiers, which will execute the update at the server-side instead. You can enable the upsert flag, in which case if an insert is required, MongoDB will apply the $modifiers to the filter query object and insert the result.
from("direct:insert") .to("mongodb:myDb?database=flights&collection=tickets&operation=save");
from("direct:insert")
.to("mongodb:myDb?database=flights&collection=tickets&operation=save");
update Copier lienLien copié sur presse-papiers!
- Element 1 (index 0) => filter query => determines what objects will be affected, same as a typical query object
- Element 2 (index 1) => update rules => how matched objects will be updated. All modifier operations from MongoDB are supported.
CamelMongoDbMultiUpdate
IN message header to true
.
CamelMongoDbRecordsAffected
will be returned (MongoDbConstants.RECORDS_AFFECTED
constant) with the number of records updated (copied from WriteResult.getN()
).
Header key | Quick constant | Description (extracted from MongoDB API doc) | Expected type |
---|---|---|---|
CamelMongoDbMultiUpdate
|
MongoDbConstants.MULTIUPDATE
|
If the update should be applied to all objects matching. See http://www.mongodb.org/display/DOCS/Atomic+Operations | boolean/Boolean |
CamelMongoDbUpsert
|
MongoDbConstants.UPSERT
|
If the database should create the element if it does not exist | boolean/Boolean |
// route: from("direct:update").to("mongodb:myDb?database=science&collection=notableScientists&operation=update"); DBObject filterField = new BasicDBObject("filterField", true); DBObject updateObj = new BasicDBObject("$set", new BasicDBObject("scientist", "Darwin")); Object result = template.requestBodyAndHeader("direct:update", new Object[] {filterField, updateObj}, MongoDbConstants.MULTIUPDATE, true);
// route: from("direct:update").to("mongodb:myDb?database=science&collection=notableScientists&operation=update");
DBObject filterField = new BasicDBObject("filterField", true);
DBObject updateObj = new BasicDBObject("$set", new BasicDBObject("scientist", "Darwin"));
Object result = template.requestBodyAndHeader("direct:update", new Object[] {filterField, updateObj}, MongoDbConstants.MULTIUPDATE, true);
Delete operations Copier lienLien copié sur presse-papiers!
remove Copier lienLien copié sur presse-papiers!
DBObject
or a type convertible to it. The following example will remove all objects whose field 'conditionField' equals true, in the science database, notableScientists collection:
// route: from("direct:remove").to("mongodb:myDb?database=science&collection=notableScientists&operation=remove"); DBObject conditionField = new BasicDBObject("conditionField", true); Object result = template.requestBody("direct:remove", conditionField);
// route: from("direct:remove").to("mongodb:myDb?database=science&collection=notableScientists&operation=remove");
DBObject conditionField = new BasicDBObject("conditionField", true);
Object result = template.requestBody("direct:remove", conditionField);
CamelMongoDbRecordsAffected
is returned (MongoDbConstants.RECORDS_AFFECTED
constant) with type int
, containing the number of records deleted (copied from WriteResult.getN()
).
Other operations Copier lienLien copié sur presse-papiers!
count Copier lienLien copié sur presse-papiers!
// from("direct:count").to("mongodb:myDb?database=tickets&collection=flights&operation=count&dynamicity=true"); Long result = template.requestBodyAndHeader("direct:count", "irrelevantBody", MongoDbConstants.COLLECTION, "dynamicCollectionName"); assertTrue("Result is not of type Long", result instanceof Long);
// from("direct:count").to("mongodb:myDb?database=tickets&collection=flights&operation=count&dynamicity=true");
Long result = template.requestBodyAndHeader("direct:count", "irrelevantBody", MongoDbConstants.COLLECTION, "dynamicCollectionName");
assertTrue("Result is not of type Long", result instanceof Long);
getDbStats Copier lienLien copié sur presse-papiers!
db.stats()
command in the MongoDB shell, which displays useful statistic figures about the database. For example:
// from("direct:getDbStats").to("mongodb:myDb?database=flights&collection=tickets&operation=getDbStats"); Object result = template.requestBody("direct:getDbStats", "irrelevantBody"); assertTrue("Result is not of type DBObject", result instanceof DBObject);
// from("direct:getDbStats").to("mongodb:myDb?database=flights&collection=tickets&operation=getDbStats");
Object result = template.requestBody("direct:getDbStats", "irrelevantBody");
assertTrue("Result is not of type DBObject", result instanceof DBObject);
DBObject
in the OUT message body.
getColStats Copier lienLien copié sur presse-papiers!
db.collection.stats()
command in the MongoDB shell, which displays useful statistic figures about the collection. For example:
// from("direct:getColStats").to("mongodb:myDb?database=flights&collection=tickets&operation=getColStats"); Object result = template.requestBody("direct:getColStats", "irrelevantBody"); assertTrue("Result is not of type DBObject", result instanceof DBObject);
// from("direct:getColStats").to("mongodb:myDb?database=flights&collection=tickets&operation=getColStats");
Object result = template.requestBody("direct:getColStats", "irrelevantBody");
assertTrue("Result is not of type DBObject", result instanceof DBObject);
DBObject
in the OUT message body.
Dynamic operations Copier lienLien copié sur presse-papiers!
CamelMongoDbOperation
header, defined by the MongoDbConstants.OPERATION_HEADER
constant. The values supported are determined by the MongoDbOperation enumeration and match the accepted values for the operation
parameter on the endpoint URI.
// from("direct:insert").to("mongodb:myDb?database=flights&collection=tickets&operation=insert"); Object result = template.requestBodyAndHeader("direct:insert", "irrelevantBody", MongoDbConstants.OPERATION_HEADER, "count"); assertTrue("Result is not of type Long", result instanceof Long);
// from("direct:insert").to("mongodb:myDb?database=flights&collection=tickets&operation=insert");
Object result = template.requestBodyAndHeader("direct:insert", "irrelevantBody", MongoDbConstants.OPERATION_HEADER, "count");
assertTrue("Result is not of type Long", result instanceof Long);
Tailable Cursor Consumer Copier lienLien copié sur presse-papiers!
tail -f
command of *nix systems. This mechanism is significantly more efficient than a scheduled poll, due to the fact that the server pushes new data to the client as it becomes available, rather than making the client ping back at scheduled intervals to fetch new data. It also reduces otherwise redundant network traffic.
How the tailable cursor consumer works Copier lienLien copié sur presse-papiers!
DBCursor.next()
method until new data arrives. However, the MongoDB server reserves itself the right to kill your cursor if new data doesn't appear after an indeterminate period. If you are interested to continue consuming new data, you have to regenerate the cursor. And to do so, you will have to remember the position where you left off or else you will start consuming from the top again.
increasingField > lastValue
, so that only unread data is consumed.
tailTrackingIncreasingField
option. In Camel 2.10, it must be a top-level field in your data, as nested navigation for this field is not yet supported. That is, the "timestamp" field is okay, but "nested.timestamp" will not work. Please open a ticket in the Camel JIRA if you do require support for nested increasing fields.
cursorRegenerationDelay
option has been introduced (with a default value of 1000ms.), which you can modify to suit your needs.
from("mongodb:myDb?database=flights&collection=cancellations&tailTrackIncreasingField=departureTime") .id("tailableCursorConsumer1") .autoStartup(false) .to("mock:test");
from("mongodb:myDb?database=flights&collection=cancellations&tailTrackIncreasingField=departureTime")
.id("tailableCursorConsumer1")
.autoStartup(false)
.to("mock:test");
Persistent tail tracking Copier lienLien copié sur presse-papiers!
Enabling persistent tail tracking Copier lienLien copié sur presse-papiers!
persistentTailTracking
option totrue
persistentId
option to a unique identifier for this consumer, so that the same collection can be reused across many consumers
tailTrackDb
, tailTrackCollection
and tailTrackField
options to customise where the runtime information will be stored. Refer to the endpoint options table at the top of this page for descriptions of each option.
camelTailTracking
and lastTrackingValue
are defaults).
Type conversions Copier lienLien copié sur presse-papiers!
MongoDbBasicConverters
type converter included with the camel-mongodb component provides the following conversions:
Name | From type | To type | How? |
---|---|---|---|
fromMapToDBObject |
Map
|
DBObject
|
constructs a new BasicDBObject via the new BasicDBObject(Map m) constructor
|
fromBasicDBObjectToMap |
BasicDBObject
|
Map
|
BasicDBObject already implements Map
|
fromStringToDBObject |
String
|
DBObject
|
uses com.mongodb.util.JSON.parse(String s)
|
fromAnyObjectToDBObject |
Object
|
DBObject
|
uses the Jackson library to convert the object to a Map , which is in turn used to initialise a new BasicDBObject
|
See also Copier lienLien copié sur presse-papiers!
- Unit tests for more examples of usage
Chapter 70. MQTT Copier lienLien copié sur presse-papiers!
MQTT Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
mqtt://name[?options]
mqtt://name[?options]
Options Copier lienLien copié sur presse-papiers!
Property | Default | Description |
---|---|---|
host
|
tcp://127.0.0.1:1883
|
The URI of the MQTT broker to connect too - this component also supports SSL - e.g. ssl://127.0.0.1:8883 |
localAddress
|
The local InetAddress and port to use | |
connectAttemptsMax
|
-1
|
The maximum number of attempts to establish an initial connection - -1 in infinite. |
reconnectAttemptsMax
|
-1
|
The maximum number of attempts to re-establish a connection after failure - -1 in infinite. |
reconnectDelay
|
10
|
The time in milliseconds between attempts to reestablish an initial or failed connection |
reconnectBackOffMultiplier
|
2.0
|
The multiplier to use to the delay between connection attempts for successive failed connection attempts |
reconnectDelayMax
|
30000
|
The maximum time in milliseconds between a new attempt to establish a connection. So even using the reconnectBackOffMultiplier, this property will define the maximum delay before another connection attempt to the MQTT broker |
QoS
|
AtLeastOnce
|
The MQTT Quality of Service to use for message exchanges. It can be one of AtMostOnce, AtLeastOnce or ExactlyOnce |
subscribeTopicName
|
The name of the Topic to subscribe to for messages | |
publishTopicName
|
camel/mqtt/test
|
The default Topic to publish messages on |
byDefaultRetain
|
false
|
The default retain policy to be used on messages sent to the MQTT broker |
mqttTopicPropertyName
|
_MQTTTopicPropertyName+
|
The property name to look for on an Exchange for an individual published message. If this is set - the name will be used as the Topic to publish a message to the MQTT message broker. |
mqttRetainPropertyName
|
MQTTRetain
|
The property name to look for on an Exchange for an individual published message. If this is set (expects a Boolean value) - then the retain property will be set on the message sent to the MQTT message broker. |
mqttQosPropertyName
|
MQTTQos
|
The property name to look for on an Exchange for an individual published message. If this is set (one of AtMostOnce, AtLeastOnce or ExactlyOnce ) - then that QoS will be set on the message sent to the MQTT message broker. |
connectWaitInSeconds
|
10
|
Delay in seconds the Component will wait for a connection to be established to the MQTT broker |
disconnectWaitInSeconds
|
5
|
the number of seconds the Component will wait for a valid disconnect on stop() from the MQTT broker |
sendWaitInSeconds
|
5
|
The maximum time the Component will wait for a receipt from the MQTT broker to acknowledge a published message before throwing an exception |
?option=value&option=value&...
Samples Copier lienLien copié sur presse-papiers!
from("direct:foo").to("mqtt:cheese?publishTopicName=test.mqtt.topic");
from("direct:foo").to("mqtt:cheese?publishTopicName=test.mqtt.topic");
from("mqtt:bar?subscribeTopicName=test.mqtt.topic").transform(body().convertToString()).to("mock:result")
from("mqtt:bar?subscribeTopicName=test.mqtt.topic").transform(body().convertToString()).to("mock:result")
Chapter 71. MSV Copier lienLien copié sur presse-papiers!
MSV Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
msv:someLocalOrRemoteResource[?options]
msv:someLocalOrRemoteResource[?options]
msv:org/foo/bar.rng msv:file:../foo/bar.rng msv:http://acme.com/cheese.rng
msv:org/foo/bar.rng
msv:file:../foo/bar.rng
msv:http://acme.com/cheese.rng
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
useDom
|
true
|
Whether DOMSource/DOMResult or SaxSource/SaxResult should be used by the validator. Note: DOM must be used by the MSV component. |
Example Copier lienLien copié sur presse-papiers!
Chapter 72. MyBatis Copier lienLien copié sur presse-papiers!
MyBatis Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
mybatis:statementName[?options]
mybatis:statementName[?options]
?option=value&option=value&...
SqlMapConfig.xml
. If the file is located in another location, you will need to configure the configurationUri
option on the MyBatisComponent
component.
Options Copier lienLien copié sur presse-papiers!
Option | Type | Default | Description |
---|---|---|---|
consumer.onConsume
|
String
|
null
|
Statements to run after consuming. Can be used, for example, to update rows after they have been consumed and processed in Camel. See sample later. Multiple statements can be separated with commas. |
consumer.useIterator
|
boolean
|
true
|
If true each row returned when polling will be processed individually. If false the entire List of data is set as the IN body.
|
consumer.routeEmptyResultSet
|
boolean
|
false
|
Sets whether empty result sets should be routed. |
statementType
|
StatementType
|
null
|
Mandatory to specify for the producer to control which kind of operation to invoke. The enum values are: SelectOne , SelectList , Insert , InsertList , Update , Delete . Notice:InsertList is available as of Camel 2.10.
|
maxMessagesPerPoll
|
int
|
0
|
An integer to define the maximum messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid when starting up the server that there are thousands of files. Set a value of 0 or negative to disable it. |
Message Headers Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelMyBatisStatementName
|
String
|
The statementName used (for example: insertAccount). |
CamelMyBatisResult
|
Object
|
The response returned from MtBatis in any of the operations. For instance an INSERT could return the auto-generated key, or number of rows etc.
|
Message Body Copier lienLien copié sur presse-papiers!
SELECT
statement. That means, for example, for INSERT
statements Camel will not replace the body. This allows you to continue routing and keep the original body. The response from MyBatis is always stored in the header with the key CamelMyBatisResult
.
Samples Copier lienLien copié sur presse-papiers!
from("activemq:queue:newAccount"). to("mybatis:insertAccount?statementType=Insert");
from("activemq:queue:newAccount").
to("mybatis:insertAccount?statementType=Insert");
statementType
, as we need to instruct Camel which kind of operation to invoke.
Using StatementType for better control of MyBatis Copier lienLien copié sur presse-papiers!
SELECT
, UPDATE
, DELETE
or INSERT
etc. So for instance if we want to route to an MyBatis endpoint in which the IN body contains parameters to a SELECT
statement we can do:
from("direct:start") .to("mybatis:selectAccountById?statementType=SelectOne") .to("mock:result");
from("direct:start")
.to("mybatis:selectAccountById?statementType=SelectOne")
.to("mock:result");
selectAccountById
and the IN body should contain the account id we want to retrieve, such as an Integer
type.
SelectList
:
from("direct:start") .to("mybatis:selectAllAccounts?statementType=SelectList") .to("mock:result");
from("direct:start")
.to("mybatis:selectAllAccounts?statementType=SelectList")
.to("mock:result");
UPDATE
, where we can send an Account
object as the IN body to MyBatis:
from("direct:start") .to("mybatis:updateAccount?statementType=Update") .to("mock:result");
from("direct:start")
.to("mybatis:updateAccount?statementType=Update")
.to("mock:result");
Using InsertList StatementType Copier lienLien copié sur presse-papiers!
mybatis
endpoint which uses the InsertList
statement type, as shown below:
from("direct:start") .to("mybatis:batchInsertAccount?statementType=InsertList") .to("mock:result");
from("direct:start")
.to("mybatis:batchInsertAccount?statementType=InsertList")
.to("mock:result");
Scheduled polling example Copier lienLien copié sur presse-papiers!
from("timer://pollTheDatabase?delay=30000").to("mbatis:selectAllAccounts").to("activemq:queue:allAccounts");
from("timer://pollTheDatabase?delay=30000").to("mbatis:selectAllAccounts").to("activemq:queue:allAccounts");
<!-- Select with no parameters using the result map for Account class. --> <select id="selectAllAccounts" resultMap="AccountResult"> select * from ACCOUNT </select>
<!-- Select with no parameters using the result map for Account class. -->
<select id="selectAllAccounts" resultMap="AccountResult">
select * from ACCOUNT
</select>
Using onConsume Copier lienLien copié sur presse-papiers!
UPDATE
statements. Camel supports executing multiple statements whose names should be separated by commas.
from("mybatis:selectUnprocessedAccounts?consumer.onConsume=consumeAccount").to("mock:results");
from("mybatis:selectUnprocessedAccounts?consumer.onConsume=consumeAccount").to("mock:results");
<select id="selectUnprocessedAccounts" resultMap="AccountResult"> select * from ACCOUNT where PROCESSED = false </select>
<select id="selectUnprocessedAccounts" resultMap="AccountResult">
select * from ACCOUNT where PROCESSED = false
</select>
<update id="consumeAccount" parameterType="Account"> update ACCOUNT set PROCESSED = true where ACC_ID = #{id} </update>
<update id="consumeAccount" parameterType="Account">
update ACCOUNT set PROCESSED = true where ACC_ID = #{id}
</update>
Participating in transactions Copier lienLien copié sur presse-papiers!
SqlMapConfig.xml
file.
DataSource
. This is typically a pool (either DBCP, or c3p0), which needs to be wrapped in a Spring proxy. This proxy enables non-Spring use of the DataSource
to participate in Spring transactions (the MyBatis SqlSessionFactory
does just this).
DataSource
:
<bean id="txManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager"> <property name="dataSource" ref="dataSource"/> </bean>
<bean id="txManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
<property name="dataSource" ref="dataSource"/>
</bean>
<bean id="mybatis" class="org.apache.camel.component.mybatis.MyBatisComponent"> <property name="sqlSessionFactory" ref="sqlSessionFactory"/> </bean>
<bean id="mybatis" class="org.apache.camel.component.mybatis.MyBatisComponent">
<property name="sqlSessionFactory" ref="sqlSessionFactory"/>
</bean>
Chapter 73. Nagios Copier lienLien copié sur presse-papiers!
Nagios Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
nagios://host[:port][?Options]
nagios://host[:port][?Options]
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
host
|
none | This is the address of the Nagios host where checks should be send. |
port
|
The port number of the host. | |
password
|
Password to be authenticated when sending checks to Nagios. | |
connectionTimeout
|
5000 | Connection timeout in millis. |
timeout
|
5000 | Sending timeout in millis. |
nagiosSettings
|
To use an already configured com.googlecode.jsendnsca.core.NagiosSettings object. Then any of the other options are not in use, if using this.
|
|
sendSync
|
true
|
Whether or not to use synchronous when sending a passive check. Setting it to false will allow Apache Camel to continue routing the message and the passive check message will be send asynchronously.
|
encryptionMethod
|
No
|
*Camel 2.9:* To specify an encryption method. Possible values: No , Xor , or TripleDes .
|
Headers Copier lienLien copié sur presse-papiers!
Name | Description |
---|---|
CamelNagiosHostName
|
This is the address of the Nagios host where checks should be send. This header will override any existing hostname configured on the endpoint. |
CamelNagiosLevel
|
This is the severity level. You can use values CRITICAL, WARNING, OK . Apache Camel will by default use OK .
|
CamelNagiosServiceName
|
The servie name. Will default use the CamelContext name. |
Sending message examples Copier lienLien copié sur presse-papiers!
OK
level and use the CamelContext name as the service name. You can overrule these values using headers as shown above.
Hello Nagios
message to Nagios as follows:
template.sendBody("direct:start", "Hello Nagios"); from("direct:start").to("nagios:127.0.0.1:5667?password=secret").to("mock:result");
template.sendBody("direct:start", "Hello Nagios");
from("direct:start").to("nagios:127.0.0.1:5667?password=secret").to("mock:result");
CRITICAL
message you can send the headers such as:
Map headers = new HashMap(); headers.put(NagiosConstants.LEVEL, "CRITICAL"); headers.put(NagiosConstants.HOST_NAME, "myHost"); headers.put(NagiosConstants.SERVICE_NAME, "myService"); template.sendBodyAndHeaders("direct:start", "Hello Nagios", headers);
Map headers = new HashMap();
headers.put(NagiosConstants.LEVEL, "CRITICAL");
headers.put(NagiosConstants.HOST_NAME, "myHost");
headers.put(NagiosConstants.SERVICE_NAME, "myService");
template.sendBodyAndHeaders("direct:start", "Hello Nagios", headers);
Using NagiosEventNotifer Copier lienLien copié sur presse-papiers!
EventNotifier
and Apache Camel will pick it up as documented here: Advanced configuration of CamelContext using Spring.
Chapter 74. Netty Copier lienLien copié sur presse-papiers!
Netty Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
netty:tcp://localhost:99999[?options] netty:udp://remotehost:99999/[?options]
netty:tcp://localhost:99999[?options]
netty:udp://remotehost:99999/[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
keepAlive
|
true
|
Setting to ensure socket is not closed due to inactivity |
tcpNoDelay
|
true
|
Setting to improve TCP protocol performance |
broadcast
|
false
|
Setting to choose Multicast over UDP |
connectTimeout
|
10000
|
Time to wait for a socket connection to be available. Value is in millis. |
reuseAddress
|
true
|
Setting to facilitate socket multiplexing |
sync
|
true
|
Setting to set endpoint as one-way or request-response |
synchronous
|
false
|
*Camel 2.10:* Whether Asynchronous Routing Engine is not in use. false then the Asynchronous Routing Engine is used, true to force processing synchronous.
|
ssl
|
false
|
Setting to specify whether SSL encryption is applied to this endpoint |
sendBufferSize
|
65536 bytes
|
The TCP/UDP buffer sizes to be used during outbound communication. Size is bytes. |
receiveBufferSize
|
65536 bytes
|
The TCP/UDP buffer sizes to be used during inbound communication. Size is bytes. |
corePoolSize
|
10
|
The number of allocated threads at component startup. Defaults to 10. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings. |
maxPoolSize
|
100
|
The maximum number of threads that may be allocated to this endpoint. Defaults to 100. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings. |
disconnect
|
false
|
Whether or not to disconnect(close) from Netty Channel right after use. Can be used for both consumer and producer. |
lazyChannelCreation
|
true
|
Channels can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started. |
transferExchange
|
false
|
Only used for TCP. You can transfer the exchange over the wire instead of just the body. The following fields are transferred: In body, Out body, fault body, In headers, Out headers, fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. |
disconnectOnNoReply
|
true
|
If sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back. |
noReplyLogLevel
|
WARN
|
If sync is enabled this option dictates NettyConsumer which logging level to use when logging a there is no reply to send back. Values are: FATAL, ERROR, INFO, DEBUG, OFF .
|
allowDefaultCodec
|
true
|
*Camel 2.4:* The netty component installs a default codec if both, encoder/deocder is null and textline is false. Setting allowDefaultCodec to false prevents the netty component from installing a default codec as the first element in the filter chain. |
textline
|
false
|
*Camel 2.4:* Only used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not specified or the value is false, then Object Serialization is assumed over TCP. |
delimiter
|
LINE
|
*Camel 2.4:* The delimiter to use for the textline codec. Possible values are LINE and NULL .
|
decoderMaxLineLength
|
1024
|
*Camel 2.4:* The max line length to use for the textline codec. |
autoAppendDelimiter
|
true
|
*Camel 2.4:* Whether or not to auto append missing end delimiter when sending using the textline codec. |
encoding
|
null
|
*Camel 2.4:* The encoding (a charset name) to use for the textline codec. If not provided, Camel will use the JVM default Charset. |
workerCount
|
null
|
*Camel 2.9:* When netty works on nio mode, it uses default workerCount parameter from Netty, which is cpu_core_threads*2. User can use this operation to override the default workerCount from Netty |
sslContextParametersRef
|
null
|
*Camel 2.9:* Reference to a org.apache.camel.util.jsse.SSLContextParameters in the CAMEL:Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
|
receiveBufferSizePredictor
|
null
|
*Camel 2.9:* Configures the buffer size predictor. See details at Jetty documentation and this mail thread. |
needClientAuth
|
false
|
*Camel 2.11:* Configures whether the server needs client authentication when using SSL. |
orderedThreadPoolExecutor
|
true
|
*Camel 2.10.2:* Whether to use ordered thread pool, to ensure events are processed orderly on the same channel. See details at the netty javadoc of org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor for more details.
|
maximumPoolSize
|
16
|
*Camel 2.10.2:* The core pool size for the ordered thread pool, if its in use. |
producerPoolMaxActive
|
-1
|
*Camel 2.10.3:* Producer only. Sets the cap on the number of objects that can be allocated by the pool (checked out to clients, or idle awaiting checkout) at a given time. Use a negative value for no limit. |
producerPoolMinIdle
|
0
|
*Camel 2.10.3:* Producer only. Sets the minimum number of instances allowed in the producer pool before the evictor thread (if active) spawns new objects. |
producerPoolMaxIdle
|
100
|
*Camel 2.10.3:* Producer only. Sets the cap on the number of "idle" instances in the pool. |
producerPoolMinEvictableIdle
|
30000
|
*Camel 2.10.3:* Producer only. Sets the minimum amount of time (value in millis) an object may sit idle in the pool before it is eligible for eviction by the idle object evictor. |
Registry based Options Copier lienLien copié sur presse-papiers!
Name | Description |
---|---|
passphrase
|
password setting to use in order to encrypt/decrypt payloads sent using SSH |
keyStoreFormat
|
keystore format to be used for payload encryption. Defaults to "JKS" if not set |
securityProvider
|
Security provider to be used for payload encryption. Defaults to "SunX509" if not set. |
keyStoreFile
|
Client side certificate keystore to be used for encryption |
trustStoreFile
|
Server side certificate keystore to be used for encryption |
sslHandler
|
Reference to a class that could be used to return an SSL Handler |
encoder
|
A custom ChannelHandler class that can be used to perform special marshalling of outbound payloads. Must override org.jboss.netty.channel.ChannelDownStreamHandler .
|
encorders
|
A list of encoders to be used. You can use a String which have values separated by comma, and have the values be looked up in the Registry. Just remember to prefix the value with # so Camel knows it should lookup. |
decoder
|
A custom ChannelHandler class that can be used to perform special marshalling of inbound payloads. Must override org.jboss.netty.channel.ChannelUpStreamHandler .
|
decoders
|
A list of decoders to be used. You can use a String which have values separated by comma, and have the values be looked up in the Registry. Just remember to prefix the value with # so Camel knows it should lookup. |
Sending Messages to/from a Netty endpoint Copier lienLien copié sur presse-papiers!
Netty Producer Copier lienLien copié sur presse-papiers!
Netty Consumer Copier lienLien copié sur presse-papiers!
- listen on a specified socket using either TCP or UDP protocols (with optional SSL support),
- receive requests on the socket using text/xml, binary and serialized object based payloads and
- send them along on a route as message exchanges.
A UDP Netty endpoint using Request-Reply and serialized object payload Copier lienLien copié sur presse-papiers!
A TCP based Netty consumer endpoint using One-way communication Copier lienLien copié sur presse-papiers!
An SSL/TCP based Netty consumer endpoint using Request-Reply communication Copier lienLien copié sur presse-papiers!
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
Programmatic configuration of the component Copier lienLien copié sur presse-papiers!
Spring DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
Using Basic SSL/TLS configuration on the Jetty Component Copier lienLien copié sur presse-papiers!
Using Multiple Codecs Copier lienLien copié sur presse-papiers!
Closing Channel When Complete Copier lienLien copié sur presse-papiers!
disconnect=true
.
CamelNettyCloseChannelWhenComplete
set to a boolean true
value. For instance, the example below will close the channel after it has written the bye message back to the client:
Adding custom channel pipeline factories to gain complete control over a created pipeline Copier lienLien copié sur presse-papiers!
- A Producer linked channel pipeline factory must extend the abstract class
ClientPipelineFactory
. - A Consumer linked channel pipeline factory must extend the abstract class
ServerPipelineFactory
. - The classes should override the getPipeline() method in order to insert custom handler(s), encoder(s) and decoder(s). Not overriding the getPipeline() method creates a pipeline with no handlers, encoders or decoders wired to the pipeline.
Chapter 75. NMR Copier lienLien copié sur presse-papiers!
NMR Component Copier lienLien copié sur presse-papiers!
Installing Copier lienLien copié sur presse-papiers!
features install nmr
features install nmr
META-INF/spring/*.xml
, and adding the following bean
instance:
NMR consumer and producer endpoints Copier lienLien copié sur presse-papiers!
from("nmr:MyServiceEndpoint")
from("nmr:MyServiceEndpoint")
MyServiceEndpoint
(see #URI-format).
to("nmr:MyServiceEndpoint")
to("nmr:MyServiceEndpoint")
URI format Copier lienLien copié sur presse-papiers!
nmr:endpointName
nmr:endpointName
URI Options Copier lienLien copié sur presse-papiers!
Option | Default Value | Description |
---|---|---|
synchronous
|
false
|
When this is set to true on a consumer endpoint, an incoming, synchronous NMR Exchange will be handled on the sender's thread instead of being handled on a new thread of the NMR endpoint's thread pool
|
runAsSubject
|
false
|
When this is set to true on a consumer endpoint, the endpoint will be invoked on behalf of the Subject that is set on the Exchange (i.e. the call to Subject.getSubject(AccessControlContext) returns the Subject instance)
|
timeout
|
0
|
When this is set to a value greater than 0 , the producer endpoint will time out if it doesn't receive a response from the NMR within the given timeout period (in milliseconds). Configuring a timeout value will switch to using synchronous interactions with the NMR instead of the usual asynchronous messaging.
|
Examples Copier lienLien copié sur presse-papiers!
// consume nmr exchanges asynchronously from("nmr:MyServiceEndpoint") // consume nmr exchanges synchronously and use the same thread as defined by NMR ThreadPool from("nmr:MyServiceEndpoint?synchronous=true").to()
// consume nmr exchanges asynchronously
from("nmr:MyServiceEndpoint")
// consume nmr exchanges synchronously and use the same thread as defined by NMR ThreadPool
from("nmr:MyServiceEndpoint?synchronous=true").to()
// produce nmr exchanges asynchronously from()...to("nmr:MyServiceEndpoint") // produce nmr exchanges synchronously and wait till 10s to receive response from()...to("nmr:MyServiceEndpoint?timeout=10000")
// produce nmr exchanges asynchronously
from()...to("nmr:MyServiceEndpoint")
// produce nmr exchanges synchronously and wait till 10s to receive response
from()...to("nmr:MyServiceEndpoint?timeout=10000")
Using Stream bodies Copier lienLien copié sur presse-papiers!
DEBUG
logging, the body is usually logged and thus read. To deal with this, Camel has a streamCaching
option that can cache the stream, enabling you to read it multiple times.
from("nmr:MyEndpoint").streamCaching().to("xslt:transform.xsl", "bean:doSomething");
from("nmr:MyEndpoint").streamCaching().to("xslt:transform.xsl", "bean:doSomething");
streamCaching()
option. In Camel 2.0 we store big input streams (by default, over 64K) in a temp
file using CachedOutputStream
. When you close the input stream, the temp file will be deleted.
Testing Copier lienLien copié sur presse-papiers!
ServiceMixNMR
Mock class, org.apache.servicemix.camel.nmr.AbstractComponentTest
, which will create an NMR bus, register the Apache Camel NMR Component and the endpoints defined into the Apache Camel routes.
Chapter 76. Pax-Logging Copier lienLien copié sur presse-papiers!
PaxLogging component Copier lienLien copié sur presse-papiers!
paxlogging
component can be used in an OSGi environment to receive PaxLogging events and process them.
Dependencies Copier lienLien copié sur presse-papiers!
pom.xml
$\{camel-version\}
must be replaced by the actual version of Camel (2.6.0 or higher).
URI format Copier lienLien copié sur presse-papiers!
paxlogging:appender
paxlogging:appender
appender
is the name of the pax appender that need to be configured in the PaxLogging service configuration.
URI options Copier lienLien copié sur presse-papiers!
Name | Default value | Description |
---|
Message headers Copier lienLien copié sur presse-papiers!
Name | Type | Message | Description |
---|
Message body Copier lienLien copié sur presse-papiers!
in
message body will be set to the received PaxLoggingEvent.
Example usage Copier lienLien copié sur presse-papiers!
log4j.rootLogger=INFO, out, osgi:VmLogAppender, osgi:camel
log4j.rootLogger=INFO, out, osgi:VmLogAppender, osgi:camel
Chapter 77. Printer Copier lienLien copié sur presse-papiers!
Printer Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
lpr://localhost/default[?options] lpr://remotehost:port/path/to/printer[?options]
lpr://localhost/default[?options]
lpr://remotehost:port/path/to/printer[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
mediaSize
|
MediaSizeName.NA_LETTER
|
Sets the stationary as defined by enumeration settings in the javax.print.attribute.standard.MediaSizeName API API. The default setting is to use North American Letter sized stationary |
copies
|
1
|
Sets number of copies based on the javax.print.attribute.standard.Copies API
|
sides
|
Sides.ONE_SIDED
|
Sets one sided or two sided printing based on the javax.print.attribute.standard.Sides API
|
flavor
|
DocFlavor.BYTE_ARRAY
|
Sets DocFlavor based on the javax.print.DocFlavor API
|
mimeType
|
AUTOSENSE
|
Sets mimeTypes supported by the javax.print.DocFlavor API
|
mediaTray
|
AUTOSENSE
|
Since Camel 2.11.x sets MediaTray supported by the javax.print.DocFlavor API |
printerPrefix
|
null | Since Camel 2.11.x sets the prefix name of the printer, it is useful when the printer name is not start with //hostname/printer |
sendToPrinter
|
true |
Setting this option to false prevents sending of the print data to the printer
|
Printer Producer Copier lienLien copié sur presse-papiers!
Example 1: Printing text based payloads on a Default printer using letter stationary and one-sided mode Copier lienLien copié sur presse-papiers!
Example 2: Printing GIF based payloads on a Remote printer using A4 stationary and one-sided mode Copier lienLien copié sur presse-papiers!
Example 3: Printing JPEG based payloads on a Remote printer using Japanese Postcard stationary and one-sided mode Copier lienLien copié sur presse-papiers!
Chapter 78. Properties Copier lienLien copié sur presse-papiers!
Properties Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
properties:key[?options]
properties:key[?options]
Options Copier lienLien copié sur presse-papiers!
Name | Type | Default | Description |
---|---|---|---|
cache
|
boolean
|
true
|
Whether or not to cache loaded properties. |
locations
|
String
|
null
|
A list of locations to load properties. You can use comma to separate multiple locations. This option will override any default locations and only use the locations from this option. |
ignoreMissingLocation
|
boolean
|
false
|
*Camel 2.10:* Whether to silently ignore if a location cannot be located, such as a properties file not found. |
propertyPrefix
|
String
|
null
|
*Camel 2.9* Optional prefix prepended to property names before resolution. |
propertySuffix
|
String
|
null
|
*Camel 2.9* Optional suffix appended to property names before resolution. |
fallbackToUnaugmentedProperty
|
boolean
|
true
|
*Camel 2.9* If true, first attempt resolution of property name augmented with propertyPrefix and propertySuffix before falling back the plain property name specified. If false, only the augmented property name is searched.
|
prefixToken
|
String
|
{{ | *Camel 2.9* The token to indicate the beginning of a property token. |
suffixToken
|
String
|
}} | *Camel 2.9* The token to indicate the end of a property token. |
resolvePropertyPlaceholders
on the CamelContext
to resolve a property from any Java code.
See also Copier lienLien copié sur presse-papiers!
- Jasypt for using encrypted values (for example, passwords) in the properties
Chapter 79. Quartz Copier lienLien copié sur presse-papiers!
Quartz Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
quartz://timerName?options quartz://groupName/timerName?options quartz://groupName/timerName?cron=expression quartz://timerName?cron=expression
quartz://timerName?options
quartz://groupName/timerName?options
quartz://groupName/timerName?cron=expression
quartz://timerName?cron=expression
CronTrigger
or a SimpleTrigger
. If no cron expression is provided, the component uses a simple trigger. If no groupName
is provided, the quartz component uses the Camel
group name.
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Parameter | Default | Description |
---|---|---|
cron
|
None |
Specifies a cron expression (not compatible with the trigger.\* or job.\* options).
|
trigger.repeatCount
|
0
|
SimpleTrigger: How many times should the timer repeat? |
trigger.repeatInterval
|
0
|
SimpleTrigger: The amount of time in milliseconds between repeated triggers. |
job.name
|
null
|
Sets the job name. |
job._XXX_
|
null
|
Sets the job option with the _XXX_ setter name.
|
trigger._XXX_
|
null
|
Sets the trigger option with the _XXX_ setter name.
|
stateful
|
false
|
Uses a Quartz StatefulJob instead of the default job.
|
fireNow
|
false
|
New to Camel 2.2.0, if it is true will fire the trigger when the route is start when using SimpleTrigger. |
mock:results
endpoint:
from("quartz://myGroup/myTimerName?trigger.repeatInterval=2&trigger.repeatCount=1").routeId("myRoute").to("mock:result");
from("quartz://myGroup/myTimerName?trigger.repeatInterval=2&trigger.repeatCount=1").routeId("myRoute").to("mock:result");
id
to the <camelContext> that this id is unique, as this is required by the QuartzScheduler
in the OSGi container. If you do not set any id
on <camelContext> then an unique id is auto assigned, and there is no problem.
Configuring quartz.properties file Copier lienLien copié sur presse-papiers!
quartz.properties
file in the root of the classpath. If you are using WAR deployments this means just drop the quartz.properties in WEB-INF/classes
.
Parameter | Default | Type | Description |
---|---|---|---|
properties
|
null
|
Properties
|
Camel 2.4: You can configure a java.util.Propoperties instance.
|
propertiesFile
|
null
|
String
|
Camel 2.4: File name of the properties to load from the classpath |
<bean id="quartz" class="org.apache.camel.component.quartz.QuartzComponent"> <property name="propertiesFile" value="com/mycompany/myquartz.properties"/> </bean>
<bean id="quartz" class="org.apache.camel.component.quartz.QuartzComponent">
<property name="propertiesFile" value="com/mycompany/myquartz.properties"/>
</bean>
Starting the Quartz scheduler Copier lienLien copié sur presse-papiers!
Parameter | Default | Type | Description |
---|---|---|---|
startDelayedSeconds
|
0
|
int
|
Camel 2.4: Seconds to wait before starting the quartz scheduler. |
autoStartScheduler
|
true
|
boolean
|
Camel 2.4: Whether or not the scheduler should be auto started. |
<bean id="quartz" class="org.apache.camel.component.quartz.QuartzComponent"> <property name="startDelayedSeconds" value="5"/> </bean>
<bean id="quartz" class="org.apache.camel.component.quartz.QuartzComponent">
<property name="startDelayedSeconds" value="5"/>
</bean>
Clustering Copier lienLien copié sur presse-papiers!
JobStore
is clustered. Then from Camel 2.4 onwards the Quartz component will not pause/remove triggers when a node is being stopped/shutdown. This allows the trigger to keep running on the other nodes in the cluster.
Message Headers Copier lienLien copié sur presse-papiers!
calendar
, fireTime
, jobDetail
, jobInstance
, jobRuntTime
, mergedJobDataMap
, nextFireTime
, previousFireTime
, refireCount
, result
, scheduledFireTime
, scheduler
, trigger
, triggerName
, triggerGroup
.
fireTime
header contains the java.util.Date
of when the exchange was fired.
Using Cron Triggers Copier lienLien copié sur presse-papiers!
cron
URI parameter; though to preserve valid URI encoding we allow + to be used instead of spaces. Quartz provides a little tutorial on how to use cron expressions.
from("quartz://myGroup/myTimerName?cron=0+0/5+12-18+?+*+MON-FRI").to("activemq:Totally.Rocks");
from("quartz://myGroup/myTimerName?cron=0+0/5+12-18+?+*+MON-FRI").to("activemq:Totally.Rocks");
0 0/5 12-18 ? * MON-FRI
0 0/5 12-18 ? * MON-FRI
URI Character | Cron character |
---|---|
\+
|
Space |
Specifying time zone Copier lienLien copié sur presse-papiers!
quartz://groupName/timerName?cron=0+0/5+12-18+?+*+MON-FRI&trigger.timeZone=Europe/Stockholm
quartz://groupName/timerName?cron=0+0/5+12-18+?+*+MON-FRI&trigger.timeZone=Europe/Stockholm
java.util.TimeZone
.
String
to java.util.TimeZone
Type Converter to be able configure this from the endpoint uri. From Camel 2.8.1 onwards we have included such a Type Converter in the camel-core.
Chapter 80. Quickfix Copier lienLien copié sur presse-papiers!
QuickFIX/J Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
quickfix:configFile[?sessionID=sessionID]
quickfix:configFile[?sessionID=sessionID]
(BeginString):(SenderCompID)[/(SenderSubID)[/(SenderLocationID)]]->(TargetCompID)[/(TargetSubID)[/(TargetLocationID)]]
(BeginString):(SenderCompID)[/(SenderSubID)[/(SenderLocationID)]]->(TargetCompID)[/(TargetSubID)[/(TargetLocationID)]]
quickfix:config.cfg quickfix:config.cfg?sessionID=FIX.4.2:MyTradingCompany->SomeExchange
quickfix:config.cfg
quickfix:config.cfg?sessionID=FIX.4.2:MyTradingCompany->SomeExchange
Endpoints Copier lienLien copié sur presse-papiers!
Exchange Format Copier lienLien copié sur presse-papiers!
Header Name | Description |
---|---|
EventCategory
|
One of AppMessageReceived , AppMessageSent , AdminMessageReceived , AdminMessageSent , SessionCreated , SessionLogon , SessionLogoff . See the QuickfixjEventCategory enum.
|
SessionID
|
The FIX message SessionID |
MessageType
|
The FIX MsgType tag value |
DataDictionary
|
Specifies a data dictionary to used for parsing an incoming message. Can be an instance of a data dictionary or a resource path for a QuickFIX/J data dictionary file |
QuickFIX/J Configuration Extensions Copier lienLien copié sur presse-papiers!
Communication Connectors Copier lienLien copié sur presse-papiers!
Session Setting | Component Action |
---|---|
ConnectionType=initiator
|
Create an initiator connector |
ConnectionType=acceptor
|
Create an acceptor connector |
Default/Global Setting | Component Action |
---|---|
ThreadModel=ThreadPerConnector
|
Use SocketInitiator or SocketAcceptor (default)
|
ThreadModel=ThreadPerSession
|
Use ThreadedSocketInitiator or ThreadedSocketAcceptor
|
Logging Copier lienLien copié sur presse-papiers!
ScreenLog
is the default if none of the following settings are present in the configuration. It's an error to include settings that imply more than one log implementation.
Default/Global Setting | Component Action |
---|---|
ScreenLogShowEvents
|
Use a ScreenLog
|
ScreenLogShowIncoming
|
Use a ScreenLog
|
ScreenLogShowOutgoing
|
Use a ScreenLog
|
SLF4J*
|
Camel 2.6+. Use a SLF4JLog . Any of the SLF4J settings will cause this log to be used.
|
FileLogPath
|
Use a FileLog
|
JdbcDriver
|
Use a JdbcLog
|
Message Store Copier lienLien copié sur presse-papiers!
MemoryStore
is the default if none of the following settings are present in the configuration. It's an error to include settings that imply more than one message store implementation.
Default/Global Setting | Component Action |
---|---|
JdbcDriver
|
Use a JdbcStore
|
FileStorePath
|
Use a FileStore
|
SleepycatDatabaseDir
|
Use a SleepcatStore
|
Message Factory Copier lienLien copié sur presse-papiers!
DefaultMessageFactory
. However, advanced applications may require a custom message factory. This can be set on the QuickFIX/J component.
JMX Copier lienLien copié sur presse-papiers!
Default/Global Setting | Component Action |
---|---|
UseJmx
|
if Y , then enable QuickFIX/J JMX
|
Other Defaults Copier lienLien copié sur presse-papiers!
SessionStartTime
and SessionEndTime
default to "00:00:00", meaning the session will not be automatically started and stopped. The HeartBtInt
(heartbeat interval) defaults to 30 seconds.
Minimal Initiator Configuration Example Copier lienLien copié sur presse-papiers!
[SESSION] ConnectionType=initiator BeginString=FIX.4.4 SenderCompID=YOUR_SENDER TargetCompID=YOUR_TARGET
[SESSION]
ConnectionType=initiator
BeginString=FIX.4.4
SenderCompID=YOUR_SENDER
TargetCompID=YOUR_TARGET
Using the InOut Message Exchange Pattern Copier lienLien copié sur presse-papiers!
Implementing InOut Exchanges for Consumers Copier lienLien copié sur presse-papiers!
MessageOrderStatusService
in the example below is a bean with a synchronous service method. The method returns the response to the request (an ExecutionReport in this case) which is then sent back to the requestor session.
from("quickfix:examples/inprocess.cfg?sessionID=FIX.4.2:MARKET->TRADER&exchangePattern=InOut") .filter(header(QuickfixjEndpoint.MESSAGE_TYPE_KEY).isEqualTo(MsgType.ORDER_STATUS_REQUEST)) .bean(new MarketOrderStatusService());
from("quickfix:examples/inprocess.cfg?sessionID=FIX.4.2:MARKET->TRADER&exchangePattern=InOut")
.filter(header(QuickfixjEndpoint.MESSAGE_TYPE_KEY).isEqualTo(MsgType.ORDER_STATUS_REQUEST))
.bean(new MarketOrderStatusService());
Implementing InOut Exchanges for Producers Copier lienLien copié sur presse-papiers!
Exchange
properties.
Description | Key String | Key Constant | Default | Correlation Criteria | "CorrelationCriteria" | QuickfixjProducer.CORRELATION_CRITERIA_KEY | None | |
---|---|---|---|---|---|---|---|---|
Correlation Timeout in Milliseconds | "CorrelationTimeout" | QuickfixjProducer.CORRELATION_TIMEOUT_KEY | 1000 |
MessagePredicate
object. The following example will treat a FIX ExecutionReport from the specified session where the transaction type is STATUS and the Order ID matches our request. The session ID should be for the requestor, the sender and target CompID fields will be reversed when looking for the reply.
Example Copier lienLien copié sur presse-papiers!
RequestReplyExample
that demonstrates the InOut exchanges for a consumer and producer. This example creates a simple HTTP server endpoint that accepts order status requests. The HTTP request is converted to a FIX OrderStatusRequestMessage, is augmented with a correlation criteria, and is then routed to a quickfix endpoint. The response is then converted to a JSON-formatted string and sent back to the HTTP server endpoint to be provided as the web response.
Spring Configuration Copier lienLien copié sur presse-papiers!
FactoryBean
for configuring the session settings within a Spring context. A type converter for QuickFIX/J session ID strings is also included. The following example shows a simple configuration of an acceptor and initiator session with default settings for both sessions.
QuickfixjConfiguration
class for configuring the session settings. A type converter for QuickFIX/J session ID strings is also included. The following example shows a simple configuration of an acceptor and initiator session with default settings for both sessions.
Exception handling Copier lienLien copié sur presse-papiers!
RejectLogon
exception is thrown while processing an incoming logon administrative message, then the logon will be rejected.
FIX Sequence Number Management Copier lienLien copié sur presse-papiers!
SessionLogon
event category and signals the application to start sending messages.
Route Examples Copier lienLien copié sur presse-papiers!
from("quickfix:examples/inprocess.cfg?sessionID=FIX.4.2:MARKET->TRADER"). filter(header(QuickfixjEndpoint.EVENT_CATEGORY_KEY).isEqualTo(QuickfixjEventCategory.AppMessageReceived)). to("trade-executor:market");
from("quickfix:examples/inprocess.cfg?sessionID=FIX.4.2:MARKET->TRADER").
filter(header(QuickfixjEndpoint.EVENT_CATEGORY_KEY).isEqualTo(QuickfixjEventCategory.AppMessageReceived)).
to("trade-executor:market");
from("trade-executor:market").to("quickfix:examples/inprocess.cfg");
from("trade-executor:market").to("quickfix:examples/inprocess.cfg");
from("quickfix:examples/inprocess.cfg?sessionID=FIX.4.2:TRADER->MARKET"). filter(header(QuickfixjEndpoint.MESSAGE_TYPE_KEY).isEqualTo(MsgType.EXECUTION_REPORT)). bean(new MyTradeExecutionProcessor());
from("quickfix:examples/inprocess.cfg?sessionID=FIX.4.2:TRADER->MARKET").
filter(header(QuickfixjEndpoint.MESSAGE_TYPE_KEY).isEqualTo(MsgType.EXECUTION_REPORT)).
bean(new MyTradeExecutionProcessor());
QuickFIX/J Component Prior to Camel 2.5 Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
quickfix-server:config file quickfix-client:config file
quickfix-server:config file
quickfix-client:config file
Exchange data format Copier lienLien copié sur presse-papiers!
Samples Copier lienLien copié sur presse-papiers!
<route> <from uri="activemq:queue:fix"/> <bean ref="fixService" method="createFixMessage" /> // bean method in charge to transform message into a QuickFix.Message <to uri="quickfix-client:META-INF/quickfix/client.cfg" /> // Quickfix engine who will send the FIX messages to the gateway </route>
<route>
<from uri="activemq:queue:fix"/>
<bean ref="fixService" method="createFixMessage" /> // bean method in charge to transform message into a QuickFix.Message
<to uri="quickfix-client:META-INF/quickfix/client.cfg" /> // Quickfix engine who will send the FIX messages to the gateway
</route>
<route> <from uri="quickfix-server:META-INF/quickfix/server.cfg"/> // QuickFix engine who will receive the message from FIX gateway <bean ref="fixService" method="parseFixMessage" /> // bean method parsing the QuickFix.Message <to uri="uri="activemq:queue:fix"/>" /> </route>
<route>
<from uri="quickfix-server:META-INF/quickfix/server.cfg"/> // QuickFix engine who will receive the message from FIX gateway
<bean ref="fixService" method="parseFixMessage" /> // bean method parsing the QuickFix.Message
<to uri="uri="activemq:queue:fix"/>" />
</route>
Chapter 81. Ref Copier lienLien copié sur presse-papiers!
Ref Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
ref:someName
ref:someName
someName
would be the bean ID of an endpoint in the Spring registry.
Runtime lookup Copier lienLien copié sur presse-papiers!
<camelContext id="camel" xmlns="http://activemq.apache.org/camel/schema/spring"> <endpoint id="normalOrder" uri="activemq:order.slow"/> <endpoint id="bigspenderOrder" uri="activemq:order.high"/> ... </camelContext>
<camelContext id="camel" xmlns="http://activemq.apache.org/camel/schema/spring">
<endpoint id="normalOrder" uri="activemq:order.slow"/>
<endpoint id="bigspenderOrder" uri="activemq:order.high"/>
...
</camelContext>
Sample Copier lienLien copié sur presse-papiers!
ref:
in the URI to reference the endpoint with the spring ID, endpoint2
:
ref
attribute instead:
<to ref="endpoint2"/>
<to ref="endpoint2"/>
Chapter 82. Restlet Copier lienLien copié sur presse-papiers!
Restlet Component Copier lienLien copié sur presse-papiers!
APPLICATION_JAVA_OBJECT
and APPLICATION_JAVA_OBJECT_XML
media types are not safe to use from a security perspective. There is a weakness in the XML deserialization mechanism used by these media types, which allows a remote attacker to force the JVM to execute unwanted Java code embedded inside a specially-crafted request to the REST endpoint. By default, camel-restlet
uses the APPLICATION_WWW_FORM
media type, which is not affected by this issue. It is possible to change the media type by setting the Content-Type
message header. If you do so, it is important to ensure you do not use the APPLICATION_JAVA_OBJECT
and APPLICATION_JAVA_OBJECT_XML
media types. These media types will be disabled entirely in a future release.
URI format Copier lienLien copié sur presse-papiers!
restlet:restletUrl[?options]
restlet:restletUrl[?options]
protocol://hostname[:port][/resourcePattern]
protocol://hostname[:port][/resourcePattern]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
headerFilterStrategy=#refName
|
An instance of RestletHeaderFilterStrategy
|
Use the # notation (headerFilterStrategy=#refName ) to reference a header filter strategy in the Camel Registry. The strategy will be plugged into the restlet binding if it is HeaderFilterStrategyAware .
|
restletBinding=# refName
|
An instance of DefaultRestletBinding
|
The bean ID of a RestletBinding object in the Camel Registry.
|
restletMethod
|
GET
|
On a producer endpoint, specifies the request method to use. On a consumer endpoint, specifies that the endpoint consumes only restletMethod requests. The string value is converted to org.restlet.data.Method by the Method.valueOf(String) method.
|
restletMethod
|
GET
|
On a producer endpoint, specifies the request method to use. On a consumer endpoint, specifies that the endpoint consumes only restletMethod requests. The string value is converted to org.restlet.data.Method by the Method.valueOf(String) method.
|
restletMethods
|
None |
Consumer only Specify one or more methods separated by commas (e.g. restletMethods=post,put ) to be serviced by a restlet consumer endpoint. If both restletMethod and restletMethods options are specified, the restletMethod setting is ignored.
|
restletUriPatterns=#refName
|
None |
Consumer only Specify one ore more URI templates to be serviced by a restlet consumer endpoint, using the # notation to reference a List<String> in the Camel Registry. If a URI pattern has been defined in the endpoint URI, both the URI pattern defined in the endpoint and the restletUriPatterns option will be honored.
|
throwExceptionOnFailure (2.6 or later)
|
true
|
Producer only Throws exception on a producer failure. |
Component Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
controllerDaemon
|
true
|
*Camel 2.10:* Indicates if the controller thread should be a daemon (not blocking JVM exit). |
controllerSleepTimeMs
|
100
|
*Camel 2.10:* Time for the controller thread to sleep between each control. |
inboundBufferSize
|
8192
|
*Camel 2.10:* The size of the buffer when reading messages. |
minThreads
|
1
|
*Camel 2.10:* Minimum threads waiting to service requests. |
maxThreads
|
10
|
*Camel 2.10:* Maximum threads that will service requests. |
maxConnectionsPerHost
|
-1
|
*Camel 2.10:* Maximum number of concurrent connections per host (IP address). |
maxTotalConnections
|
-1
|
*Camel 2.10:* Maximum number of concurrent connections in total. |
outboundBufferSize
|
8192
|
*Camel 2.10:* The size of the buffer when writing messages. |
persistingConnections
|
true
|
*Camel 2.10:* Indicates if connections should be kept alive after a call. |
pipeliningConnections
|
false
|
*Camel 2.10:* Indicates if pipelining connections are supported. |
threadMaxIdleTimeMs
|
60000
|
*Camel 2.10:* Time for an idle thread to wait for an operation before being collected. |
useForwardedForHeader
|
false
|
*Camel 2.10:* Lookup the "X-Forwarded-For" header supported by popular proxies and caches and uses it to populate the Request.getClientAddresses() method result. This information is only safe for intermediary components within your local network. Other addresses could easily be changed by setting a fake header and should not be trusted for serious security checks. |
Message Headers Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
CamelContentType
|
String
|
Specifies the content type, which can be set on the OUT message by the application/processor. The value is the content-type of the response message. If this header is not set, the content-type is based on the object type of the OUT message body. In Camel 2.3 onward, if the Content-Type header is specified in the Camel IN message, the value of the header determine the content type for the Restlet request message. nbsp; Otherwise, it is defaulted to "application/x-www-form-urlencoded'. Prior to release 2.3, it is not possible to change the request content type default.
|
CamelAcceptContentType
|
String
|
*Since Camel 2.9.3, 2.10.0:* The HTTP Accept request header. |
CamelHttpMethod
|
String
|
The HTTP request method. This is set in the IN message header. |
CamelHttpQuery
|
String
|
The query string of the request URI. It is set on the IN message by DefaultRestletBinding when the restlet component receives a request.
|
CamelHttpResponseCode
|
String or Integer
|
The response code can be set on the OUT message by the application/processor. The value is the response code of the response message. If this header is not set, the response code is set by the restlet runtime engine. |
CamelHttpUri
|
String
|
The HTTP request URI. This is set in the IN message header. |
CamelRestletLogin
|
String
|
Login name for basic authentication. It is set on the IN message by the application and gets filtered before the restlet request header by Apache Camel. |
CamelRestletPassword
|
String
|
Password name for basic authentication. It is set on the IN message by the application and gets filtered before the restlet request header by Apache Camel. |
CamelRestletRequest
|
Request
|
Camel 2.8: The org.restlet.Request object which holds all request details.
|
CamelRestletResponse
|
Response
|
Camel 2.8: The org.restlet.Response object. You can use this to create responses using the API from Restlet. See examples below.
|
org.restlet.*
|
Attributes of a Restlet message that get propagated to Apache Camel IN headers. |
Message Body Copier lienLien copié sur presse-papiers!
Restlet Endpoint with Authentication Copier lienLien copié sur presse-papiers!
restlet
consumer endpoint that listens for POST
requests on http://localhost:8080 . The processor creates a response that echoes the request body and the value of the id
header.
restletRealm
setting in the URI query is used to look up a Realm Map in the registry. If this option is specified, the restlet consumer uses the information to authenticate user logins. Only authenticated requests can access the resources. In this sample, we create a Spring application context that serves as a registry. The bean ID of the Realm Map should match the restletRealmRef.
<util:map id="realm"> <entry key="admin" value="foo" /> <entry key="bar" value="foo" /> </util:map>
<util:map id="realm">
<entry key="admin" value="foo" />
<entry key="bar" value="foo" />
</util:map>
direct
endpoint that sends requests to the server on http://localhost:8080 (that is, our restlet consumer endpoint).
// Note: restletMethod and restletRealmRef are stripped // from the query before a request is sent as they are // only processed by Camel. from("direct:start-auth").to("restlet:http://localhost:9080/securedOrders?restletMethod=post");
// Note: restletMethod and restletRealmRef are stripped
// from the query before a request is sent as they are
// only processed by Camel.
from("direct:start-auth").to("restlet:http://localhost:9080/securedOrders?restletMethod=post");
direct:start-auth
endpoint with the following headers:
CamelRestletLogin
(used internally by Apache Camel)CamelRestletPassword
(used internally by Apache Camel)id
(application header)
org.apache.camel.restlet.auth.login
and org.apache.camel.restlet.auth.password
will not be propagated as Restlet header.
received [<order foo='1'/>] as an order id = 89531
received [<order foo='1'/>] as an order id = 89531
Single restlet endpoint to service multiple methods and URI templates (2.0 or later) Copier lienLien copié sur presse-papiers!
restletMethods
option. This snippet also shows how to retrieve the request method from the header:
restletUriPatterns
option. The request URI is available in the header of the IN message as well. If a URI pattern has been defined in the endpoint URI (which is not the case in this sample), both the URI pattern defined in the endpoint and the restletUriPatterns
option will be honored.
restletUriPatterns=#uriTemplates
option references the List<String>
bean defined in the Spring XML configuration.
<util:list id="uriTemplates"> <value>/users/{username}</value> <value>/atom/collection/{id}/component/{cid}</value> </util:list>
<util:list id="uriTemplates">
<value>/users/{username}</value>
<value>/atom/collection/{id}/component/{cid}</value>
</util:list>
Using Restlet API to populate response Copier lienLien copié sur presse-papiers!
org.restlet.Response
API to populate the response. This gives you full access to the Restlet API and fine grained control of the response. See the route snippet below where we generate the response from an inlined Camel Processor:
Using the Restlet servlet within a webapp Copier lienLien copié sur presse-papiers!
"Request type : GET and ID : 1234"
"Request type : GET and ID : 1234"
<dependency> <groupId>org.restlet.jee</groupId> <artifactId>org.restlet.ext.spring</artifactId> <version>${restlet-version}</version> </dependency>
<dependency>
<groupId>org.restlet.jee</groupId>
<artifactId>org.restlet.ext.spring</artifactId>
<version>${restlet-version}</version>
</dependency>
<repository> <id>maven-restlet</id> <name>Public online Restlet repository</name> <url>http://maven.restlet.org</url> </repository>
<repository>
<id>maven-restlet</id>
<name>Public online Restlet repository</name>
<url>http://maven.restlet.org</url>
</repository>
Chapter 83. RMI Copier lienLien copié sur presse-papiers!
RMI Component Copier lienLien copié sur presse-papiers!
Remote
objects.
URI format Copier lienLien copié sur presse-papiers!
rmi://rmi-regisitry-host:rmi-registry-port/registry-path[?options]
rmi://rmi-regisitry-host:rmi-registry-port/registry-path[?options]
rmi://localhost:1099/path/to/service
rmi://localhost:1099/path/to/service
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
method
|
null
|
As of Apache Camel 1.3, you can set the name of the method to invoke. |
remoteInterfaces
|
null
|
Its now possible to use this option from Camel 2.7: in the XML DSL. It can be a list of interface names separated by comma. |
Using Copier lienLien copié sur presse-papiers!
from("pojo:foo").to("rmi://localhost:1099/foo");
from("pojo:foo").to("rmi://localhost:1099/foo");
RmiEndpoint endpoint= (RmiEndpoint) endpoint("rmi://localhost:1099/bar"); endpoint.setRemoteInterfaces(ISay.class); from(endpoint).to("pojo:bar");
RmiEndpoint endpoint= (RmiEndpoint) endpoint("rmi://localhost:1099/bar");
endpoint.setRemoteInterfaces(ISay.class);
from(endpoint).to("pojo:bar");
Remote
interfaces exposed.
<camel:route> <from uri="rmi://localhost:37541/helloServiceBean?remoteInterfaces=org.apache.camel.example.osgi.HelloService"/> <to uri="bean:helloServiceBean"/> </camel:route>
<camel:route>
<from uri="rmi://localhost:37541/helloServiceBean?remoteInterfaces=org.apache.camel.example.osgi.HelloService"/>
<to uri="bean:helloServiceBean"/>
</camel:route>
Chapter 84. Routebox Copier lienLien copié sur presse-papiers!
Routebox Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
The need for a Camel Routebox endpoint Copier lienLien copié sur presse-papiers!
- a large collection of routes and
- involving a wide set of endpoint technologies needing integration in different ways
- Coarse grained or higher level routes - aggregated collection of inner or lower level routes exposed as Routebox endpoints that represent an integration focus area. For example:
Expand Focus Area Coarse-Grained Route Example Department Focus HR routes, Sales routes etc Supply chain & B2B Focus Shipping routes, Fulfillment routes, 3rd party services etc Technology Focus Database routes, JMS routes, Scheduled batch routes etc - Fine grained routes - routes that execute a singular and specific business and/or integration pattern.
URI format Copier lienLien copié sur presse-papiers!
routebox:routeboxname[?options]
routebox:routeboxname[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
dispatchStrategy
|
null
|
A string representing a key in the Camel Registry matching an object value implementing the interface org.apache.camel.component.routebox.strategy.RouteboxDispatchStrategy |
dispatchMap
|
null
|
A string representing a key in the Camel Registry matching an object value of the type HashMap<String, String>. The HashMap key should contain strings that can be matched against the value set for the exchange header ROUTE_DISPATCH_KEY. The HashMap value should contain inner route consumer URI's to which requests should be directed. |
innerContext
|
auto created
|
A string representing a key in the Camel Registry matching an object value of the type org.apache.camel.CamelContext. If a CamelContext is not provided by the user a CamelContext is automatically created for deployment of inner routes. |
innerRegistry
|
null
|
A string representing a key in the Camel Registry matching an object value that implements the interface org.apache.camel.spi.Registry. If Registry values are utilized by inner routes to create endpoints, an innerRegistry parameter must be provided |
routeBuilders
|
empty List
|
A string representing a key in the Camel Registry matching an object value of the type List<org.apache.camel.builder.RouteBuilder>. If the user does not supply an innerContext pre-primed with inner routes, the routeBuilders option must be provided as a non-empty list of RouteBuilders containing inner routes |
innerProtocol
|
Direct
|
The Protocol used internally by the Routebox component. Can be Direct or SEDA. The Routebox component currently offers protocols that are JVM bound. |
sendToConsumer
|
true
|
Dictates whether a Producer endpoint sends a request to an external routebox consumer. If the setting is false, the Producer creates an embedded inner context and processes requests internally. |
forkContext
|
true
|
The Protocol used internally by the Routebox component. Can be Direct or SEDA. The Routebox component currently offers protocols that are JVM bound. |
threads
|
20
|
Number of threads to be used by the routebox to receive requests. Setting applicable only for innerProtocol SEDA. |
queueSize
|
unlimited
|
Create a fixed size queue to receive requests. Setting applicable only for innerProtocol SEDA. |
Sending/Receiving Messages to/from the routebox Copier lienLien copié sur presse-papiers!
Step 1: Loading inner route details into the Registry Copier lienLien copié sur presse-papiers!
Step 2: Optionaly using a Dispatch Strategy instead of a Dispatch Map Copier lienLien copié sur presse-papiers!
Step 2: Launching a routebox consumer Copier lienLien copié sur presse-papiers!
Step 3: Using a routebox producer Copier lienLien copié sur presse-papiers!
Chapter 85. RSS Copier lienLien copié sur presse-papiers!
RSS Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
rss:rssUri
rss:rssUri
rssUri
is the URI to the RSS feed to poll.
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Property | Default | Description |
---|---|---|
splitEntries
|
true
|
If true , Apache Camel splits a feed into its individual entries and returns each entry, poll by poll. For example, if a feed contains seven entries, Apache Camel returns the first entry on the first poll, the second entry on the second poll, and so on. When no more entries are left in the feed, Apache Camel contacts the remote RSS URI to obtain a new feed. If false , Apache Camel obtains a fresh feed on every poll and returns all of the feed's entries.
|
filter
|
true
|
Use in combination with the splitEntries option in order to filter returned entries. By default, Apache Camel applies the UpdateDateFilter filter, which returns only new entries from the feed, ensuring that the consumer endpoint never receives an entry more than once. The filter orders the entries chronologically, with the newest returned last.
|
throttleEntries
|
true
|
Camel 2.5: Sets whether all entries identified in a single feed poll should be delivered immediately. If true, only one entry is processed per consumer.delay. Only applicable when splitEntries is set to true. |
lastUpdate
|
null
|
Use in combination with the filter option to block entries earlier than a specific date/time (uses the entry.updated timestamp). The format is: yyyy-MM-ddTHH:MM:ss . Example: 2007-12-24T17:45:59 .
|
feedHeader
|
true
|
Specifies whether to add the ROME SyndFeed object as a header.
|
sortEntries
|
false
|
If splitEntries is true , this specifies whether to sort the entries by updated date.
|
consumer.delay
|
60000
|
Delay in milliseconds between each poll. |
consumer.initialDelay
|
1000
|
Milliseconds before polling starts. |
consumer.userFixedDelay
|
false
|
Set to true to use fixed delay between pools, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
|
Exchange data types Copier lienLien copié sur presse-papiers!
SyndFeed
. Depending on the value of the splitEntries
flag, Apache Camel returns either a SyndFeed
with one SyndEntry
or a java.util.List
of SyndEntrys
.
Option | Value | Behavior |
---|---|---|
splitEntries
|
true
|
A single entry from the current feed is set in the exchange. |
splitEntries
|
false
|
The entire list of entries from the current feed is set in the exchange. |
Message Headers Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelRssFeed
|
Apache Camel 2.0: The entire SyncFeed object.
|
RSS Dataformat Copier lienLien copié sur presse-papiers!
- marshal = from ROME
SyndFeed
to XMLString
- unmarshal = from XML
String
to ROMESyndFeed
from("rss:file:src/test/data/rss20.xml?splitEntries=false&consumer.delay=1000").marshal().rss().to("mock:marshal");
from("rss:file:src/test/data/rss20.xml?splitEntries=false&consumer.delay=1000").marshal().rss().to("mock:marshal");
// only entries with Apache Camel in the title will get through the filter from("rss:file:src/test/data/rss20.xml?splitEntries=true&consumer.delay=100") .marshal().rss().filter().xpath("//item/title[contains(.,'Camel')]").to("mock:result");
// only entries with Apache Camel in the title will get through the filter
from("rss:file:src/test/data/rss20.xml?splitEntries=true&consumer.delay=100")
.marshal().rss().filter().xpath("//item/title[contains(.,'Camel')]").to("mock:result");
alt=rss
, then you can for example do from("rss:http://someserver.com/feeds/posts/default?alt=rss&splitEntries=false&consumer.delay=1000").to("bean:rss");
Filtering entries Copier lienLien copié sur presse-papiers!
// only entries with Camel in the title will get through the filter from("rss:file:src/test/data/rss20.xml?splitEntries=true&consumer.delay=100"). filter().method("myFilterBean", "titleContainsCamel").to("mock:result");
// only entries with Camel in the title will get through the filter
from("rss:file:src/test/data/rss20.xml?splitEntries=true&consumer.delay=100").
filter().method("myFilterBean", "titleContainsCamel").to("mock:result");
See also Copier lienLien copié sur presse-papiers!
Chapter 86. SEDA Copier lienLien copié sur presse-papiers!
SEDA Component Copier lienLien copié sur presse-papiers!
CamelContext
instances (for example, communicating between Web applications), see the VM component.
URI format Copier lienLien copié sur presse-papiers!
seda:queueName[?options]
seda:queueName[?options]
queueName
can be any string that uniquely identifies the endpoint within the current CamelContext.
?option=value&option=value&...
queueName
is considered and any option settings are ignored. That is, the identity of a consumer endpoint depends only on the queueName
. If you want to attach multiple consumers to the same queue, use the approach described in the section called “Using multipleConsumers”.
Options Copier lienLien copié sur presse-papiers!
Name | Default | Description |
---|---|---|
size
|
Unbounded |
The maximum size (= capacity of the number of messages it can max hold) of the SEDA queue. The default value in Camel 2.2 or older is 1000 . From Camel 2.3 onwards the size is unbounded by default.
|
concurrentConsumers
|
1
|
Apache Camel 1.6.1/2.0: Number of concurrent threads processing exchanges. |
waitForTaskToComplete
|
IfReplyExpected
|
Apache Camel 2.0: Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: Always , Never or IfReplyExpected . The first two values are self-explanatory. The last value, IfReplyExpected , will only wait if the message is Request Reply based. The default option is IfReplyExpected . See more information about Async messaging.
|
timeout
|
30000
|
Apache Camel 2.0: Timeout in millis a seda producer will at most waiting for an async task to complete. See waitForTaskToComplete and Async for more details. In Camel 2.2 you can now disable timeout by using 0 or a negative value.
|
multipleConsumers
|
false
|
Camel 2.2: Specifies whether multiple consumers are allowed or not. If enabled, you can use SEDA for a publish/subscribe style of messaging. Send a message to a SEDA queue and have multiple consumers receive a copy of the message. |
limitConcurrentConsumers
|
true
|
Camel 2.3: Whether to limit the concurrentConsumers to maximum 500. If its configured with a higher number an exception will be thrown. You can disable this check by turning this option off. |
Changes in Apache Camel 2.0 Copier lienLien copié sur presse-papiers!
from("mina:tcp://0.0.0.0:9876?textline=true&sync=true").to("seda:input"); from("seda:input").to("bean:processInput").to("bean:createResponse");
from("mina:tcp://0.0.0.0:9876?textline=true&sync=true").to("seda:input");
from("seda:input").to("bean:processInput").to("bean:createResponse");
seda:input
queue. As it is a Request Reply message, we wait for the response. When the consumer on the seda:input
queue is complete, it copies the response to the original message response.
Concurrent consumers Copier lienLien copié sur presse-papiers!
from("seda:stageName?concurrentConsumers=5").process(...)
from("seda:stageName?concurrentConsumers=5").process(...)
Difference between thread pools and concurrent consumers Copier lienLien copié sur presse-papiers!
Thread pools Copier lienLien copié sur presse-papiers!
from("seda:stageName").thread(5).process(...)
from("seda:stageName").thread(5).process(...)
BlockQueues
: one from the SEDA endpoint, and one from the workqueue of the thread pool, which may not be what you want. Instead, you might want to consider configuring a Direct endpoint with a thread pool, which can process messages both synchronously and asynchronously. For example:
from("direct:stageName").thread(5).process(...)
from("direct:stageName").thread(5).process(...)
concurrentConsumers
option.
Sample Copier lienLien copié sur presse-papiers!
Object out = template.requestBody("direct:start", "Hello World"); assertEquals("OK", out);
Object out = template.requestBody("direct:start", "Hello World");
assertEquals("OK", out);
mock
endpoint where we can do assertions in the unit test.
Using multipleConsumers Copier lienLien copié sur presse-papiers!
Extracting queue information. Copier lienLien copié sur presse-papiers!
SedaEndpoint seda = context.getEndpoint("seda:xxxx"); int size = seda.getExchanges().size()
SedaEndpoint seda = context.getEndpoint("seda:xxxx");
int size = seda.getExchanges().size()
Chapter 87. SERVLET Copier lienLien copié sur presse-papiers!
Servlet Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
servlet://relative_path[?options]
servlet://relative_path[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
httpBindingRef
|
null
|
Reference to an org.apache.camel.component.http.HttpBinding in the Registry. A HttpBinding implementation can be used to customize how to write a response.
|
matchOnUriPrefix
|
false
|
Whether or not the CamelServlet should try to find a target consumer by matching the URI prefix, if no exact match is found.
|
servletName
|
null
|
Specifies the servlet name that the servlet endpoint will bind to. If there is no servlet name specified, the servlet endpoint will be bind to first published Servlet |
Message Headers Copier lienLien copié sur presse-papiers!
request.parameter
and request.headers
. For example, if a client request has the URL, http://myserver/myserver?orderid=123
, the exchange will contain a header named orderid
with the value 123.
Usage Copier lienLien copié sur presse-papiers!
Sample Copier lienLien copié sur presse-papiers!
http://localhost:8080/camel/services/hello
. First, you need to publish the CamelHttpTransportServlet through the normal Web Container, or OSGi Service. Use the Web.xml
file to publish the CamelHttpTransportServlet as follows:
camel-servlet
endpoint uses the relative path to specify the endpoint's URL. A client can access the camel-servlet
endpoint through the servlet publish address: ("http://localhost:8080/camel/services") + RELATIVE_PATH("/hello")
.
Sample when using Spring 3.x Copier lienLien copié sur presse-papiers!
examples/camel-example-servlet-tomcat
directory. When deploying a Servlet component in the Web container, it is necessary to create a Spring application context explicitly by creating a Spring ContextLoaderListener
instance in the WEB-INF/web.xml
file.
camelContext
and route definitions) from the camel-config.xml
file, define a web.xml
file as follows:
Sample when using Spring 2.x Copier lienLien copié sur presse-papiers!
ContextLoaderServlet
instead of ContextLoaderListener
. In that case you'll need to start ContextLoaderServlet
after CamelHttpTransportServlet like this:
Sample when using OSGi Copier lienLien copié sur presse-papiers!
Activator
to publish the CamelHttpTransportServlet on the OSGi platform
Chapter 88. Shiro Security Copier lienLien copié sur presse-papiers!
Shiro Security Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
Shiro Security Basics Copier lienLien copié sur presse-papiers!
Instantiating a ShiroSecurityPolicy Object Copier lienLien copié sur presse-papiers!
ShiroSecurityPolicy Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Type | Description |
---|---|---|---|
iniResourcePath or ini
|
none
|
Resource String or Ini Object | A mandatory Resource String for the iniResourcePath or an instance of an Ini object must be passed to the security policy. Resources can be acquired from the file system, classpath, or URLs when prefixed with "file:, classpath:, or url:" respectively. For e.g "classpath:shiro.ini" |
passPhrase
|
An AES 128 based key
|
byte[] | A passPhrase to decrypt ShiroSecurityToken(s) sent along with Message Exchanges |
alwaysReauthenticate
|
true
|
boolean | Setting to ensure re-authentication on every individual request. If set to false, the user is authenticated and locked such than only requests from the same user going forward are authenticated. |
permissionsList
|
none
|
List<Permission> | A List of permissions required in order for an authenticated user to be authorized to perform further action i.e continue further on the route. If no Permissions list is provided to the ShiroSecurityPolicy object, then authorization is deemed as not required |
cipherService
|
AES
|
org.apache.shiro.crypto.CipherService | Shiro ships with AES & Blowfish based CipherServices. You may use one these or pass in your own Cipher implementation |
Applying Shiro Authentication on a Camel Route Copier lienLien copié sur presse-papiers!
Applying Shiro Authorization on a Camel Route Copier lienLien copié sur presse-papiers!
Creating a ShiroSecurityToken and injecting it into a Message Exchange Copier lienLien copié sur presse-papiers!
Sending Messages to routes secured by a ShiroSecurityPolicy Copier lienLien copié sur presse-papiers!
Chapter 89. Sip Copier lienLien copié sur presse-papiers!
SIP Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
sip://johndoe@localhost:99999[?options] sips://johndoe@localhost:99999/[?options]
sip://johndoe@localhost:99999[?options]
sips://johndoe@localhost:99999/[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
stackName
|
NAME_NOT_SET
|
Name of the SIP Stack instance associated with an SIP Endpoint. |
transport
|
tcp
|
Setting for choice of transport potocol. Valid choices are "tcp" or "udp". |
fromUser
|
Username of the message originator. Mandatory setting unless a registry based custom FromHeader is specified. | |
fromHost
|
Hostname of the message originator. Mandatory setting unless a registry based FromHeader is specified | |
fromPort
|
Port of the message originator. Mandatory setting unless a registry based FromHeader is specified | |
toUser
|
Username of the message receiver. Mandatory setting unless a registry based custom ToHeader is specified. | |
toHost
|
Hostname of the message receiver. Mandatory setting unless a registry based ToHeader is specified | |
toPort
|
Portname of the message receiver. Mandatory setting unless a registry based ToHeader is specified | |
maxforwards
|
0 | the number of intermediaries that may forward the message to the message receiver. Optional setting. May alternatively be set using as registry based MaxForwardsHeader |
eventId
|
Setting for a String based event Id. Mandatory setting unless a registry based FromHeader is specified | |
eventHeaderName
|
Setting for a String based event Id. Mandatory setting unless a registry based FromHeader is specified | |
maxMessageSize
|
1048576
|
Setting for maximum allowed Message size in bytes. |
cacheConnections
|
false
|
Should connections be cached by the SipStack to reduce cost of connection creation. This is useful if the connection is used for long running conversations. |
consumer
|
false
|
This setting is used to determine whether the kind of header (FromHeader,ToHeader etc) that needs to be created for this endpoint |
automaticDialogSupport
|
off
|
Setting to specify whether every communication should be associated with a dialog. |
contentType
|
text
|
Setting for contentType can be set to any valid MimeType. |
contentSubType
|
xml
|
Setting for contentSubType can be set to any valid MimeSubType. |
receiveTimeoutMillis
|
10000
|
Setting for specifying amount of time to wait for a Response and/or Acknowledgement can be received from another SIP stack |
useRouterForAllUris
|
false
|
This setting is used when requests are sent to the Presence Agent via a proxy. |
msgExpiration
|
3600
|
The amount of time a message received at an endpoint is considered valid |
presenceAgent
|
false
|
This setting is used to distingish between a Presence Agent & a consumer. This is due to the fact that the SIP Camel component ships with a basic Presence Agent (for testing purposes only). Consumers have to set this flag to true. |
Registry based Options Copier lienLien copié sur presse-papiers!
Name | Description |
---|---|
fromHeader
|
a custom Header object containing message originator settings. Must implement the type javax.sip.header.FromHeader |
toHeader
|
a custom Header object containing message receiver settings. Must implement the type javax.sip.header.ToHeader |
viaHeaders
|
List of custom Header objects of the type javax.sip.header.ViaHeader. Each ViaHeader containing a proxy address for request forwarding. (Note this header is automatically updated by each proxy when the request arrives at its listener) |
contentTypeHeader
|
a custom Header object containing message content details. Must implement the type javax.sip.header.ContentTypeHeader |
callIdHeader
|
a custom Header object containing call details. Must implement the type javax.sip.header.CallIdHeader |
maxForwardsHeader
|
a custom Header object containing details on maximum proxy forwards. This header places a limit on the viaHeaders possible. Must implement the type javax.sip.header.MaxForwardsHeader |
eventHeader
|
a custom Header object containing event details. Must implement the type javax.sip.header.EventHeader |
contactHeader
|
an optional custom Header object containing verbose contact details (email, phone number etc). Must implement the type javax.sip.header.ContactHeader |
expiresHeader
|
a custom Header object containing message expiration details. Must implement the type javax.sip.header.ExpiresHeader |
extensionHeader
|
a custom Header object containing user/application specific details. Must implement the type javax.sip.header.ExtensionHeader |
Sending Messages to/from a SIP endpoint Copier lienLien copié sur presse-papiers!
Creating a Camel SIP Publisher Copier lienLien copié sur presse-papiers!
- using a SIP Stack named client
- using a registry based eventHeader called evtHdrName
- using a registry based eventId called evtId
- from a SIP Stack with Listener set up as user2@localhost:3534
- The Event being published is EVENT_A
- A Mandatory Header called REQUEST_METHOD is set to Request.Publish thereby setting up the endpoint as a Event publisher"
Creating a Camel SIP Subscriber Copier lienLien copié sur presse-papiers!
- using a SIP Stack named Subscriber
- registering with a Presence Agent user called agent@localhost:5152
- using a registry based eventHeader called evtHdrName. The evtHdrName contains the Event which is se to "Event_A"
- using a registry based eventId called evtId
Chapter 90. SMPP Copier lienLien copié sur presse-papiers!
SMPP Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
smpp://[username@]hostname[:port][?options] smpps://[username@]hostname[:port][?options]
smpp://[username@]hostname[:port][?options]
smpps://[username@]hostname[:port][?options]
smppclient
. If no port number is provided, then Apache Camel will provide the default value 2775
.Camel 2.3: If the protocol name is smpps
, camel-smpp with try to use SSLSocket to init a connection to the server.
?option=value&option=value&...
URI Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
password
|
password
|
Specifies the password to use to log in to the SMSC. |
systemType
|
cp
|
This parameter is used to categorize the type of ESME (External Short Message Entity) that is binding to the SMSC (max. 13 characters). |
dataCoding
|
0
|
Camel 2.5 onwarts Defines encoding of data according the SMPP 3.4 specification, section 5.2.19. Example data encodings are:
0 : SMSC Default Alphabet 4 : 8 bit Alphabet 8 : UCS2 Alphabet
|
encoding
|
ISO-8859-1
|
Defines the encoding scheme of the short message user data. |
enquireLinkTimer
|
5000
|
Defines the interval in milliseconds between the confidence checks. The confidence check is used to test the communication path between an ESME and an SMSC. |
transactionTimer
|
10000
|
Defines the maximum period of inactivity allowed after a transaction, after which an SMPP entity may assume that the session is no longer active. This timer may be active on either communicating SMPP entity (i.e. SMSC or ESME). |
initialReconnectDelay
|
5000
|
Defines the initial delay in milliseconds after the consumer/producer tries to reconnect to the SMSC, after the connection was lost. |
reconnectDelay
|
5000
|
Defines the interval in milliseconds between the reconnect attempts, if the connection to the SMSC was lost and the previous was not succeed. |
registeredDelivery
|
1
|
Is used to request an SMSC delivery receipt and/or SME originated acknowledgements. The following values are defined:
0 : No SMSC delivery receipt requested. 1 : SMSC delivery receipt requested where final delivery outcome is success or failure. 2 : SMSC delivery receipt requested where the final delivery outcome is delivery failure.
|
serviceType
|
CMT
|
The service type parameter can be used to indicate the SMS Application service associated with the message. The following generic service_types are defined:
|
sourceAddr
|
1616
|
Defines the address of SME (Short Message Entity) which originated this message. |
destAddr
|
1717
|
Defines the destination SME address. For mobile terminated messages, this is the directory number of the recipient MS. |
sourceAddrTon
|
0
|
Defines the type of number (TON) to be used in the SME originator address parameters. The following TON values are defined:
|
destAddrTon
|
0
|
Defines the type of number (TON) to be used in the SME destination address parameters. The following TON values are defined:
|
sourceAddrNpi
|
0
|
Defines the numeric plan indicator (NPI) to be used in the SME originator address parameters. The following NPI values are defined:
|
destAddrNpi
|
0
|
Defines the numeric plan indicator (NPI) to be used in the SME destination address parameters. The following NPI values are defined:
|
priorityFlag
|
1
|
Allows the originating SME to assign a priority level to the short message. Four Priority Levels are supported:
|
replaceIfPresentFlag
|
0
|
Used to request the SMSC to replace a previously submitted message, that is still pending delivery. The SMSC will replace an existing message provided that the source address, destination address and service type match the same fields in the new message. The following replace if present flag values are defined:
|
dataCoding
|
0
|
Camel 2.5 onwarts Defines encoding of data according the SMPP 3.4 specification, section 5.2.19. Example data encodings are:
0 : SMSC Default Alphabet 4 : 8 bit Alphabet 8 : UCS2 Alphabet
|
typeOfNumber
|
0
|
Defines the type of number (TON) to be used in the SME. The following TON values are defined:
|
numberingPlanIndicator
|
0
|
Defines the numeric plan indicator (NPI) to be used in the SME. The following NPI values are defined:
|
lazySessionCreation
|
false
|
Camel 2.8 onwarts Sessions can be lazily created to avoid exceptions, if the SMSC is not available when the Camel producer is started. |
CamelSmppSentMessageCount
|
Integer
|
*From Camel 2.9 onwards only for SubmitSm and SubmitMultiSm* The total number of messages which has been sent. |
CamelSmppError
|
Map<String, List<Map<String, Object>>>
|
*From Camel 2.9 onwards only for SubmitMultiSm* The errors which occurred by sending the short message(s) the form Map<String, List<Map<String, Object>>> (messageID : (destAddr : address, error : errorCode)).
|
smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer
smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer
Message Headers Copier lienLien copié sur presse-papiers!
Header | Description |
---|---|
CamelSmppDestAddr
|
Defines the destination SME address. For mobile terminated messages, this is the directory number of the recipient MS. |
CamelSmppDestAddrTon
|
Defines the type of number (TON) to be used in the SME destination address parameters. The following TON values are defined:
|
CamelSmppDestAddrNpi
|
Defines the numeric plan indicator (NPI) to be used in the SME destination address parameters. The following NPI values are defined:
|
CamelSmppSourceAddr
|
Defines the address of SME (Short Message Entity) which originated this message. |
CamelSmppSourceAddrTon
|
Defines the type of number (TON) to be used in the SME originator address parameters. The following TON values are defined:
|
CamelSmppSourceAddrNpi
|
Defines the numeric plan indicator (NPI) to be used in the SME originator address parameters. The following NPI values are defined:
|
CamelSmppServiceType
|
The service type parameter can be used to indicate the SMS Application service associated with the message. The following generic service_types are defined:
|
CamelSmppRegisteredDelivery
|
Is used to request an SMSC delivery receipt and/or SME originated acknowledgements. The following values are defined:
|
CamelSmppPriorityFlag
|
Allows the originating SME to assign a priority level to the short message. Four Priority Levels are supported:
|
CamelSmppScheduleDeliveryTime
|
This parameter specifies the scheduled time at which the message delivery should be first attempted. It defines either the absolute date and time or relative time from the current SMSC time at which delivery of this message will be attempted by the SMSC. It can be specified in either absolute time format or relative time format. The encoding of a time format is specified in chapter 7.1.1. in the smpp specification v3.4. |
CamelSmppValidityPeriod
|
The validity period parameter indicates the SMSC expiration time, after which the message should be discarded if not delivered to the destination. It can be defined in absolute time format or relative time format. The encoding of absolute and relative time format is specified in chapter 7.1.1 in the smpp specification v3.4. |
CamelSmppReplaceIfPresentFlag
|
The replace if present flag parameter is used to request the SMSC to replace a previously submitted message, that is still pending delivery. The SMSC will replace an existing message provided that the source address, destination address and service type match the same fields in the new message. The following values are defined:
|
CamelSmppDataCoding
|
The data coding according to the SMPP 3.4 specification, section 5.2.19:
0 : SMSC Default Alphabet 4 : 8 bit Alphabet 8 : UCS2 Alphabet
|
Header | Description |
---|---|
CamelSmppId
|
the id to identify the submitted short message for later use (delivery receipt, query sm, cancel sm, replace sm). |
Header | Description | |
---|---|---|
CamelSmppSequenceNumber
|
only for alert notification, deliver sm and data sm: A sequence number allows a response PDU to be correlated with a request PDU. The associated SMPP response PDU must preserve this field. | |
CamelSmppCommandId
|
only for alert notification, deliver sm and data sm: The command id field identifies the particular SMPP PDU. For the complete list of defined values see chapter 5.1.2.1 in the smpp specification v3.4. | |
CamelSmppSourceAddr
|
only for alert notification, deliver sm and data sm: Defines the address of SME (Short Message Entity) which originated this message. | |
CamelSmppSourceAddrNpi
|
only for alert notification and data sm: Defines the numeric plan indicator (NPI) to be used in the SME originator address parameters. The following NPI values are defined:
|
|
CamelSmppSourceAddrTon
|
only for alert notification and data sm: Defines the type of number (TON) to be used in the SME originator address parameters. The following TON values are defined:
|
|
CamelSmppEsmeAddr
|
only for alert notification: Defines the destination ESME address. For mobile terminated messages, this is the directory number of the recipient MS. | |
CamelSmppEsmeAddrNpi
|
only for alert notification: Defines the numeric plan indicator (NPI) to be used in the ESME originator address parameters. The following NPI values are defined:
|
|
CamelSmppEsmeAddrTon
|
only for alert notification: Defines the type of number (TON) to be used in the ESME originator address parameters. The following TON values are defined:
|
|
CamelSmppId
|
only for smsc delivery receipt and data sm: The message ID allocated to the message by the SMSC when originally submitted. | |
CamelSmppDelivered
|
only for smsc delivery receipt: Number of short messages delivered. This is only relevant where the original message was submitted to a distribution list.The value is padded with leading zeros if necessary. | |
CamelSmppDoneDate
|
only for smsc delivery receipt: The time and date at which the short message reached it's final state. The format is as follows: YYMMDDhhmm. | |
CamelSmppStatus
|
only for smsc delivery receipt and data sm: The final status of the message. The following values are defined:
|
|
CamelSmppCommandStatus
|
Integer
|
*only for DataSm* The Command status of the message. |
CamelSmppError
|
only for smsc delivery receipt: Where appropriate this may hold a Network specific error code or an SMSC error code for the attempted delivery of the message. These errors are Network or SMSC specific and are not included here. | |
CamelSmppSubmitDate
|
only for smsc delivery receipt: The time and date at which the short message was submitted. In the case of a message which has been replaced, this is the date that the original message was replaced. The format is as follows: YYMMDDhhmm. | |
CamelSmppSubmitted
|
only for smsc delivery receipt: Number of short messages originally submitted. This is only relevant when the original message was submitted to a distribution list.The value is padded with leading zeros if necessary. | |
CamelSmppDestAddr
|
only for deliver sm and data sm: Defines the destination SME address. For mobile terminated messages, this is the directory number of the recipient MS. | |
CamelSmppScheduleDeliveryTime
|
only for deliver sm and data sm: This parameter specifies the scheduled time at which the message delivery should be first attempted. It defines either the absolute date and time or relative time from the current SMSC time at which delivery of this message will be attempted by the SMSC. It can be specified in either absolute time format or relative time format. The encoding of a time format is specified in Section 7.1.1. in the smpp specification v3.4. | |
CamelSmppValidityPeriod
|
only for deliver sm: The validity period parameter indicates the SMSC expiration time, after which the message should be discarded if not delivered to the destination. It can be defined in absolute time format or relative time format. The encoding of absolute and relative time format is specified in Section 7.1.1 in the smpp specification v3.4. | |
CamelSmppServiceType
|
only for deliver sm and data sm: The service type parameter indicates the SMS Application service associated with the message. | |
CamelSmppRegisteredDelivery
|
only for data sm: Is used to request an delivery receipt and/or SME originated acknowledgements. The following values are defined:
0 : No SMSC delivery receipt requested. 1 : SMSC delivery receipt requested where final delivery outcome is success or failure. 2 : SMSC delivery receipt requested where the final delivery outcome is delivery failure.
|
|
CamelSmppDestAddrNpi
|
only for data sm: Defines the numeric plan indicator (NPI) in the destination address parameters. The following NPI values are defined:
0 : Unknown 1 : ISDN (E163/E164) 2 : Data (X.121) 3 : Telex (F.69) 6 : Land Mobile (E.212) 8 : National 9 : Private 10 : ERMES 13 : Internet (IP) 18 : WAP Client Id (to be defined by WAP Forum)
|
|
CamelSmppDestAddrTon
|
only for data sm: Defines the type of number (TON) in the destination address parameters. The following TON values are defined:
0 : Unknown 1 : International 2 : National 3 : Network Specific 4 : Subscriber Number 5 : Alphanumeric 6 : Abbreviated
|
|
CamelSmppMessageType
|
Camel 2.6 onwarts: Identifies the type of an incoming message:
AlertNotification : an SMSC alert notification DataSm : an SMSC data short message DeliveryReceipt : an SMSC delivery receipt DeliverSm : an SMSC deliver short message
|
Exception handling Copier lienLien copié sur presse-papiers!
DeliverSm
or DataSm
short message and the processing of these messages fails, you can also throw a ProcessRequestException
instead of handle the failure. In this case, this exception is forwarded to the underlying JSMPP library which will return the included error code to the SMSC. This feature is useful to e.g. instruct the SMSC to resend the short message at a later time. This could be done with the following lines of code:
Samples Copier lienLien copié sur presse-papiers!
from("direct:start") .to("smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=producer");
from("direct:start")
.to("smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=producer");
<route> <from uri="direct:start"/> <to uri="smpp://smppclient@localhost:2775?password=password&nquireLinkTimer=3000&ransactionTimer=5000&ystemType=producer"/> </route>
<route>
<from uri="direct:start"/>
<to uri="smpp://smppclient@localhost:2775?password=password&nquireLinkTimer=3000&ransactionTimer=5000&ystemType=producer"/>
</route>
from("smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer") .to("bean:foo");
from("smpp://smppclient@localhost:2775?password=password&enquireLinkTimer=3000&transactionTimer=5000&systemType=consumer")
.to("bean:foo");
<route> <from uri="smpp://smppclient@localhost:2775?password=password&nquireLinkTimer=3000&ransactionTimer=5000&ystemType=consumer"/> <to uri="bean:foo"/> </route>
<route>
<from uri="smpp://smppclient@localhost:2775?password=password&nquireLinkTimer=3000&ransactionTimer=5000&ystemType=consumer"/>
<to uri="bean:foo"/>
</route>
Debug logging Copier lienLien copié sur presse-papiers!
log4j.logger.org.apache.camel.component.smpp=DEBUG
log4j.logger.org.apache.camel.component.smpp=DEBUG
Chapter 91. SNMP Copier lienLien copié sur presse-papiers!
SNMP Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
snmp://hostname[:port][?Options]
snmp://hostname[:port][?Options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
type
|
none |
The type of action you want to perform. Actually you can enter here POLL or TRAP . The value POLL will instruct the endpoint to poll a given host for the supplied OID keys. If you put in TRAP you will setup a listener for SNMP Trap Events.
|
address
|
none |
This is the IP address and the port of the host to poll or where to setup the Trap Receiver. Example: 127.0.0.1:162
|
protocol
|
udp
|
Here you can select which protocol to use. You can use either udp or tcp .
|
retries
|
2
|
Defines how often a retry is made before canceling the request. |
timeout
|
1500
|
Sets the timeout value for the request in millis. |
snmpVersion
|
0 (which means SNMPv1)
|
Sets the snmp version for the request. |
snmpCommunity
|
public
|
Sets the community octet string for the snmp request. |
delay
|
60 seconds
|
Defines the delay in seconds between to poll cycles. |
oids
|
none |
Defines which values you are interested in. Please have a look at the Wikipedia to get a better understanding. You may provide a single OID or a coma separated list of OIDs. Example: oids="1.3.6.1.2.1.1.3.0,1.3.6.1.2.1.25.3.2.1.5.1,1.3.6.1.2.1.25.3.5.1.1.1,1.3.6.1.2.1.43.5.1.1.11.1"
|
The result of a poll Copier lienLien copié sur presse-papiers!
1.3.6.1.2.1.1.3.0 1.3.6.1.2.1.25.3.2.1.5.1 1.3.6.1.2.1.25.3.5.1.1.1 1.3.6.1.2.1.43.5.1.1.11.1
1.3.6.1.2.1.1.3.0
1.3.6.1.2.1.25.3.2.1.5.1
1.3.6.1.2.1.25.3.5.1.1.1
1.3.6.1.2.1.43.5.1.1.11.1
Examples Copier lienLien copié sur presse-papiers!
snmp:192.168.178.23:161?protocol=udp&type=POLL&oids=1.3.6.1.2.1.1.5.0
snmp:192.168.178.23:161?protocol=udp&type=POLL&oids=1.3.6.1.2.1.1.5.0
snmp:127.0.0.1:162?protocol=udp&type=TRAP
snmp:127.0.0.1:162?protocol=udp&type=TRAP
from("snmp:192.168.178.23:161?protocol=udp&type=POLL&oids=1.3.6.1.2.1.1.5.0"). convertBodyTo(String.class). to("activemq:snmp.states");
from("snmp:192.168.178.23:161?protocol=udp&type=POLL&oids=1.3.6.1.2.1.1.5.0").
convertBodyTo(String.class).
to("activemq:snmp.states");
Chapter 92. Solr Copier lienLien copié sur presse-papiers!
Solr Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
solr://host[:port]/solr?[options]
solr://host[:port]/solr?[options]
Endpoint Options Copier lienLien copié sur presse-papiers!
name | default value | description |
---|---|---|
maxRetries | 0 | maximum number of retries to attempt in the event of transient errors |
soTimeout | 1000 | read timeout on the underlying HttpConnectionManager. This is desirable for queries, but probably not for indexing |
connectionTimeout | 100 | connectionTimeout on the underlying HttpConnectionManager |
defaultMaxConnectionsPerHost | 2 | maxConnectionsPerHost on the underlying HttpConnectionManager |
maxTotalConnections | 20 | maxTotalConnection on the underlying HttpConnectionManager |
followRedirects | false | indicates whether redirects are used to get to the Solr server |
allowCompression | false | server side must support gzip or deflate for this to have any effect |
requestHandler | /update (xml) | set the request handler to be used |
streamingThreadCount | 2 | Camel 2.9.2 set the number of threads for the StreamingUpdateSolrServer |
streamingQueueSize | 10 | Camel 2.9.2 set the queue size for the StreamingUpdateSolrServer |
Message Operations Copier lienLien copié sur presse-papiers!
- the INSERT operations use the CommonsHttpSolrServer
- the INSERT_STREAMING operations use the StreamingUpdateSolrServer (Camel 2.9.2)
operation | message body | description |
---|---|---|
INSERT/INSERT_STREAMING | n/a | adds an index using message headers (must be prefixed with "SolrField.") |
INSERT/INSERT_STREAMING | File | adds an index using the given File (using ContentStreamUpdateRequest) |
INSERT/INSERT_STREAMING | SolrInputDocument | Camel 2.9.2 updates index based on the given SolrInputDocument |
INSERT/INSERT_STREAMING | String XML | Camel 2.9.2 updates index based on the given XML (must follow SolrInputDocument format) |
ADD_BEAN | bean instance | adds an index based on values in an annotated bean |
DELETE_BY_ID | index id to delete | delete a record by ID |
DELETE_BY_QUERY | query string | delete a record by a query |
COMMIT | n/a | performs a commit on any pending index changes |
ROLLBACK | n/a | performs a rollback on any pending index changes |
OPTIMIZE | n/a | performs a commit on any pending index changes and then runs the optimize command |
Example Copier lienLien copié sur presse-papiers!
template.sendBody("direct:insert", "1234"); template.sendBody("direct:commit", null);
template.sendBody("direct:insert", "1234");
template.sendBody("direct:commit", null);
Querying Solr Copier lienLien copié sur presse-papiers!
Chapter 93. SpringBatch Copier lienLien copié sur presse-papiers!
Spring Batch Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
spring-batch:jobName[?options]
spring-batch:jobName[?options]
from()
statement.
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
jobLauncherRef
|
null
|
*Camel 2.10:* Explicitly specifies the name of the JobLauncher to be used.
|
Usage Copier lienLien copié sur presse-papiers!
org.springframework.batch.core.launch.JobLaucher
instance resolved according to the following algorithm:
- if
JobLauncher
is manually set on the component, then use it. - if
jobLauncherRef
option is set on the component, then search Camel Registry for theJobLauncher
with the given name. - if there is
JobLauncher
registered in the Camel Registry under jobLauncher name, then use it. - if none of the steps above allow to resolve the
JobLauncher
and there is exactly oneJobLauncher
instance in the Camel Registry, then use it.
JobLauncher
as job parameters. String
, Long
, Double
and java.util.Date
values are copied to the org.springframework.batch.core.JobParametersBuilder
- other data types are converted to Strings.
Examples Copier lienLien copié sur presse-papiers!
from("direct:startBatch").to("spring-batch:myJob");
from("direct:startBatch").to("spring-batch:myJob");
JobLauncher
set explicitly.
from("direct:startBatch").to("spring-batch:myJob?jobLauncherRef=myJobLauncher");
from("direct:startBatch").to("spring-batch:myJob?jobLauncherRef=myJobLauncher");
Support classes Copier lienLien copié sur presse-papiers!
CamelItemReader Copier lienLien copié sur presse-papiers!
CamelItemReader
can be used to read batch data directly from the Camel infrastructure.
CamelItemWriter Copier lienLien copié sur presse-papiers!
CamelItemWriter
has similar purpose as CamelItemReader
, but it is dedicated to write chunk of the processed data.
CamelItemProcessor Copier lienLien copié sur presse-papiers!
CamelItemProcessor
is the implementation of Spring Batch org.springframework.batch.item.ItemProcessor
interface. The latter implementation relays on Request Reply pattern to delegate the processing of the batch item to the Camel infrastructure. The item to process is sent to the Camel endpoint as the body of the message.
CamelJobExecutionListener Copier lienLien copié sur presse-papiers!
CamelJobExecutionListener
is the implementation of the org.springframework.batch.core.JobExecutionListener
interface sending job execution events to the Camel endpoint.
org.springframework.batch.core.JobExecution
instance produced by the Spring Batch is sent as a body of the message. To distinguish between before- and after-callbacks SPRING_BATCH_JOB_EVENT_TYPE
header is set to the BEFORE
or AFTER
value.
Chapter 94. SpringIntegration Copier lienLien copié sur presse-papiers!
Spring Integration Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
spring-integration:defaultChannelName[?options]
spring-integration:defaultChannelName[?options]
inputChannel
name for the Spring Integration consumer and the outputChannel
name for the Spring Integration provider.
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Description | Example | Required | Default Value |
---|---|---|---|---|
inputChannel
|
The Spring integration input channel name that this endpoint wants to consume from, where the specified channel name is defined in the Spring context. |
inputChannel=requestChannel
|
No | |
outputChannel
|
The Spring integration output channel name that is used to send messages to the Spring integration context. |
outputChannel=replyChannel
|
No | |
inOut
|
The exchange pattern that the Spring integration endpoint should use. |
inOut=true
|
No |
inOnly for the Spring integration consumer and outOnly for the Spring integration provider
|
consumer.delay
|
Delay in milliseconds between each poll. |
consumer.delay=60000
|
No |
500
|
consumer.initialDelay
|
Milliseconds before polling starts. |
consumer.initialDelay=10000
|
No |
1000
|
consumer.userFixedDelay
|
Specify true to use fixed delay between polls, otherwise fixed rate is used. See the ScheduledExecutorService class for details.
|
consumer.userFixedDelay=false
|
No |
false
|
Usage Copier lienLien copié sur presse-papiers!
Using the Spring integration endpoint Copier lienLien copié sur presse-papiers!
The Source and Target adapter Copier lienLien copié sur presse-papiers!
Chapter 95. Spring Security Copier lienLien copié sur presse-papiers!
Spring Security Copier lienLien copié sur presse-papiers!
Creating authorization policies Copier lienLien copié sur presse-papiers!
SpringSecurityAuthorizationPolicy
object. A policy object contains the name of the Spring Security authority (role) required to run a set of endpoints and references to Spring Security AuthenticationManager
and AccessDecisionManager
objects used to determine whether the current principal has been assigned that role. Policy objects may be configured as Spring beans or by using an <authorizationPolicy>
element in Spring XML.
<authorizationPolicy>
element may contain the following attributes:
Name | Default Value | Description |
---|---|---|
id
|
null
|
The unique Spring bean identifier which is used to reference the policy in routes (required) |
access
|
null
|
The Spring Security authority name that is passed to the access decision manager (required) |
authenticationManager
|
authenticationManager
|
The name of the Spring Security AuthenticationManager object in the context
|
accessDecisionManager
|
accessDecisionManager
|
The name of the Spring Security AccessDecisionManager object in the context
|
authenticationAdapter
|
DefaultAuthenticationAdapter |
Camel 2.4 The name of a camel-spring-securityAuthenticationAdapter object in the context that is used to convert a javax.security.auth.Subject into a Spring Security Authentication instance.
|
useThreadSecurityContext
|
true
|
If a javax.security.auth.Subject cannot be found in the In message header under Exchange.AUTHENTICATION, check the Spring Security SecurityContextHolder for an Authentication object.
|
alwaysReauthenticate
|
false
|
If set to true, the SpringSecurityAuthorizationPolicy will always call AuthenticationManager.authenticate() each time the policy is accessed.
|
Controlling access to Camel routes Copier lienLien copié sur presse-papiers!
AuthenticationManager
and AccessDecisionManager
are required to use this component. Here is an example of how to configure these objects in Spring XML using the Spring Security namespace:
mock:end
will not be executed unless a Spring Security Authentication
object that has been or can be authenticated and contains the ROLE_ADMIN
authority can be located by the adminSpringSecurityAuthorizationPolicy
.
Authentication Copier lienLien copié sur presse-papiers!
SecurityContextHolder
so the camel-spring-security component can access them:
SpringSecurityAuthorizationPolicy
will automatically authenticate the Authentication
object if necessary.
SecurityContextHolder
instead of or in addition to the Exchange.AUTHENTICATION
header. First, the context holder uses a thread-local variable to hold the Authentication
object. Any routes that cross thread boundaries, like seda or jms, will lose the Authentication
object. Second, the Spring Security system appears to expect that an Authentication
object in the context is already authenticated and has roles (see the Technical Overview section 5.3.1 for more details).
Subject
in the Exchange.AUTHENTICATION
header. This Subject
must contain at least one principal, which must be a subclass of org.springframework.security.core.Authentication
. You can customize the mapping of Subject
to Authentication
object by providing an implementation of the org.apache.camel.component.spring.security.AuthenticationAdapter
to your <authorizationPolicy>
bean. This can be useful if you are working with components that do not use Spring Security but do provide a Subject
. At this time, only the camel-cxf component populates the Exchange.AUTHENTICATION
header.
Handling authentication and authorization errors Copier lienLien copié sur presse-papiers!
SpringSecurityAuthorizationPolicy
, a CamelAuthorizationException
will be thrown. This can be handled using Camel's standard exception handling methods, like the Exception clause. The CamelAuthorizationException
will have a reference to the ID of the policy which threw the exception so you can handle errors based on the policy as well as the type of exception:
Dependencies Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-spring-security</artifactId> <version>2.4.0</version> </dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-spring-security</artifactId>
<version>2.4.0</version>
</dependency>
org.springframework.security:spring-security-core:3.0.3.RELEASE
and org.springframework.security:spring-security-config:3.0.3.RELEASE
.
Chapter 96. Spring Web Services Copier lienLien copié sur presse-papiers!
Spring Web Services Component Copier lienLien copié sur presse-papiers!
camel-spring-ws
on Spring 2.5.x you need to add the spring-webmvc
module from Spring 2.5.x. In order to run Spring-WS 1.5.9 on Spring 3.0.x you need to exclude the OXM module from Spring 3.0.x as this module is also included in Spring-WS 1.5.9 (see this post)
URI format Copier lienLien copié sur presse-papiers!
spring-ws:[mapping-type:]address[?options]
spring-ws:[mapping-type:]address[?options]
mapping-type
needs to be set to one of the following values:
Mapping type | Description |
---|---|
rootqname
|
Offers the option to map web service requests based on the qualified name of the root element contained in the message. |
soapaction
|
Used to map web service requests based on the SOAP action specified in the header of the message. |
uri
|
In order to map web service requests that target a specific URI. |
xpathresult
|
Used to map web service requests based on the evaluation of an XPath expression against the incoming message. The result of the evaluation should match the XPath result specified in the endpoint URI.
|
beanname
|
Allows you to reference a org.apache.camel.component.spring.ws.bean.CamelEndpointDispatcher in order to integrate with existing (legacy) endpoint mappings like PayloadRootQNameEndpointMapping , SoapActionEndpointMapping , etc
|
address
should contain a value relevant to the specified mapping-type (e.g. a SOAP action, XPath expression). As a producer the address should be set to the URI of the web service you are calling upon.
?option=value&option=value&...
.
Options Copier lienLien copié sur presse-papiers!
Name | Required? | Description |
---|---|---|
soapAction
|
No | SOAP action to include inside a SOAP request when accessing remote web services |
wsAddressingAction
|
No |
WS-Addressing 1.0 action header to include when accessing web services. The To header is set to the address of the web service as specified in the endpoint URI (default Spring-WS behavior).
|
expression
|
Only when mapping-type is xpathresult
|
XPath expression to use in the process of mapping web service requests, should match the result specified by xpathresult
|
timeout
|
No | *Camel 2.10:* Sets the socket read timeout (in milliseconds) while invoking a webservice using the producer, see URLConnection.setReadTimeout() and CommonsHttpMessageSender.setReadTimeout(). his option works when using the built-in message sender implementations: CommonsHttpMessageSender nd HttpUrlConnectionMessageSender. ne of these implementations will be used by default for HTTP based services unless you customize the Spring WS configuration options supplied to the component. f you are using a non-standard sender, it is assumed that you will handle your own timeout configuration. |
sslContextParameters
|
No |
*Camel 2.10:* eference to an org.apache.camel.util.jsse.SSLContextParameters in he Registry. ee Using the JSSE Configuration Utility. his option works when using the built-in message sender implementations: CommonsHttpMessageSender nd HttpUrlConnectionMessageSender. ne of these implementations will be used by default for HTTP based services unless you customize the Spring WS configuration options supplied to the component. f you are using a non-standard sender, it is assumed that you will handle your own TLS configuration.
|
Registry based options Copier lienLien copié sur presse-papiers!
#beanID
notation.
Name | Required? | Description |
---|---|---|
webServiceTemplate
|
No | Option to provide a custom WebServiceTemplate. This allows for full control over client-side web services handling; like adding a custom interceptor or specifying a fault resolver, message sender or message factory. |
messageSender
|
No | Option to provide a custom WebServiceMessageSender. For example to perform authentication or use alternative transports |
messageFactory
|
No | Option to provide a custom WebServiceMessageFactory. For example when you want Apache Axiom to handle web service messages instead of SAAJ |
transformerFactory
|
No |
Option to override the default TransformerFactory . The provided transformer factory must be of type javax.xml.transform.TransformerFactory
|
endpointMapping
|
Only when mapping-type is rootqname , soapaction , uri or xpathresult
|
Reference to org.apache.camel.component.spring.ws.bean.CamelEndpointMapping in the Registry/ApplicationContext. Only one bean is required in the registry to serve all Camel/Spring-WS endpoints. This bean is auto-discovered by the MessageDispatcher and used to map requests to Camel endpoints based on characteristics specified on the endpoint (like root QName, SOAP action, etc)
|
Message headers Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
CamelSpringWebserviceEndpointUri
|
String
|
URI of the web service you are accessing as a client; overrides the address part of the endpoint URI. |
CamelSpringWebserviceSoapAction
|
String
|
Header to specify the SOAP action of the message; overrides the soapAction option, if present
|
CamelSpringWebserviceAddressingAction
|
URI
|
Use this header to specify the WS-Addressing action of the message; overrides the wsAddressingAction option, if present
|
Accessing web services Copier lienLien copié sur presse-papiers!
http://foo.com/bar
simply define a route:
from("direct:example").to("spring-ws:http://foo.com/bar")
from("direct:example").to("spring-ws:http://foo.com/bar")
template.requestBody("direct:example", "<foobar xmlns=\"http://foo.com\"><msg>test message</msg></foobar>");
template.requestBody("direct:example", "<foobar xmlns=\"http://foo.com\"><msg>test message</msg></foobar>");
Sending SOAP and WS-Addressing action headers Copier lienLien copié sur presse-papiers!
from("direct:example") .to("spring-ws:http://foo.com/bar?soapAction=http://foo.com&wsAddressingAction=http://bar.com")
from("direct:example")
.to("spring-ws:http://foo.com/bar?soapAction=http://foo.com&wsAddressingAction=http://bar.com")
template.requestBodyAndHeader("direct:example", "<foobar xmlns=\"http://foo.com\"><msg>test message</msg></foobar>", SpringWebserviceConstants.SPRING_WS_SOAP_ACTION, "http://baz.com");
template.requestBodyAndHeader("direct:example",
"<foobar xmlns=\"http://foo.com\"><msg>test message</msg></foobar>",
SpringWebserviceConstants.SPRING_WS_SOAP_ACTION, "http://baz.com");
Using a custom MessageSender and MessageFactory Copier lienLien copié sur presse-papiers!
from("direct:example") .to("spring-ws:http://foo.com/bar?messageFactory=#messageFactory&messageSender=#messageSender")
from("direct:example")
.to("spring-ws:http://foo.com/bar?messageFactory=#messageFactory&messageSender=#messageSender")
Exposing web services Copier lienLien copié sur presse-papiers!
MessageDispatcherServlet
configured in web.xml
.
MessageDispatcherServlet
will look for a Spring XML named /WEB-INF/spring-ws-servlet.xml
. To use Camel with Spring-WS the only mandatory bean in that XML file is CamelEndpointMapping
. This bean allows the MessageDispatcher
to dispatch web service requests to your routes.
Endpoint mapping in routes Copier lienLien copié sur presse-papiers!
GetFoo
within the http://example.com/
namespace:
from("spring-ws:rootqname:{http://example.com/}GetFoo?endpointMapping=#endpointMapping") .convertBodyTo(String.class).to(mock:example)
from("spring-ws:rootqname:{http://example.com/}GetFoo?endpointMapping=#endpointMapping")
.convertBodyTo(String.class).to(mock:example)
http://example.com/GetFoo
SOAP action:
from("spring-ws:soapaction:http://example.com/GetFoo?endpointMapping=#endpointMapping") .convertBodyTo(String.class).to(mock:example)
from("spring-ws:soapaction:http://example.com/GetFoo?endpointMapping=#endpointMapping")
.convertBodyTo(String.class).to(mock:example)
http://example.com/foobar
:
from("spring-ws:uri:http://example.com/foobar?endpointMapping=#endpointMapping") .convertBodyTo(String.class).to(mock:example)
from("spring-ws:uri:http://example.com/foobar?endpointMapping=#endpointMapping")
.convertBodyTo(String.class).to(mock:example)
<foobar>abc</foobar>
anywhere inside the message (and the default namespace).
from("spring-ws:xpathresult:abc?expression=//foobar&endpointMapping=#endpointMapping") .convertBodyTo(String.class).to(mock:example)
from("spring-ws:xpathresult:abc?expression=//foobar&endpointMapping=#endpointMapping")
.convertBodyTo(String.class).to(mock:example)
Alternative configuration, using existing endpoint mappings Copier lienLien copié sur presse-papiers!
beanname
one bean of type CamelEndpointDispatcher
with a corresponding name is required in the Registry/ApplicationContext. This bean acts as a bridge between the Camel endpoint and an existing endpoint mapping like PayloadRootQNameEndpointMapping
.
beanname
mapping-type is primarily meant for (legacy) situations where you're already using Spring-WS and have endpoint mappings defined in a Spring XML file. The beanname
mapping-type allows you to wire your Camel route into an existing endpoint mapping. When you're starting from scratch it's recommended to define your endpoint mappings as Camel URI's (as illustrated above with endpointMapping
) since it requires less configuration and is more expressive. Alternatively you could use vanilla Spring-WS with the help of annotations.
beanname
:
POJO (un)marshalling Copier lienLien copié sur presse-papiers!
JaxbDataFormat jaxb = new JaxbDataFormat(false); jaxb.setContextPath("com.example.model"); from("direct:example").marshal(jaxb).to("spring-ws:http://foo.com/bar").unmarshal(jaxb);
JaxbDataFormat jaxb = new JaxbDataFormat(false);
jaxb.setContextPath("com.example.model");
from("direct:example").marshal(jaxb).to("spring-ws:http://foo.com/bar").unmarshal(jaxb);
from("spring-ws:rootqname:{http://example.com/}GetFoo?endpointMapping=#endpointMapping").unmarshal(jaxb) .to("mock:example").marshal(jaxb);
from("spring-ws:rootqname:{http://example.com/}GetFoo?endpointMapping=#endpointMapping").unmarshal(jaxb)
.to("mock:example").marshal(jaxb);
Chapter 97. SQL Component Copier lienLien copié sur presse-papiers!
SQL Component Copier lienLien copié sur presse-papiers!
spring-jdbc
behind the scenes for the actual SQL handling.
- a JDBC based repository for the Idempotent Consumer EIP pattern. See further below.
- a JDBC based repository for the Aggregator EIP pattern. See further below.
URI format Copier lienLien copié sur presse-papiers!
from()
statement.
sql:select * from table where id=# order by name[?options]
sql:select * from table where id=# order by name[?options]
?
symbol that denotes the parameters to an SQL query is substituted with the #
symbol, because the ?
symbol is used to specify options for the endpoint. The ?
symbol replacement can be configured on endpoint basis.
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Option | Type | Default | Description |
---|---|---|---|
batch
|
boolean
|
false
|
*Camel 2.7.5, 2.8.4 and 2.9:* Execute SQL batch update statements. See notes below on how the treatment of the inbound message body changes if this is set to true .
|
dataSourceRef
|
String
|
null
|
Apache Camel 1.5.1/2.0: Reference to a DataSource to look up in the registry.
|
placeholder
|
String
|
#
|
Camel 2.4: Specifies a character that will be replaced to ? in SQL query. Notice, that it is simple String.replaceAll() operation and no SQL parsing is involved (quoted strings will also change)
|
template.<xxx>
|
null
|
Sets additional options on the Spring JdbcTemplate that is used behind the scenes to execute the queries. For instance, template.maxRows=10 . For detailed documentation, see the JdbcTemplate javadoc documentation.
|
Treatment of the message body Copier lienLien copié sur presse-papiers!
java.util.Iterator
type and then uses this iterator to fill the query parameters (where each query parameter is represented by a #
symbol, or other configured placeholder, in the endpoint URI). If the message body is not an array or collection, the conversion results in an iterator that iterates over only one object, which is the body itself.
java.util.List
, the first item in the list is substituted into the first occurrence of #
in the SQL query, the second item in the list is substituted into the second occurrence of #
, and so on.
batch
is set to true
, then the interpretation of the inbound message body changes slightly - instead of an iterator of parameters, the component expects an iterator that contains the parameter iterators; the size of the outer iterator determines the batch size.
Result of the query Copier lienLien copié sur presse-papiers!
select
operations, the result is an instance of List<Map<String, Object>>
type, as returned by the JdbcTemplate.queryForList() method. For update
operations, the result is the number of updated rows, returned as an Integer
.
Header values Copier lienLien copié sur presse-papiers!
update
operations, the SQL Component stores the update count in the following message headers:
Header | Description |
---|---|
CamelSqlUpdateCount
|
Apache Camel 2.0: The number of rows updated for update operations, returned as an Integer object.
|
CamelSqlRowCount
|
Apache Camel 2.0: The number of rows returned for select operations, returned as an Integer object.
|
CamelSqlQuery
|
Camel 2.8: Query to execute. This query takes precedence over the query specified in the endpoint URI. Note that query parameters in the header are represented by a ? instead of a # symbol
|
Configuration Copier lienLien copié sur presse-papiers!
DataSource
in the URI directly:
sql:select * from table where id=# order by name?dataSourceRef=myDS
sql:select * from table where id=# order by name?dataSourceRef=myDS
Sample Copier lienLien copié sur presse-papiers!
List
of rows, where each row is a Map<String, Object
and the key is the column name.
// this is the database we create with some initial data for our unit test db = new EmbeddedDatabaseBuilder() .setType(EmbeddedDatabaseType.DERBY).addScript("sql/createAndPopulateDatabase.sql").build();
// this is the database we create with some initial data for our unit test
db = new EmbeddedDatabaseBuilder()
.setType(EmbeddedDatabaseType.DERBY).addScript("sql/createAndPopulateDatabase.sql").build();
createAndPopulateDatabase.sql
we execute looks like as described below:
create table projects (id integer primary key, project varchar(10), license varchar(5)); insert into projects values (1, 'Camel', 'ASF'); insert into projects values (2, 'AMQ', 'ASF'); insert into projects values (3, 'Linux', 'XXX');
create table projects (id integer primary key, project varchar(10), license varchar(5));
insert into projects values (1, 'Camel', 'ASF');
insert into projects values (2, 'AMQ', 'ASF');
insert into projects values (3, 'Linux', 'XXX');
sql
component. Notice that we use a direct
endpoint in front of the sql
endpoint. This allows us to send an exchange to the direct
endpoint with the URI, direct:simple
, which is much easier for the client to use than the long sql:
URI. Note that the DataSource
is looked up up in the registry, so we can use standard Spring XML to configure our DataSource
.
from("direct:simple") .to("sql:select * from projects where license = # order by id?dataSourceRef=jdbc/myDataSource") .to("mock:result");
from("direct:simple")
.to("sql:select * from projects where license = # order by id?dataSourceRef=jdbc/myDataSource")
.to("mock:result");
direct
endpoint that will route it to our sql
component that queries the database.
DataSource
in Spring XML as follows:
<jee:jndi-lookup id="myDS" jndi-name="jdbc/myDataSource"/>
<jee:jndi-lookup id="myDS" jndi-name="jdbc/myDataSource"/>
Using the JDBC based idempotent repository Copier lienLien copié sur presse-papiers!
org.apache.camel.processor.idempotent.jdbc.AbstractJdbcMessageIdRepository
you can extend to build custom JDBC idempotent repository.
createdAt
column:
CREATE TABLE CAMEL_MESSAGEPROCESSED ( processorName VARCHAR(255), messageId VARCHAR(100), createdAt TIMESTAMP )
CREATE TABLE CAMEL_MESSAGEPROCESSED (
processorName VARCHAR(255),
messageId VARCHAR(100),
createdAt TIMESTAMP
)
javax.sql.DataSource
in the spring XML file:
<jdbc:embedded-database id="dataSource" type="DERBY" />
<jdbc:embedded-database id="dataSource" type="DERBY" />
Customize the JdbcMessageIdRepository Copier lienLien copié sur presse-papiers!
org.apache.camel.processor.idempotent.jdbc.JdbcMessageIdRepository
for your needs:
Parameter | Default Value | Description |
---|---|---|
createTableIfNotExists | true | Defines whether or not Camel should try to create the table if it doesn't exist. |
tableExistsString | SELECT 1 FROM CAMEL_MESSAGEPROCESSED WHERE 1 = 0 | This query is used to figure out whether the table already exists or not. It must throw an exception to indicate the table doesn't exist. |
createString | CREATE TABLE CAMEL_MESSAGEPROCESSED (processorName VARCHAR(255), messageId VARCHAR(100), createdAt TIMESTAMP) | The statement which is used to create the table. |
queryString | SELECT COUNT\(*\) FROM CAMEL_MESSAGEPROCESSED WHERE processorName = ? AND messageId = ? |
The query which is used to figure out whether the message already exists in the repository (the result is not equals to '0'). It takes two parameters. This first one is the processor name (String ) and the second one is the message id (String ).
|
insertString | INSERT INTO CAMEL_MESSAGEPROCESSED (processorName, messageId, createdAt) VALUES (?, ?, ?) |
The statement which is used to add the entry into the table. It takes three parameter. The first one is the processor name (String ), the second one is the message id (String ) and the third one is the timestamp (java.sql.Timestamp ) when this entry was added to the repository.
|
deleteString | DELETE FROM CAMEL_MESSAGEPROCESSED WHERE processorName = ? AND messageId = ? |
The statement which is used to delete the entry from the database. It takes two parameter. This first one is the processor name (String ) and the second one is the message id (String ).
|
org.apache.camel.processor.idempotent.jdbc.JdbcMessageIdRepository
could look like:
Using the JDBC based aggregation repository Copier lienLien copié sur presse-papiers!
camel-jdbc-aggregator
component. From Camel 2.7 onwards, the JdbcAggregationRepository
is provided in the camel-sql
component.
JdbcAggregationRepository
is an AggregationRepository
which on the fly persists the aggregated messages. This ensures that you will not loose messages, as the default aggregator will use an in memory only AggregationRepository
. The JdbcAggregationRepository
allows together with Camel to provide persistent support for the Aggregator.
Option | Type | Description |
---|---|---|
dataSource
|
DataSource
|
Mandatory: The javax.sql.DataSource to use for accessing the database.
|
repositoryName
|
String
|
Mandatory: The name of the repository. |
transactionManager
|
TransactionManager
|
Mandatory: The org.springframework.transaction.PlatformTransactionManager to mange transactions for the database. The TransactionManager must be able to support databases.
|
lobHandler
|
LobHandler
|
A org.springframework.jdbc.support.lob.LobHandler to handle Lob types in the database. Use this option to use a vendor specific LobHandler, for example when using Oracle.
|
returnOldExchange
|
boolean |
Whether the get operation should return the old existing Exchange if any existed. By default this option is false to optimize as we do not need the old exchange when aggregating.
|
useRecovery
|
boolean |
Whether or not recovery is enabled. This option is by default true . When enabled the Camel Aggregator automatic recover failed aggregated exchange and have them resubmitted.
|
recoveryInterval
|
long | If recovery is enabled then a background task is run every x'th time to scan for failed exchanges to recover and resubmit. By default this interval is 5000 millis. |
maximumRedeliveries
|
int |
Allows you to limit the maximum number of redelivery attempts for a recovered exchange. If enabled then the Exchange will be moved to the dead letter channel if all redelivery attempts failed. By default this option is disabled. If this option is used then the deadLetterUri option must also be provided.
|
deadLetterUri
|
String |
An endpoint uri for a Dead Letter Channel where exhausted recovered Exchanges will be moved. If this option is used then the maximumRedeliveries option must also be provided.
|
What is preserved when persisting Copier lienLien copié sur presse-papiers!
JdbcAggregationRepository
will only preserve any Serializable
compatible data types. If a data type is not such a type its dropped and a WARN
is logged. And it only persists the Message
body and the Message
headers. The Exchange
properties are not persisted.
Recovery Copier lienLien copié sur presse-papiers!
JdbcAggregationRepository
will by default recover any failed Exchange. It does this by having a background tasks that scans for failed Exchanges in the persistent store. You can use the checkInterval
option to set how often this task runs. The recovery works as transactional which ensures that Camel will try to recover and redeliver the failed Exchange. Any Exchange which was found to be recovered will be restored from the persistent store and resubmitted and send out again.
Header | Type | Description |
---|---|---|
Exchange.REDELIVERED
|
Boolean | Is set to true to indicate the Exchange is being redelivered. |
Exchange.REDELIVERY_COUNTER
|
Integer | The redelivery attempt, starting from 1. |
confirm
method is invoked on the AggregationRepository
. This means if the same Exchange fails again it will be kept retried until it success.
maximumRedeliveries
to limit the maximum number of redelivery attempts for a given recovered Exchange. You must also set the deadLetterUri
option so Camel knows where to send the Exchange when the maximumRedeliveries
was hit.
Database Copier lienLien copié sur presse-papiers!
"_COMPLETED"
. The name must be configured in the Spring bean with the RepositoryName
property. In the following example aggregation will be used.
"aggregation"
with your aggregator repository name.
Codec (Serialization) Copier lienLien copié sur presse-papiers!
JdbcCodec
class. One detail of the code requires your attention: the ClassLoadingAwareObjectInputStream
.
ClassLoadingAwareObjectInputStream
has been reused from the Apache ActiveMQ project. It wraps an ObjectInputStream
and use it with the ContextClassLoader
rather than the currentThread
one. The benefit is to be able to load classes exposed by other bundles. This allows the exchange body and headers to have custom types object references.
Transaction Copier lienLien copié sur presse-papiers!
PlatformTransactionManager
is required to orchestrate transaction.
Service (Start/Stop) Copier lienLien copié sur presse-papiers!
start
method verify the connection of the database and the presence of the required tables. If anything is wrong it will fail during starting.
Aggregator configuration Copier lienLien copié sur presse-papiers!
lobHandler
property.
Chapter 98. SSH Copier lienLien copié sur presse-papiers!
SSH Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
ssh:[username[:password]@]host[:port][?options]
ssh:[username[:password]@]host[:port][?options]
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
host | Hostname of SSH Server | |
port |
22
|
Port of the SSH Server |
username | Username used for authenticating with SSH Server. | |
password |
Password used for authenticating with SSH Server. Used if keyPairProvider is null.
|
|
keyPairProvider |
Refers to a org.apache.sshd.common.KeyPairProvider to use for loading keys for authentication. If this option is used, then password is not used.
|
|
keyType | ssh-rsa |
Refers to a key type to load from keyPairProvider . The key types can for example be "ssh-rsa" or "ssh-dss".
|
certFilename |
Refers to a file name to use as file based keyPairProvider .
|
|
timeout |
30000
|
Milliseconds to wait beforing timing out connection to SSH Server. |
initialDelay |
1000
|
*Consumer only:* Milliseconds before polling the SSH server starts. |
delay |
500
|
*Consumer only:* Milliseconds before the next poll of the SSH Server. |
useFixedDelay |
true
|
*Consumer only:* Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. |
pollCommand | *Consumer only:* Command to send to SSH Server during each poll cycle. Used only when acting as Consumer |
Example Copier lienLien copié sur presse-papiers!
examples/camel-example-ssh
in the Camel distribution.
Chapter 99. StAX Copier lienLien copié sur presse-papiers!
StAX Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
stax:content-handler-class
stax:content-handler-class
stax:org.superbiz.FooContentHandler
stax:org.superbiz.FooContentHandler
Usage of a content handler as StAX parser Copier lienLien copié sur presse-papiers!
Iterate over a collection using JAXB and StAX Copier lienLien copié sur presse-papiers!
StAXBuilder
which can be used when iterating XML elements with the Camel Splitter
from("file:target/in") .split(stax(Record.class)).streaming() .to("mock:records");
from("file:target/in")
.split(stax(Record.class)).streaming()
.to("mock:records");
stax
is a static method on org.apache.camel.component.stax.StAXBuilder
which you can static import in the Java code.
The previous example with XML DSL Copier lienLien copié sur presse-papiers!
Chapter 100. Stream Copier lienLien copié sur presse-papiers!
Stream Component Copier lienLien copié sur presse-papiers!
System.in
, System.out
and System.err
streams as well as allowing streaming of file and URL.
URI format Copier lienLien copié sur presse-papiers!
stream:in[?options] stream:out[?options] stream:err[?options] stream:header[?options]
stream:in[?options]
stream:out[?options]
stream:err[?options]
stream:header[?options]
file
and url
endpoint URIs are supported in Apache Camel 2.0:
stream:file?fileName=/foo/bar.txt stream:url[?options]
stream:file?fileName=/foo/bar.txt
stream:url[?options]
stream:header
URI is specified, the stream
header is used to find the stream to write to. This option is available only for stream producers (that is, it cannot appear in from()
).
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
delay
|
0
|
Initial delay in milliseconds before consuming or producing the stream. |
encoding
|
JVM Default |
As of 1.4, you can configure the encoding (is a charset name) to use text-based streams (for example, message body is a String object). If not provided, Apache Camel uses the JVM default Charset.
|
promptMessage
|
null
|
Apache Camel 2.0: Message prompt to use when reading from stream:in ; for example, you could set this to Enter a command:
|
promptDelay
|
0
|
Apache Camel 2.0: Optional delay in milliseconds before showing the message prompt. |
initialPromptDelay
|
2000
|
Apache Camel 2.0: Initial delay in milliseconds before showing the message prompt. This delay occurs only once. Can be used during system startup to avoid message prompts being written while other logging is done to the system out. |
fileName
|
null
|
Apache Camel 2.0: When using the stream:file URI format, this option specifies the filename to stream to/from.
|
url
|
null
|
When using the stream:url URI format, this option specifies the URL to stream to/from. The input/output stream will be opened using the JDK URLConnection facility.
|
scanStream
|
false
|
Apache Camel 2.0: To be used for continuously reading a stream such as the unix
tail command. Camel 2.4 to Camel 2.6: will retry opening the file if it is overwritten, somewhat like tail --retry
|
retry
|
false
|
Camel 2.7: will retry opening the file if it's overwritten, somewhat like tail --retry
|
scanStreamDelay
|
0
|
Apache Camel 2.0: Delay in milliseconds between read attempts when using scanStream .
|
groupLines
|
0
|
Camel 2.5: To group X number of lines in the consumer. For example to group 10 lines and therefore only spit out an Exchange with 10 lines, instead of 1 Exchange per line. |
autoCloseCount
|
0
|
*Camel 2.10.0:* (2.9.3 and 2.8.6) Number of messages to process before closing stream on Producer side. Never close stream by default (only when Producer is stopped). If more messages are sent, the stream is reopened for another autoCloseCount batch.
|
Message content Copier lienLien copié sur presse-papiers!
String
or byte[]
for writing to streams. Just add either String
or byte[]
content to the message.in.body
. Messages sent to the stream: producer in binary mode are not followed by the newline character (as opposed to the String
messages). Message with null
body will not be appended to the output stream.
Samples Copier lienLien copié sur presse-papiers!
direct:in
endpoint to the System.out
stream:
MyOutputStream
.
tail
command):
from("stream:file?fileName=/server/logs/server.log&scanStream=true&scanStreamDelay=1000").to("bean:logService?method=parseLogLine");
from("stream:file?fileName=/server/logs/server.log&scanStream=true&scanStreamDelay=1000").to("bean:logService?method=parseLogLine");
scanStream
and retry
is that the file will be re-opened and scanned with each iteration of scanStreamDelay
. Until NIO2 is available, we cannot reliably detect when a file is deleted or recreated.
Chapter 101. StringTemplate Copier lienLien copié sur presse-papiers!
String Template Copier lienLien copié sur presse-papiers!
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
string-template:templateName[?options]
string-template:templateName[?options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
contentCache
|
false
|
Cache for the resource content when its loaded. Note : as of Camel 2.9 cached resource content can be cleared via JMX using the endpoint's clearContentCache operation.
|
Headers Copier lienLien copié sur presse-papiers!
org.apache.camel.stringtemplate.resource
. The Resource is an org.springframework.core.io.Resource
object.
Hot reloading Copier lienLien copié sur presse-papiers!
contentCache=true
, Apache Camel loads the resource only once and hot-reloading is not possible. This scenario can be used in production when the resource never changes.
StringTemplate Attributes Copier lienLien copié sur presse-papiers!
java.util.Map
) to the string template. The Exchange is transfered as:
key | value |
---|---|
exchange
|
The Exchange itself. |
headers
|
The headers of the In message. |
camelContext
|
The Camel Context. |
request
|
The In message. |
in
|
The In message. |
body
|
The In message body. |
out
|
The Out message (only for InOut message exchange pattern). |
response
|
The Out message (only for InOut message exchange pattern). |
Samples Copier lienLien copié sur presse-papiers!
from("activemq:My.Queue"). to("string-template:com/acme/MyResponse.tm");
from("activemq:My.Queue").
to("string-template:com/acme/MyResponse.tm");
The Email Sample Copier lienLien copié sur presse-papiers!
StringTemplate
as:
Chapter 102. Stub Copier lienLien copié sur presse-papiers!
Stub Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
stub:someUri
stub:someUri
someUri
can be any URI with any query parameters.
Examples Copier lienLien copié sur presse-papiers!
- stub:smtp://somehost.foo.com?user=whatnot&something=else
- stub:http://somehost.bar.com/something
Chapter 103. Test Copier lienLien copié sur presse-papiers!
Test Component Copier lienLien copié sur presse-papiers!
pom.xml
for this component when using Camel 2.8 or older:
URI format Copier lienLien copié sur presse-papiers!
test:expectedMessagesEndpointUri
test:expectedMessagesEndpointUri
Example Copier lienLien copié sur presse-papiers!
from("seda:someEndpoint"). to("test:file://data/expectedOutput?noop=true");
from("seda:someEndpoint").
to("test:file://data/expectedOutput?noop=true");
Chapter 104. Timer Copier lienLien copié sur presse-papiers!
Timer Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
timer:name[?options]
timer:name[?options]
name
is the name of the Timer
object, which is created and shared across endpoints. So if you use the same name for all your timer endpoints, only one Timer
object and thread will be used.
?option=value&option=value&...
null
. So exchange.getIn().getBody()
returns null
.
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
time
|
null
|
A java.util.Date the first event should be generated. If using the URI, the pattern expected is: yyyy-MM-dd HH:mm:ss or yyyy-MM-dd'T'HH:mm:ss .
|
pattern
|
null
|
Allows you to specify a custom Date pattern to use for setting the time option using URI syntax.
|
period
|
1000
|
If greater than 0, generate periodic events every period milliseconds.
|
delay
|
1000
|
The number of milliseconds to wait before the first event is generated. Should not be used in conjunction with the time option. The default value has been changed to 1000 from Camel 2.11 onwards. In older releases the default value is 0 .
|
fixedRate
|
false
|
Events take place at approximately regular intervals, separated by the specified period. |
daemon
|
true
|
Specifies whether or not the thread associated with the timer endpoint runs as a daemon. |
repeatCount
|
0
|
Camel 2.8: Specifies a maximum limit of number of fires. So if you set it to 1, the timer will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. |
Exchange Properties Copier lienLien copié sur presse-papiers!
Exchange
:
Name | Type | Description |
---|---|---|
Exchange.TIMER_NAME
|
String
|
The value of the name option.
|
Exchange.TIMER_TIME
|
Date
|
The value of the time option.
|
Exchange.TIMER_PERIOD
|
long
|
The value of the period option.
|
Exchange.TIMER_FIRED_TIME
|
Date
|
The time when the consumer fired. |
Exchange.TIMER_COUNTER
|
Long
|
Camel 2.8: The current fire counter. Starts from 1. |
Message Headers Copier lienLien copié sur presse-papiers!
Name | Type | Description |
---|---|---|
Exchange.TIMER_FIRED_TIME
|
java.util.Date
|
The time when the consumer fired |
Sample Copier lienLien copié sur presse-papiers!
from("timer://foo?fixedRate=true&period=60000").to("bean:myBean?method=someMethodName");
from("timer://foo?fixedRate=true&period=60000").to("bean:myBean?method=someMethodName");
period=60s
.
someMethodName
method on the bean called myBean
in the Registry such as JNDI or Spring.
<route> <from uri="timer://foo?fixedRate=true&eriod=60000"/> <to uri="bean:myBean?method=someMethodName"/> </route>
<route>
<from uri="timer://foo?fixedRate=true&eriod=60000"/>
<to uri="bean:myBean?method=someMethodName"/>
</route>
Firing only once Copier lienLien copié sur presse-papiers!
repeatCount
option as follows:
<route> <from uri="timer://foo?repeatCount=1"/> <to uri="bean:myBean?method=someMethodName"/> </route>
<route>
<from uri="timer://foo?repeatCount=1"/>
<to uri="bean:myBean?method=someMethodName"/>
</route>
Chapter 105. Twitter Copier lienLien copié sur presse-papiers!
Twitter Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
twitter://[endpoint]?[options]
twitter://[endpoint]?[options]
TwitterComponent: Copier lienLien copié sur presse-papiers!
Option | Description |
---|---|
consumerKey | The consumer key |
consumerSecret | The consumer secret |
accessToken | The access token |
accessTokenSecret | The access token secret |
Consumer Endpoints: Copier lienLien copié sur presse-papiers!
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: Copier lienLien copié sur presse-papiers!
Endpoint | Body Type |
---|---|
directmessage | String |
search | List<twitter4j.Tweet> |
timeline/user | String |
URI Options Copier lienLien copié sur presse-papiers!
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 Copier lienLien copié sur presse-papiers!
Use cases Copier lienLien copié sur presse-papiers!
To create a status update within your Twitter profile, send this producer a String body. Copier lienLien copié sur presse-papiers!
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]);
To poll, every 5 sec., all statuses on your home timeline: Copier lienLien copié sur presse-papiers!
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': Copier lienLien copié sur presse-papiers!
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 Copier lienLien copié sur presse-papiers!
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]");
Searching using a producer with dynamic keywords from header Copier lienLien copié sur presse-papiers!
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 Copier lienLien copié sur presse-papiers!
Chapter 106. Validation Copier lienLien copié sur presse-papiers!
Validation Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
validator:someLocalOrRemoteResource
validator:someLocalOrRemoteResource
msv:org/foo/bar.xsd
msv:file:../foo/bar.xsd
validator:com/mypackage/myschema.xsd
pom.xml
for this component when using Camel 2.8 or older:
Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
resourceResolver
|
null
|
*Camel 2.9:* Reference to a org.w3c.dom.ls.LSResourceResolver in the Registry.
|
useDom
|
false
|
Apache Camel 2.0: Whether DOMSource /{{DOMResult}} or SaxSource /{{SaxResult}} should be used by the validator.
|
useSharedSchema
|
true
|
Camel 2.3: Whether the Schema instance should be shared or not. This option is introduced to work around a JDK 1.6.x bug. Xerces should not have this issue.
|
failIfNoBody
|
true
|
*Camel 2.9.5/2.10.3:* Whether to fail if no body exists. |
Example Copier lienLien copié sur presse-papiers!
Chapter 107. Velocity Copier lienLien copié sur presse-papiers!
Velocity Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
velocity:templateName[?options]
velocity:templateName[?options]
file://folder/myfile.vm
).
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Option | Default | Description |
---|---|---|
loaderCache
|
true
|
Velocity based file loader cache. |
contentCache
|
true
|
Cache for the resource content when it is loaded. Note : as of Camel 2.9 cached resource content can be cleared via JMX using the endpoint's clearContentCache operation.
|
encoding
|
null
|
Character encoding of the resource content. |
propertiesFile
|
null
|
New option in Camel 2.1: The URI of the properties file which is used for VelocityEngine initialization. |
Velocity Context Copier lienLien copié sur presse-papiers!
Map
). The Exchange
is transfered as:
key | value |
---|---|
exchange
|
The Exchange itself.
|
exchange.properties
|
The Exchange properties.
|
headers
|
The headers of the In message. |
camelContext
|
The Camel Context intance. |
request
|
The In message. |
in
|
The In message. |
body
|
The In message body. |
out
|
The Out message (only for InOut message exchange pattern). |
response
|
The Out message (only for InOut message exchange pattern). |
Hot reloading Copier lienLien copié sur presse-papiers!
contentCache=true
, Apache Camel will only load the resource once, and thus hot reloading is not possible. This scenario can be used in production, when the resource never changes.
Dynamic templates Copier lienLien copié sur presse-papiers!
Header | Type | Description |
---|---|---|
CamelVelocityResourceUri | String | Camel 2.1: A URI for the template resource to use instead of the endpoint configured. |
CamelVelocityTemplate | String | Camel 2.1: The template to use instead of the endpoint configured. |
Samples Copier lienLien copié sur presse-papiers!
from("activemq:My.Queue"). to("velocity:com/acme/MyResponse.vm");
from("activemq:My.Queue").
to("velocity:com/acme/MyResponse.vm");
JMSReplyTo
header).
from("activemq:My.Queue"). to("velocity:com/acme/MyResponse.vm"). to("activemq:Another.Queue");
from("activemq:My.Queue").
to("velocity:com/acme/MyResponse.vm").
to("activemq:Another.Queue");
.vm
template never changes:
from("activemq:My.Queue"). to("velocity:com/acme/MyResponse.vm?contentCache=true"). to("activemq:Another.Queue");
from("activemq:My.Queue").
to("velocity:com/acme/MyResponse.vm?contentCache=true").
to("activemq:Another.Queue");
from("activemq:My.Queue"). to("velocity:file://myfolder/MyResponse.vm?contentCache=true"). to("activemq:Another.Queue");
from("activemq:My.Queue").
to("velocity:file://myfolder/MyResponse.vm?contentCache=true").
to("activemq:Another.Queue");
from("direct:in"). setHeader("CamelVelocityResourceUri").constant("path/to/my/template.vm"). to("velocity:dummy");
from("direct:in").
setHeader("CamelVelocityResourceUri").constant("path/to/my/template.vm").
to("velocity:dummy");
from("direct:in"). setHeader("CamelVelocityTemplate").constant("Hi this is a velocity template that can do templating ${body}"). to("velocity:dummy");
from("direct:in").
setHeader("CamelVelocityTemplate").constant("Hi this is a velocity template that can do templating ${body}").
to("velocity:dummy");
The Email Sample Copier lienLien copié sur presse-papiers!
Chapter 108. VM Copier lienLien copié sur presse-papiers!
VM Component Copier lienLien copié sur presse-papiers!
camel-core.jar
is on the system/boot
classpath).
URI format Copier lienLien copié sur presse-papiers!
vm:queueName[?options]
vm:queueName[?options]
queueName
can be any string to uniquely identify the endpoint within the JVM (or at least within the classloader that loaded camel-core.jar)
?option=value&option=value&...
queueName
portion of the URI is identical. For example:
from("direct:foo").to("vm:bar?concurrentConsumers=5"); from("vm:bar?concurrentConsumers=5").to("file://output");
from("direct:foo").to("vm:bar?concurrentConsumers=5");
from("vm:bar?concurrentConsumers=5").to("file://output");
bar
, we could rewrite the previous exmple as follows:
from("direct:foo").to("vm:bar"); from("vm:bar?concurrentConsumers=5").to("file://output");
from("direct:foo").to("vm:bar");
from("vm:bar?concurrentConsumers=5").to("file://output");
Options Copier lienLien copié sur presse-papiers!
Samples Copier lienLien copié sur presse-papiers!
order.email
:
from("direct:in").bean(MyOrderBean.class).to("vm:order.email");
from("direct:in").bean(MyOrderBean.class).to("vm:order.email");
.war
application):
from("vm:order.email").bean(MyOrderEmailSender.class);
from("vm:order.email").bean(MyOrderEmailSender.class);
Chapter 109. Websocket Copier lienLien copié sur presse-papiers!
Websocket Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
websocket://hostname[:port][/resourceUri][?options]
websocket://hostname[:port][/resourceUri][?options]
?option=value&option=value&...
Component Options Copier lienLien copié sur presse-papiers!
WebsocketComponent
can be configured prior to use, to setup host, to act as a websocket server.
Option | Default | Description |
---|---|---|
host | 0.0.0.0 | The hostname. |
port | 9292 | The port number. |
staticResources |
null
|
Path for static resources such as index.html files etc. If this option has been configured, then a server is started on the given hostname and port, to service the static resources, eg such as an index.html file. If this option has not been configured, then no server is started. |
sslContextParameters |
Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
|
|
enableJmx
|
false
|
If this option is true, Jetty JMX support will be enabled for this endpoint. |
sslKeyPassword
|
null
|
*Consumer only*: The password for the keystore when using SSL. |
sslPassword
|
null
|
*Consumer only*: The password when using SSL. |
sslKeystore
|
null
|
*Consumer only*: The path to the keystore. |
minThreads
|
null
|
*Consumer only*: To set a value for minimum number of threads in server thread pool. |
maxThreads
|
null
|
*Consumer only*: To set a value for maximum number of threads in server thread pool. |
threadPool
|
null
|
*Consumer only*: To use a custom thread pool for the server. |
Endpoint Options Copier lienLien copié sur presse-papiers!
WebsocketEndpoint
can be configured prior to use
Option | Default | Description |
---|---|---|
sslContextParameters |
Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
|
|
sendToAll |
null
|
*Producer only:* To send to all websocket subscribers. Can be used to configure on endpoint level, instead of having to use the WebsocketConstants.SEND_TO_ALL header on the message.
|
staticResources |
null
|
The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. |
Message Headers Copier lienLien copié sur presse-papiers!
Key | Description |
---|---|
WebsocketConstants.SEND_TO_ALL
|
Sends the message to all clients which are currently connected. You can use the sendToAll option on the endpoint instead of using this header.
|
WebsocketConstants.CONNECTION_KEY
|
Sends the message to the client with the given connection key. |
Usage Copier lienLien copié sur presse-papiers!
0.0.0.0:9292
. The example will send back an echo of the input. To send back a message, we need to send the transformed message to the same endpoint "websocket://echo"
. This is needed because by default the messaging is InOnly.
from("activemq:topic:newsTopic") .routeId("fromJMStoWebSocket") .to("websocket://localhost:8443/newsTopic?sendToAll=true&staticResources=classpath:webapp");
from("activemq:topic:newsTopic")
.routeId("fromJMStoWebSocket")
.to("websocket://localhost:8443/newsTopic?sendToAll=true&staticResources=classpath:webapp");
Setting up SSL for WebSocket Component Copier lienLien copié sur presse-papiers!
Using the JSSE Configuration Utility Copier lienLien copié sur presse-papiers!
Programmatic configuration of the component Copier lienLien copié sur presse-papiers!
Spring DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
Java DSL based configuration of endpoint Copier lienLien copié sur presse-papiers!
- Twitter Websocket Example demonstrates how to poll a constant feed of twitter searches and publish results in real time using web socket to a web page.
Chapter 110. XMPP Copier lienLien copié sur presse-papiers!
XMPP Component Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
xmpp://[login@]hostname[:port][/participant][?Options]
xmpp://[login@]hostname[:port][/participant][?Options]
?option=value&option=value&...
Options Copier lienLien copié sur presse-papiers!
Name | Description |
---|---|
room
|
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 superman@jabber.org and want to join the krypton room, then the room URL is krypton@conference.jabber.org . Note the conference part.
|
user
|
User name (without server name). If not specified, anonymous login will be attempted. |
password
|
Password. |
resource
|
XMPP resource. The default is Camel .
|
createAccount
|
If true , an attempt to create an account will be made. Default is false .
|
participant
|
JID (Jabber ID) of person to receive messages. room parameter has precedence over participant .
|
nickname
|
Use nickname when joining room. If room is specified and nickname is not, user will be used for the nickname.
|
serviceName
|
The name of the service you are connecting to. For Google Talk, this would be gmail.com .
|
testConnectionOnStartup
|
*Camel 2.11* 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 .
|
connectionPollDelay
|
*Camel 2.11* The amount of time in seconds between polls 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 .
|
Headers and setting Subject or Language Copier lienLien copié sur presse-papiers!
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.
Examples Copier lienLien copié sur presse-papiers!
superman
to join room krypton
at jabber
server with password, secret
:
xmpp://superman@jabber.org/?room=krypton@conference.jabber.org&password=secret
xmpp://superman@jabber.org/?room=krypton@conference.jabber.org&password=secret
superman
to send messages to joker
:
xmpp://superman@jabber.org/joker@jabber.org?password=secret
xmpp://superman@jabber.org/joker@jabber.org?password=secret
from("timer://kickoff?period=10000"). setBody(constant("I will win!\n Your Superman.")). to("xmpp://superman@jabber.org/joker@jabber.org?password=secret");
from("timer://kickoff?period=10000").
setBody(constant("I will win!\n Your Superman.")).
to("xmpp://superman@jabber.org/joker@jabber.org?password=secret");
joker
into the queue, evil.talk
.
from("xmpp://superman@jabber.org/joker@jabber.org?password=secret"). to("activemq:evil.talk");
from("xmpp://superman@jabber.org/joker@jabber.org?password=secret").
to("activemq:evil.talk");
from("xmpp://superman@jabber.org/?password=secret&room=krypton@conference.jabber.org"). to("activemq:krypton.talk");
from("xmpp://superman@jabber.org/?password=secret&room=krypton@conference.jabber.org").
to("activemq:krypton.talk");
from("xmpp://superman@jabber.org/?password=secret&room=krypton"). to("activemq:krypton.talk");
from("xmpp://superman@jabber.org/?password=secret&room=krypton").
to("activemq:krypton.talk");
serviceName
as well as your credentials:
// send a message from fromuser@gmail.com to touser@gmail.com from("direct:start"). to("xmpp://talk.google.com:5222/touser@gmail.com?serviceName=gmail.com&user=fromuser&password=secret"). to("mock:result");
// send a message from fromuser@gmail.com to touser@gmail.com
from("direct:start").
to("xmpp://talk.google.com:5222/touser@gmail.com?serviceName=gmail.com&user=fromuser&password=secret").
to("mock:result");
Chapter 111. XQuery Endpoint Copier lienLien copié sur presse-papiers!
XQuery Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
xquery:templateName
xquery:templateName
from("activemq:My.Queue"). to("xquery:com/acme/mytransform.xquery");
from("activemq:My.Queue").
to("xquery:com/acme/mytransform.xquery");
JMSReplyTo
header).
from("activemq:My.Queue"). to("xquery:com/acme/mytransform.xquery"). to("activemq:Another.Queue");
from("activemq:My.Queue").
to("xquery:com/acme/mytransform.xquery").
to("activemq:Another.Queue");
Chapter 112. XSLT Copier lienLien copié sur presse-papiers!
XSLT Copier lienLien copié sur presse-papiers!
URI format Copier lienLien copié sur presse-papiers!
xslt:templateName[?options]
xslt:templateName[?options]
?option=value&option=value&...
URI | Description |
---|---|
xslt:com/acme/mytransform.xsl
|
Refers to the file, com/acme/mytransform.xsl , on the classpath.
|
xslt:file:///foo/bar.xsl
|
Refers to the file, /foo/bar.xsl .
|
xslt:http://acme.com/cheese/foo.xsl
|
Refers to the remote HTTP resource. |
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
converter
|
null
|
Option to override default XmlConverter. Will lookup for the converter in the Registry. The provided converted must be of type org.apache.camel.converter.jaxp.XmlConverter. |
transformerFactory
|
null
|
Option to override default TransformerFactory. Will lookup for the transformerFactory in the Registry. The provided transformer factory must be of type javax.xml.transform.TransformerFactory .
|
transformerFactoryClass
|
null
|
Option to override default TransformerFactory. Will create a TransformerFactoryClass instance and set it to the converter.
|
uriResolver
|
null
|
Camel 2.3: Allows you to use a custom javax.xml.transformation.URIResolver . Camel will by default use its own implementation org.apache.camel.builder.xml.XsltUriResolver which is capable of loading from classpath.
|
resultHandlerFactory
|
null
|
Camel 2.3: Allows you to use a custom org.apache.camel.builder.xml.ResultHandlerFactory which is capable of using custom org.apache.camel.builder.xml.ResultHandler types.
|
failOnNullBody
|
true
|
Camel 2.3: Whether or not to throw an exception if the input body is null. |
deleteOutputFile
|
false
|
Camel 2.6: If you have output=file then this option dictates whether or not the output file should be deleted when the Exchange is done processing. For example suppose the output file is a temporary file, then it can be a good idea to delete it after use.
|
output
|
string
|
Camel 2.3: Option to specify which output type to use. Possible values are: string, bytes, DOM, file . The first three options are all in memory based, where as file is streamed directly to a java.io.File . For file you must specify the filename in the IN header with the key Exchange.XSLT_FILE_NAME which is also CamelXsltFileName . Also any paths leading to the filename must be created beforehand, otherwise an exception is thrown at runtime.
|
contentCache
|
true
|
Camel 2.6: Cache for the resource content (the stylesheet file) when it is loaded. If set to false Camel will reloader the stylesheet file on each message processing. This is good for development.
|
allowStAX
|
false
|
*Camel 2.8.3/2.9:* Whether to allow using StAX as the javax.xml.transform.Source .
|
transformerCacheSize
|
0
|
*Camel 2.9.3/2.10.1:* The number of javax.xml.transform.Transformer object that are cached for reuse to avoid calls to Template.newTransformer() .
|
Using XSLT endpoints Copier lienLien copié sur presse-papiers!
from("activemq:My.Queue"). to("xslt:com/acme/mytransform.xsl");
from("activemq:My.Queue").
to("xslt:com/acme/mytransform.xsl");
JMSReplyTo
header).
from("activemq:My.Queue"). to("xslt:com/acme/mytransform.xsl"). to("activemq:Another.Queue");
from("activemq:My.Queue").
to("xslt:com/acme/mytransform.xsl").
to("activemq:Another.Queue");
Getting Parameters into the XSLT to work with Copier lienLien copié sur presse-papiers!
<setHeader headerName="myParam"><constant>42</constant></setHeader> <to uri="xslt:MyTransform.xsl"/>
<setHeader headerName="myParam"><constant>42</constant></setHeader>
<to uri="xslt:MyTransform.xsl"/>
<xsl: ...... > <xsl:param name="myParam"/> <xsl:template ...>
<xsl: ...... >
<xsl:param name="myParam"/>
<xsl:template ...>
Spring XML versions Copier lienLien copié sur presse-papiers!
Using xsl:include Copier lienLien copié sur presse-papiers!
URIResolver
which allows Camel to load included files from the classpath and more intelligent than before.
<xsl:include href="staff_template.xsl"/>
<xsl:include href="staff_template.xsl"/>
.to("xslt:org/apache/camel/component/xslt/staff_include_relative.xsl")
.to("xslt:org/apache/camel/component/xslt/staff_include_relative.xsl")
org/apache/camel/component/xslt/staff_template.xsl
. This allows you to use xsl include and have xsl files located in the same folder such as we do in the example org/apache/camel/component/xslt
.
classpath:
or file:
to instruct Camel to look either in classpath or file system. If you omit the prefix then Camel uses the prefix from the endpoint configuration. If that neither has one, then classpath is assumed.
<xsl:include href="../staff_other_template.xsl"/>
<xsl:include href="../staff_other_template.xsl"/>
org/apache/camel/component
.
Dynamic stylesheets Copier lienLien copié sur presse-papiers!
CamelXsltResourceUri
header which you can use to define a stylesheet to use instead of what is configured on the endpoint URI. This allows you to provide a dynamic stylesheet at runtime.
Chapter 113. Zookeeper Copier lienLien copié sur presse-papiers!
ZooKeeper Copier lienLien copié sur presse-papiers!
- Creation of nodes in any of the ZooKeeper create modes.
- Get and Set the data contents of arbitrary cluster nodes.
- Create and retrieve the list the child nodes attached to a particular node.
- A Distributed RoutePolicy that leverages a Leader election coordinated by ZooKeeper to determine if exchanges should get processed.
pom.xml
for this component:
URI format Copier lienLien copié sur presse-papiers!
zookeeper://zookeeper-server[:port][/path][?options]
zookeeper://zookeeper-server[:port][/path][?options]
Options Copier lienLien copié sur presse-papiers!
Name | Default Value | Description |
---|---|---|
sessionId
|
null
|
The session id used to identify a connection to the cluster |
password
|
null
|
The password to use when making a connection |
awaitCreation
|
true
|
should the endpoint await the creation of a node that does not yet exist. |
listChildren
|
false
|
whether the children of the node should be listed |
repeat
|
false
|
should changes to the znode be 'watched' and repeatedly processed. |
backoff
|
5000
|
the time interval to backoff for after an error before retrying. |
timeout
|
5000
|
the time interval to wait on connection before timing out. |
create
|
false
|
should the endpoint create the node if it does not currently exist. |
createMode
|
EPHEMERAL
|
the create mode that should be used for the newly created node (see below). |
sendEmptyMessageOnDelete
|
true
|
*Camel 2.10:* upon the delete of a znode, should an empty message be send to the consumer |
Use cases Copier lienLien copié sur presse-papiers!
Reading from a znode. Copier lienLien copié sur presse-papiers!
from("zookeeper://localhost:39913/somepath/somenode").to("mock:result");
from("zookeeper://localhost:39913/somepath/somenode").to("mock:result");
from("zookeeper://localhost:39913/somepath/somenode?awaitCreation=true").to("mock:result");
from("zookeeper://localhost:39913/somepath/somenode?awaitCreation=true").to("mock:result");
Reading from a znode - (additional Camel 2.10 onwards) Copier lienLien copié sur presse-papiers!
Writing to a znode. Copier lienLien copié sur presse-papiers!
from("direct:write-to-znode").to("zookeeper://localhost:39913/somepath/somenode");
from("direct:write-to-znode").to("zookeeper://localhost:39913/somepath/somenode");
Exchange e = createExchangeWithBody(testPayload); template.sendBodyAndHeader("direct:write-to-znode", e, "CamelZooKeeperNode", "/somepath/someothernode");
Exchange e = createExchangeWithBody(testPayload);
template.sendBodyAndHeader("direct:write-to-znode", e, "CamelZooKeeperNode", "/somepath/someothernode");
from("direct:create-and-write-to-znode").to("zookeeper://localhost:39913/somepath/somenode?create=true");
from("direct:create-and-write-to-znode").to("zookeeper://localhost:39913/somepath/somenode?create=true");
- PERSISTENT
- PERSISTENT_SEQUENTIAL
- EPHEMERAL
- EPHEMERAL_SEQUENTIAL
from("direct:create-and-write-to-persistent-znode").to("zookeeper://localhost:39913/somepath/somenode?create=true&createMode=PERSISTENT");
from("direct:create-and-write-to-persistent-znode").to("zookeeper://localhost:39913/somepath/somenode?create=true&createMode=PERSISTENT");
Exchange e = createExchangeWithBody(testPayload); template.sendBodyAndHeader("direct:create-and-write-to-persistent-znode", e, "CamelZooKeeperCreateMode", "PERSISTENT");
Exchange e = createExchangeWithBody(testPayload);
template.sendBodyAndHeader("direct:create-and-write-to-persistent-znode", e, "CamelZooKeeperCreateMode", "PERSISTENT");
ZooKeeper enabled Route policy. Copier lienLien copié sur presse-papiers!
ZooKeeperRoutePolicy policy = new ZooKeeperRoutePolicy("zookeeper:localhost:39913/someapp/somepolicy", 1); from("direct:policy-controlled").routePolicy(policy).to("mock:controlled");
ZooKeeperRoutePolicy policy = new ZooKeeperRoutePolicy("zookeeper:localhost:39913/someapp/somepolicy", 1);
from("direct:policy-controlled").routePolicy(policy).to("mock:controlled");
Legal Notice Copier lienLien copié sur presse-papiers!
Trademark Disclaimer
Legal Notice Copier lienLien copié sur presse-papiers!
Third Party Acknowledgements
- JLine (http://jline.sourceforge.net) jline:jline:jar:1.0License: BSD (LICENSE.txt) - Copyright (c) 2002-2006, Marc Prud'hommeaux
mwp1@cornell.edu
All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of JLine nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - Stax2 API (http://woodstox.codehaus.org/StAX2) org.codehaus.woodstox:stax2-api:jar:3.1.1License: The BSD License (http://www.opensource.org/licenses/bsd-license.php)Copyright (c) <YEAR>, <OWNER> All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - jibx-run - JiBX runtime (http://www.jibx.org/main-reactor/jibx-run) org.jibx:jibx-run:bundle:1.2.3License: BSD (http://jibx.sourceforge.net/jibx-license.html) Copyright (c) 2003-2010, Dennis M. Sosnoski.All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of JiBX nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - JavaAssist (http://www.jboss.org/javassist) org.jboss.javassist:com.springsource.javassist:jar:3.9.0.GA:compileLicense: MPL (http://www.mozilla.org/MPL/MPL-1.1.html)
- HAPI-OSGI-Base Module (http://hl7api.sourceforge.net/hapi-osgi-base/) ca.uhn.hapi:hapi-osgi-base:bundle:1.2License: Mozilla Public License 1.1 (http://www.mozilla.org/MPL/MPL-1.1.txt)