Camel 2.15.0 release (currently in progress)

New and Noteworthy

Welcome to the 2.15.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

highlighted issue fixed
highlighted issue fixed

New Enterprise Integration Patterns

New DSL

New Annotations

API breaking

Known Issues

Dependency Upgrades

CXF 3.0.1 to 3.0.2
Guava 17.0 to 18.0
Spring Security 3.1.7.RELEASE to 3.2.5.RELEASE

Important changes to consider when upgrading

Getting the Distr ibutions

Binary Distributions

Description	Download Link	PGP Signature file of download
Windows Distribution	apache-camel-2.15.0.zip	apache-camel-2.15.0.zip.asc
Unix/Linux/Cygwin Dis tribution	apache-camel-2.15.0.tar.gz	apache-camel-2.15.0.tar.gz.asc

+

Camel 2.15.0 release (currently in progress)

New and Noteworthy

Welcome to the 2.15.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

highlighted issue fixed
highlighted issue fixed

New Enterprise Integration Patterns

New Components

camel-beanstalk - for working with Amazon Beanstalk jobs.

New DSL

New Annotations

API breaking

Known Issues

Dependency Upgrades

Codahale Metrics 3.0 to 3.1
CXF 3.0.1 to 3.0.2
Guava 17.0 to 18.0
Spring Security 3.1.7.RELEASE to 3.2.5.RELEASE

Important changes to consider when upgrading

Spring 4.x is now the default out of the box Spring version.

Getting the Distributions

Binary Distributions

Description	Download Link	PGP Signature file of download
Windows Distribution	apache-camel-2.15.0.zip	apache-camel-2.15.0.zip.asc
Unix/Linux/Cygwin Distribution	apache-camel-2.15.0.tar.gz	apache-camel-2.15.0.tar.gz.asc

The above URLs use redirection

Icon

Modified: websites/production/camel/content/component-list.html ============================================================================== --- websites/production/camel/content/component-list.html (original) +++ websites/production/camel/content/component-list.html Sun Sep 21 09:18:43 2014 @@ -132,7 +132,7 @@

For working with Amazon's Simple Storage Service (S3).

Bean / 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).

Beanstalk / camel-beanstalk

+

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).

Beanstalk / camel-beanstalk

For working with Amazon's Beanstalk.

Bean Validator / camel-bean-validator

Modified: websites/production/camel/content/components.html
==============================================================================
--- websites/production/camel/content/components.html (original)
+++ websites/production/camel/content/components.html Sun Sep 21 09:18:43 2014
@@ -141,7 +141,7 @@
 

For working with Amazon's Simple Storage Service (S3).

Bean / 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).

Beanstalk / camel-beanstalk

+

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).

Beanstalk / camel-beanstalk

For working with Amazon's Beanstalk.

Bean Validator / camel-bean-validator

Modified: websites/production/camel/content/polling-consumer.html
==============================================================================
--- websites/production/camel/content/polling-consumer.html (original)
+++ websites/production/camel/content/polling-consumer.html Sun Sep 21 09:18:43 2014
@@ -91,9 +91,7 @@
 PollingConsumer consumer = endpoint.createPollingConsumer();
 Exchange exchange = consumer.receive();
 ]]>
-

The ConsumerTemplate (discussed below) is also available.

There are 3 main polling methods on PollingConsumer

Method name	Description
receive()	Waits until a message is available and then returns it; potentially blocking forever
receive(long)	Attempts to receive a message exchange, waiting up to the given timeout and returning null if no message exchange could be received within the time available
receiveNoWait()	Attempts to receive a message exchange immediately without waiting and returning null if a message exchange is not available yet

EventDrivenPollingConsumer Options

The EventDrivePollingConsumer (the default implementation) supports the following options:

-

Option	Default	Description
`pollingConsumerQueueSize`	`1000`	Camel 2.14/2.13.1/2.12.4: The queue size for the internal handoff queue between the polling consumer, and producers sending data into the queue.
`pollingConsumerBlockWhenFull`	`true`	Camel 2.14/2.13.1/2.12/4: Whether to block any producer if the internal queue is full.

-

Notice that some Camel Components has their own implementation of PollingConsumer and therefore do not support the options above.

You can configure these options in endpoints URIs, such as shown below:

+

The ConsumerTemplate (discussed below) is also available.

There are 3 main polling methods on PollingConsumer

Method name	Description
receive()	Waits until a message is available and then returns it; potentially blocking forever
receive(long)	Attempts to receive a message exchange, waiting up to the given timeout and returning null if no message exchange could be received within the time available
receiveNoWait()	Attempts to receive a message exchange immediately without waiting and returning null if a message exchange is not available yet

EventDrivenPollingConsumer Options

The EventDrivePollingConsumer (the default implementation) supports the following options:

Option	Default	Description
`pollingConsumerQueueSize`	`1000`	Camel 2.14/2.13.1/2.12.4: The queue size for the internal handoff queue between the polling consumer, and producers sending data into the queue.
`pollingConsumerBlockWhenFull`	`true`	Camel 2.14/2.13.1/2.12/4: Whether to block any producer if the internal queue is full.

Notice that some Camel Components has their own implementation of PollingConsumer and therefore do not support the options above.

You can configure these options in endpoints URIs, such as shown below:

 
@@ -204,10 +202,7 @@ public static class MyCoolBean {
     }
 }
 ]]>
-

Scheduled Poll Components

Quite a few inbound Camel endpoints use a scheduled poll pattern to receive messages and push them through the Camel processing routes. That is to say externally from the client the endpoint appears to use an Event Driven Consumer but internally a scheduled poll is used to monitor some kind of state or resource and then fire message exchanges.

Since this a such a common pattern, polling components can extend the ScheduledPollConsumer base class which makes it simpler to implement this pattern.

There is also the Quartz Component which provides scheduled delivery of messages using the Quartz enterprise scheduler.

For more details s ee:

PollingConsumer
Scheduled Polling Components

ScheduledPollConsumer Options

The ScheduledPollConsumer supports the following options:

-

Option	Default	Description
`pollStrategy`	-	A pluggable `org.apache.camel.PollingConsumerPollingStrategy` allowing you to provide your custom implementation to control error handling usually occurred during the `poll` operation before an Exchange have been created and being routed in Camel. In other words the error occurred while the polling was gathering information, for instance access to a file network failed so Camel cannot access it to scan for files. The default implementation will log the caused exception at `WARN` level and ignore it.
`sendEmptyMessageWhenIdle`	`false`	Camel 2.9: If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.
`startScheduler`	`true`	Whether the scheduler should be auto started.
`initialDelay`	`1000`	Milliseconds before the first poll starts.
`delay`	`500`	Milliseconds before the next poll.
`useFixedDelay`		Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. In Camel 2.7.x or older the default value is `false`. From Camel 2.8 onwards the default value is `true`.
`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.
`scheduledExecutorService`	`null`	Camel 2.10: Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. This option allows you to share a thread pool among multiple consumers.
`greedy`	`false`	Camel 2.10.6/2.11.1: If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.
`scheduler`	`null`	Camel 2.12: Allow to plugin a custom `org.apache.camel.spi.ScheduledPollConsumerScheduler` to use as the scheduler for firing when the polling consumer runs. The default implementation uses the `ScheduledExecutorService` and there is a Quartz2, and Spring based which supports CRON expressions. Notice: If using a custom scheduler then the options for `initialDelay`, `useFixedDelay`, `timeUnit`, and `scheduledExecutorService` ma y not be in use. Use the text `quartz2` to refer to use the Quartz2 scheduler; and use the text `spring` to use the Spring based; and use the text `#myScheduler` to refer to a custom scheduler by its id in the Registry. See Quartz2 page for an example.
`scheduler.xxx`	`null`	Camel 2.12: To configure additional properties when using a custom `scheduler` or any of the Quartz2, Spring based scheduler.
`b ackoffMultiplier`	`0`	Camel 2.12: To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then `backoffIdleThreshold` and/or `backoffErrorThreshold` must also be configured.
`backoffIdleThreshold`	`0`	Camel 2.12: The number of subsequent idle polls that should happen before the `backoffMultipler` should kick-in.
`backoffErrorThreshold`	`0`	Camel 2.12: The number of subsequent error polls (failed due some error) that should happen before the `backoffMultipler` should kick-in.

-

Using backoff to let the scheduler be less aggressive

Available as of Camel 2.12

The scheduled Polling Consumer is by default static by using the same poll frequency whether or not there is messages to pickup or not. From Camel 2.12 onwards you can configure the scheduled Polling Consumer to be more dynamic by using backoff. This allows the scheduler to skip N number of polls when it becomes idle, or there has been X number of errors in a row. See more details in the table above for the backoffXXX options.

For example to let a FTP consumer backoff if its becoming idle for a while you can do:

+

Scheduled Poll Components

Quite a few inbound Camel endpoints use a scheduled poll pattern to receive messages and push them through the Camel processing routes. That is to say externally from the client the endpoint appears to use an Event Driven Consumer but internally a scheduled poll is used to monitor some kind of state or resource and then fire message exchanges.

Since this a such a common pattern, polling components can extend the ScheduledPollConsumer base class which makes it simpler to implement this pattern.

There is also the Quartz Component which provides scheduled delivery of messages using the Quartz enterprise scheduler.

For more details s ee:

PollingConsumer
Scheduled Polling Components

ScheduledPollConsumer Options

The ScheduledPollConsumer supports the following options:

Option	Default	Description
`pollStrategy`		A pluggable `org.apache.camel.PollingConsumerPollingStrategy` allowing you to provide your custom implementation to control error handling usually occurred during the `poll` operation before an Exchange have been created and being routed in Camel. In other words the error occurred while the polling was gathering information, for instance access to a file network failed so Camel cannot access it to scan for files. The default implementation will log the caused exception at `WARN` level and ignore it.
`sendEmptyMessageWhenIdle`	`false`	Camel 2.9: If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.
`startScheduler`	`true`	Wh ether the scheduler should be auto started.
`initialDelay`	`1000`	Milliseconds before the first poll starts.
`delay`	`500`	Milliseconds before the next poll.
`useFixedDelay`		Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. In Camel 2.7.x or older the default value is `false`. From Camel 2.8 onwards the default value is `true`.
`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.
scheduledExecutorService	`null`	Camel 2.10: Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. This option allows you to share a thread pool among multiple consumers.
`greedy`	`false`	Camel 2.10.6/2.11.1: If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.
`scheduler`	`null`	Camel 2.12: Allow to plugin a custom `org.apache.camel.spi.ScheduledPollConsumerScheduler` to use as the scheduler for firing when the polling consumer runs. The default implementation uses the `ScheduledExecutorService` and there is a Quartz2, and Spring based which supports CRON expressions. Notice: If using a custom scheduler then the options for `initialDelay`, `useFixedDelay`, `timeUnit`, and `scheduledExecutorService` may not be in use. Use the text `quartz2` to refer to use the Quartz2 scheduler; and use the text `spring` to use the Spring based; and use the text `#myScheduler` to refer to a custom scheduler by its id in the Registry. See Quartz2 page for an example.
`scheduler.xxx`	`null`	Camel 2.12: To configure additional properties when using a custom `scheduler` or any of the Quartz2, Spring based scheduler.
`backoffMultiplier`	`0`	Camel 2.12: To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then `backoffIdleThreshold` and/or `backoffErrorThreshold` must also be configured.
`backoffIdleThreshold`	`0`	Camel 2.12: The number of subsequent idle polls that should happen before the `backoffMultipler` should kick-in.
`backoffErrorThreshold`	`0`	Camel 2.12: The number of subsequent error polls (failed due some error) that should happen before the `backoffMultipler` should kick-in.

Using backoff to let the scheduler be less aggressive

Available as of Camel 2.12

The scheduled Polling Consumer is by default static by using the same poll frequency whether or not there is messages to pickup or not. From Camel 2.12 onwards you can configure the scheduled Polling Consumer to be more dynamic by using backoff. This allows the scheduler to skip N number of polls when it becomes idle, or there has been X number of errors in a row. See more details in the table above for the backoffXXX options.

For example to let a FTP consumer backoff if its becoming idle for a while you can do:

 

Modified: websites/production/camel/content/transport.html
==============================================================================
--- websites/production/camel/content/transport.html (original)
+++ websites/production/camel/content/transport.html Sun Sep 21 09:18:43 2014
@@ -145,7 +145,7 @@
 

For working with Amazon's Simple Storage Service (S3).

Bean / 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).

Beanstalk / camel-beanstalk

+

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).

Beanstalk / camel-beanstalk

For working with Amazon's Beanstalk.

Bean Validator / camel-bean-validator

Modified: websites/production/camel/content/uris.html
==============================================================================
--- websites/production/camel/content/uris.html (original)
+++ websites/production/camel/content/uris.html Sun Sep 21 09:18:43 2014
@@ -150,7 +150,7 @@
 

For working with Amazon's Simple Storage Service (S3).

Bean / 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).

Beanstalk / camel-beanstalk

+

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).

Beanstalk / camel-beanstalk

For working with Amazon's Beanstalk.

Bean Validator / camel-bean-validator

EventDrivenPollingConsumer Options

EventDrivenPollingConsumer Options

Scheduled Poll Components

ScheduledPollConsumer Options

Using backoff to let the scheduler be less aggressive

Scheduled Poll Components

ScheduledPollConsumer Options

Using backoff to let the scheduler be less aggressive

Camel 2.15.0 release (currently in progress)

New and Noteworthy

New Enterprise Integration Patterns

New Components

New DSL

New Annotations

New Data Formats

New Languages

New Examples

New Tutorials

API breaking

Known Issues

Dependency Upgrades

Important changes to consider when upgrading

Getting the Distr ibutions

Binary Distributions

Camel 2.15.0 release (currently in progress)

New and Noteworthy

New Enterprise Integration Patterns

New Components

New DSL

New Annotations

New Data Formats

New Languages

New Examples

New Tutorials

API breaking

Known Issues

Dependency Upgrades

Important changes to consider when upgrading

Getting the Distributions

Binary Distributions

EventDrivenPollingConsumer Options

EventDrivenPollingConsumer Options

Scheduled Poll Components

ScheduledPollConsumer Options

Using backoff to let the scheduler be less aggressive

Scheduled Poll Components

ScheduledPollConsumer Options

Using backoff to let the scheduler be less aggressive