[CONF] Apache Camel Camel 2.7.0 Release
Christian Mueller edited the page: Camel 2.7.0 Release ... Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs. Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
[CONF] Apache Camel Camel 2.7.0 Release
Christian Mueller edited the page: Camel 2.7.0 Release ... Description Download Link PGP Signature file of download Windows Distribution apache-camel-2.7.0.zip apache-camel-2.7.0.zip.asc Unix/Linux/Cygwin Distribution apache-camel-2.7.0.tar.gz apache-camel-2.7.0.tar.gz.asc Info title The above URLs use redirection The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox ...
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* The {{camel-cache}} feature cannot load the {{ehcache-failsafe.xml}} file. * The default cacheLevel on [JMS] is always {{CACHE_CONSUMER}}. However this impacts performance when using transacted=true. The workaround is to set {{cacheLevelName=CACHE_NONE}} if you use transaction.
* Stopping a route having a context scoped error handler, may cause the error handler to stop as well, causing it to not work if it was used by other routes, see [CAMEL-3878|https://issues.apache.org/jira/browse/CAMEL-3878]
h2. Important changes to consider when upgrading
...
Full Content
Camel 2.7.0 release
New and Noteworthy
Welcome to the 2.7.0 release which approx 169 issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage.
The camel-jdbc-aggregator component is merged into the camel-sql component.
Fix in Mail component for duplicate attachments, and when using starttls.
Maven 3 is now supported for
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page moved by Hadrian Zbarcea From: Apache Camel In Progress To: Apache Camel Download Children moved Change Notification Preferences View Online | Add Comment
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page edited by Hadrian Zbarcea Changes (1) ... For a more detailed view of new features and bug fixes, see the: * [release notes for 2.7.0|http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=12311211styleName=Htmlversion=12316021] 2.7.0|https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211styleName=Htmlversion=12316021] Full Content Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx 169 issues resolved (new features, improvements and bug fixes such as...) Dependency changesThe Camel 2.7.0 release has a number of major dependency changes: JDK 1.6+ is now required Spring 3.x+ is now required if using Spring slf4j is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs. Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile. Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured. Spring Integration is upgraded to Spring Integration 2.0. Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage. The camel-jdbc-aggregator component is merged into the camel-sql component. Fix in Mail component for duplicate attachments, and when using starttls. Maven 3 is now supported for building Tidy up the XML DSL to not allow nesting tags where it doesn't make sense. Internal cleanup in route preparation logic to be fully shared for all DSLs (before the XML DSLs and Java DSL was a bit different) Fixed InterceptFrom to work
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by willem jiang
Changes (2)
...
See documentation at [slf4j|http://www.slf4j.org/] for more details. * If you have developed custom Camel [Component]s and your {{Endpoint}} class extends {{DefaultEndpoint}} then its advised to use the {{doStart}} and {{doStop}} instead of {{start}} and {{stop}}.
* camel-cxf endpoint will copy the attachments between the camel message and cxf message when it works in POJO data format, please access the attachment objects from the camel message body.
* You can not access the attachment by using Message.getAttachement(id) if the camel-cxf endpoint works in POJO data format, please access the attachment objects from the camel message body.
* [camel-restlet|Restlet] has been upgraded from Restlet 1.1.x to 2.0.5 * [Servlet] does not startup Spring XML file anymore. You should startup the XML file using 100% Spring style using the ContextLoaderListener in the web.xml. See the the [Servlet Tomcat Example] example for details.
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page edited by Claus Ibsen Changes (1) ... * [JT400] can now execute program calls on the AS/400 * [Cache] now only mandates a message body for the add and update operations. This makes get operation possible for messages with no existing body. * Fixed issue when [Jetty] continuation timeouts has been triggered before [Asynchronous Routing Engine] has reply ready. This would cause Jetty to log WARN logs about illegal state. h3. New [Enterprise Integration Patterns] ... Full Content Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) Dependency changesThe Camel 2.7.0 release has a number of major dependency changes: JDK 1.6+ is now required Spring 3.x+ is now required if using Spring slf4j is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs. Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile. Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured. Spring Integration is upgraded to Spring Integration 2.0. Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage. The camel-jdbc-aggregator component is merged into the camel-sql component. Fix in Mail component for duplicate attachments, and when using starttls. Maven 3 is now supported for building Tidy up the XML DSL to not allow nesting tags where it doesn't make sense. Internal cleanup in
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* [Property placeholders|Using PropertyPlaceholder] can now be use for any kind of attributes/options in the [EIP]s in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the [Using PropertyPlaceholder] wiki page. In the Java DSL there is a new {{placeholder}} option on each [EIP] you can leverage. * The {{camel-jdbc-aggregator}} component is merged into the {{camel-sql}} component.
* Fix in [Mail] component for duplicate attachments.
* Fix in [Mail] component for duplicate attachments, and when using starttls.
* Maven 3 is now supported for building * Tidy up the XML DSL to not allow nesting tags where it doesnt make sense.
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page edited by Claus Ibsen Changes (1) ... * [Web Console] upgraded to Scalate 1.4.1, and the webpages is now precompiled * [JT400] can now execute program calls on the AS/400 * [Cache] now only mandates a message body for the add and update operations. This makes get operation possible for messages with no existing body. h3. New [Enterprise Integration Patterns] ... Full Content Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) Dependency changesThe Camel 2.7.0 release has a number of major dependency changes: JDK 1.6+ is now required Spring 3.x+ is now required if using Spring slf4j is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs. Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile. Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured. Spring Integration is upgraded to Spring Integration 2.0. Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage. The camel-jdbc-aggregator component is merged into the camel-sql component. Fix in Mail component for duplicate attachments, and when using starttls. Maven 3 is now supported for building Tidy up the XML DSL to not allow nesting tags where it doesn't make sense. Internal cleanup in route preparation logic to be fully shared for all DSLs (before the XML DSLs and Java DSL was a bit
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (3)
...
* Fixed an issue with dependency ordering when using Springs {{depends-on}} attribute between multiple {{camelContext}}. * [Servlet] component doesnt hijack Spring to start the web application anymore. Spring and CamelServlet is now independent. See more at important changes to consider when upgrading.
* Fixed all [Camel Maven Archetypes] to use new Maven format and ensured they all work out of the box. * [Web Console] upgraded to Scalate 1.4.1, and precompiled webpages to reduce footprint
h3. New [Enterprise Integration Patterns]
...
h3. New [Archetypes|Camel Maven Archetypes]
* {{camel-archetype-light-war}} {{camel-archetype-web}} added to generate a project to deploy camel routes as a WAR
h2. API breaking
...
* [camel-restlet|Restlet] has been upgraded from Restlet 1.1.x to 2.0.5 * [Servlet] does not startup Spring XML file anymore. You should startup the XML file using 100% Spring style using the ContextLoaderListener in the web.xml. See the the [Servlet Tomcat Example] example for details.
* [Camel Maven Archetypes] the archetype {{camel-archetype-war}} has been renamed to {{camel-archetype-webconsole}}.
h2. Getting the Distributions
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page edited by Claus Ibsen Changes (1) ... * Fixed all [Camel Maven Archetypes] to use new Maven format and ensured they all work out of the box. * [Web Console] upgraded to Scalate 1.4.1, and the webpages is now precompiled * [JT400] can now execute program calls on the AS/400 h3. New [Enterprise Integration Patterns] ... Full Content Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) Dependency changesThe Camel 2.7.0 release has a number of major dependency changes: JDK 1.6+ is now required Spring 3.x+ is now required if using Spring slf4j is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs. Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile. Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured. Spring Integration is upgraded to Spring Integration 2.0. Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage. The camel-jdbc-aggregator component is merged into the camel-sql component. Fix in Mail component for duplicate attachments. Maven 3 is now supported for building Tidy up the XML DSL to not allow nesting tags where it doesn't make sense. Internal cleanup in route preparation logic to be fully shared for all DSLs (before the XML DSLs and Java DSL was a bit different) Fixed InterceptFrom to work with from endpoints defined using
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (3)
...
* Fixed an issue with [Recipient List] in parallel mode, not reusing background aggregator thread * Fixed an issue with dependency ordering when using Springs {{depends-on}} attribute between multiple {{camelContext}}.
* [Servlet] component doesnt hijack Spring to start the web application anymore. Spring and CamelServlet is now independent. See more at important changes to consider when upgrading.
h3. New [Enterprise Integration Patterns]
...
* {{camel-example-osgi-rmi}}
* {{[camel-example-servlet-tomcat|Servlet Tomcat Example]}}
h3. New [Tutorials]
...
* camel-cxf endpoint will copy the attachments between the camel message and cxf message when it works in POJO data format, please access the attachment objects from the camel message body. * [camel-restlet|Restlet] has been upgraded from Restlet 1.1.x to 2.0.5
* [Servlet] does not startup Spring XML file anymore. You should startup the XML file using 100% Spring style using the ContextLoaderListener in the web.xml. See the the [Servlet Tomcat Example] example for details.
h2. Getting the Distributions
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* [Properties] component now supports JVM system properties and OS environment variables in the locations option. For example using {{file:$\{karaf.home\}/etc/foo.properties}} to refer to the {{foo.proeprties}} file in the [Apache Karaf|http://karaf.apache.org/] installation. * Fixed an issue with [Recipient List] in parallel mode, not reusing background aggregator thread
* Fixed an issue with dependency ordering when using Springs {{depends-on}} attribute between multiple {{camelContext}}.
h3. New [Enterprise Integration Patterns]
...
* {{camel-script}} which uses {{ScriptEngineManager}} from the JDK, cannot load script engines from packages outside the JDK. * Stopping a route after using {{adviceWith}} maybe cause issues with error handlers, see [CAMEL-3534|https://issues.apache.org/jira/browse/CAMEL-3534]
* The project cannot fully build the site using Maven (eg running {{mvn site}}. There is no plan to make this work as the project do not use the maven site.
h2. Important changes to consider when upgrading
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* Stopping a route after using {{adviceWith}} maybe cause issues with error handlers, see [CAMEL-3534|https://issues.apache.org/jira/browse/CAMEL-3534] * The project cannot fully build the site using Maven (eg running {{mvn site}}. There is no plan to make this work as the project do not use the maven site.
* The [CXF Tomcat Example] does not work on Tomcat 7 due a bug in [Apache CXF|https://issues.apache.org/jira/browse/CXF-3362].
* The [CXF Tomcat Example] does not work on Tomcat 7 due a bug in [Apache CXF 2.3.3|https://issues.apache.org/jira/browse/CXF-3362] that camel-cxf uses by default. When CXF 2.3.4 is released you can upgrade and the example should work. * Spring WebService 2.0 is not OSGi compliant [due a bug|https://jira.springsource.org/browse/SWS-681] in Spring WS. Thus installing the {{camel-spring-ws}} feature in Apache ServiceMix or Apache Karaf doesnt work.
h2. Important changes to consider when upgrading
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes.
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page edited by Claus Ibsen Changes (3) ... * [Context] * [MyBatis] * [Hazelcast|Hazelcast Component] * [DNS] * [MyBatis] h3. New DSL ... Full Content Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) Dependency changesThe Camel 2.7.0 release has a number of major dependency changes: JDK 1.6+ is now required Spring 3.x+ is now required if using Spring slf4j is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs. Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile. Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured. Spring Integration is upgraded to Spring Integration 2.0. Spring Web Services is upgraded to Spring Web Services 2.0. Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage. The camel-jdbc-aggregator component is merged into the camel-sql component. Fix in Mail component for duplicate attachments. Maven 3 is now supported for building Tidy up the XML DSL to not allow nesting tags where it doesn't make sense. Internal cleanup in route preparation logic to be fully shared for all DSLs (before the XML DSLs and Java DSL was a bit different) Fixed InterceptFrom to work with from endpoints defined using ref's or instances (eg everything but uris) Fixed HTTP and HTTP4 producers double
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* {{threadPoolProfile}} and {{threadPool}} is now easier to use with [property placeholders|Using PropertyPlaceholder] * [Properties] component now supports JVM system properties and OS environment variables in the locations option. For example using {{file:$\{karaf.home\}/etc/foo.properties}} to refer to the {{foo.proeprties}} file in the [Apache Karaf|http://karaf.apache.org/] installation.
* Fixed an issue with [Recipient List] in parallel mode, not reusing background aggregator thread
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage.
The camel-jdbc-aggregator component is merged into the camel-sql component.
Fix in Mail component for duplicate
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* Fixed [JMS] producer not working with OracleAQ throwing exception on accessing {{JMSReplyTo}} * Added support for using [OSGi Blueprint property placeholder|Using PropertyPlaceholder] service with Camel routes. Camel uses convention over configuration so all you have to do is to define the OSGi blueprint placeholder and you can refer to those from the {{camelContext}}. Pay attention to the placeholder tokens using by Camel is {{ }}.
* {{threadPoolProfile}} and {{threadPool}} is now easier to use with [property placeholders|Using PropertyPlaceholder]
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage.
The camel-jdbc-aggregator component is merged into
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* Added support for using [OSGi Blueprint property placeholder|Using PropertyPlaceholder] service with Camel routes. Camel uses convention over configuration so all you have to do is to define the OSGi blueprint placeholder and you can refer to those from the {{camelContext}}. Pay attention to the placeholder tokens using by Camel is {{ }}. * {{threadPoolProfile}} and {{threadPool}} is now easier to use with [property placeholders|Using PropertyPlaceholder]
* [Properties] component now supports JVM system properties and OS environment variables in the locations option. For example using {{file:$\{karaf.home\}/etc/foo.properties}} to refer to the {{foo.proeprties}} file in the [Apache Karaf|http://karaf.apache.org/] installation.
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (3)
...
* Fixed [HTTP] and [HTTP4] producers double encoding endpoint uri, when calling external service * Fixed [JMS] producer not working with OracleAQ throwing exception on accessing {{JMSReplyTo}}
* Added support for using [OSGi Blueprint property placeholder|Using PropertyPlaceholder] service with Camel routes. Camel uses convention over configuration so all you have to do is to define the OSGi blueprint placeholder and you can refer to those from the {{camelContext}}. Pay attention to the placeholder tokens using by Camel is {{ }}.
h3. New [Enterprise Integration Patterns]
...
* None
h3. New [Archetypes|Camel Maven Archetypes]
* {{camel-archetype-light-war}} added to generate a project to deploy camel routes as a WAR
...
* {{sortBody}} methods removed from Java DSL. You can use {{sort(body())}} instead. * The [Sort] EIP in XML DSL is now configured the _expression_ directly. Which means you no longer need to use {{_expression_}} enclosing the _expression_. Instead you set the _expression_ directly, just as the other [EIP]s does.
* Method {{parsePropertyValue}} renamed to {{parseProperty}} and have additional parameters in the {{PropertiesParser}} interface.
h2. Known Issues
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by charles Moulliard
Changes (1)
...
* None
h3. New [Archetypes] * {{camel-archetype-light-war}} added to generate a project to deploy camel routes as a WAR
h2. API breaking
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage.
The camel-jdbc-aggregator component is merged into the camel-sql component.
Fix in Mail component for duplicate attachments.
Maven 3 is now supported for building
Tidy up the XML DSL to not allow nesting tags where it doesn't make sense.
Internal cleanup in route preparation logic to be fully shared for all DSLs (before the XML DSLs and Java DSL was a bit different)
Fixed InterceptFrom to work with from endpoints defined using ref's or instances (eg everything but uris)
Fixed HTTP and HTTP4
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* Fixed [InterceptFrom|Intercept] to work with from endpoints defined using refs or instances (eg everything but uris) * Fixed [HTTP] and [HTTP4] producers double encoding endpoint uri, when calling external service
* Fixed [JMS] producer not working with OracleAQ throwing exception on accessing {{JMSReplyTo}}
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage.
The camel-jdbc-aggregator component is merged into the camel-sql component.
Fix in Mail component for duplicate attachments.
Maven 3 is now supported for building
Tidy up the XML DSL to not allow nesting tags where it doesn't make sense.
Internal cleanup in route preparation logic to be fully
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* The {{batch-config}} and {{stream-config}} tags in XML DSL in the [Resequencer] EIP must now be configured in the top, and not in the bottom. So if you use those, then move them up just below the {{resequence}} [EIP] starts in the XML. * The {{JdbcAggregationRepository}} is moved from the {{camel-jdbc-aggregator}} component to the {{camel-sql}} component. The full qualified class name changed from {{org.apache.camel.component.jdbc.aggregationRepository.JdbcAggregationRepository}} to {{org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository}}.
* {{sortBody}} methods removed from Java DSL. You can use {{sort(body())}} instead. * The [Sort] EIP in XML DSL is now configured the _expression_ directly. Which means you no longer need to use {{_expression_}} enclosing the _expression_. Instead you set the _expression_ directly, just as the other [EIP]s does.
h2. Known Issues
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* If you have developed custom Camel [Component]s and your {{Endpoint}} class extends {{DefaultEndpoint}} then its advised to use the {{doStart}} and {{doStop}} instead of {{start}} and {{stop}}. * camel-cxf endpoint will copy the attachments between the camel message and cxf message when it works in POJO data format, please access the attachment objects from the camel message body.
* [camel-restlet|Restlet] has been upgraded from Restlet 1.1.x to 2.0.5
h2. Getting the Distributions
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage.
The camel-jdbc-aggregator component is merged into the camel-sql component.
Maven 3 is now supported for building
New Enterprise Integration Patterns
None
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* The {{camel-jdbc-aggregator}} component is merged into the {{camel-sql}} component. * Maven 3 is now supported for building
* Tidy up the XML DSL to not allow nesting tags where it doesnt make sense.
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage.
The camel-jdbc-aggregator component is merged into the camel-sql component.
Maven 3 is now supported for building
Tidy up the XML DSL to not allow nesting tags where it doesn't make sense.
New Enterprise Integration Patterns
None
New Components
Context
MyBatis
New DSL
setFaultBody added to XML DSL
endChoice added to Java DSL
placeholder added to Java DSL
New Annotations
None
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page edited by Hadrian Zbarcea Changes (1) ... * Maven 3 is now supported for building * Tidy up the XML DSL to not allow nesting tags where it doesnt make sense. * Fix in [Mail] component for duplicate attachments. h3. New [Enterprise Integration Patterns] ... Full Content Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) Dependency changesThe Camel 2.7.0 release has a number of major dependency changes: JDK 1.6+ is now required Spring 3.x+ is now required if using Spring slf4j is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs. Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile. Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured. Spring Integration is upgraded to Spring Integration 2.0. Spring Web Services is upgraded to Spring Web Services 2.0. Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage. The camel-jdbc-aggregator component is merged into the camel-sql component. Maven 3 is now supported for building Tidy up the XML DSL to not allow nesting tags where it doesn't make sense. Fix in Mail component for duplicate attachments. New Enterprise Integration Patterns None New Components Context MyBatis New DSL setFaultBody added to XML DSL endChoice added to Java DSL placeholder added to Java DSL New
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (5)
...
* [Quartz] update checker is now always disabled, see more [details here|http://forums.terracotta.org/forums/posts/list/3395.page#19058] * Fixed potential issue installing {{camel-ftp}} feature in Apache ServiceMix
* New {{JdbcMessageIdRepository}} for the idempotent consumer EIP in [SQL|SQL Component]
* Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting [CamelContext] or starting new routes. This avoids registering too many MBeans if using dynamic [EIP] patterns such as [Recipient List] using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the {{registerAlways}} or {{registerNewRoutes}} options on {{ManagementAgent}} to control this behavior. See [Camel JMX] for more details. * Redelivery policy and OnException now supports [property placeholders|Using PropertyPlaceholder] in both Java and XML DSLs.
...
* [Property placeholders|Using PropertyPlaceholder] can now be use for any kind of attributes/options in the [EIP]s in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the [Using PropertyPlaceholder] wiki page. In the Java DSL there is a new {{placeholder}} option on each [EIP] you can leverage. * The {{camel-jdbc-aggregator}} component is merged into the {{camel-sql}} component.
* Fix in [Mail] component for duplicate attachments.
* Maven 3 is now supported for building * Tidy up the XML DSL to not allow nesting tags where it doesnt make sense.
* Fix in [Mail] component for duplicate attachments.
* Internal cleanup in route preparation logic to be fully shared for all DSLs (before the XML DSLs and Java DSL was a bit different)
h3. New [Enterprise Integration Patterns]
...
* [Context] * [MyBatis]
* [DNS]
h3. New DSL
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page edited by Claus Ibsen Changes (1) ... * Tidy up the XML DSL to not allow nesting tags where it doesnt make sense. * Internal cleanup in route preparation logic to be fully shared for all DSLs (before the XML DSLs and Java DSL was a bit different) * Fixed [InterceptFrom|Intercept] to work with from endpoints defined using refs or instances (eg everything but uris) h3. New [Enterprise Integration Patterns] ... Full Content Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) Dependency changesThe Camel 2.7.0 release has a number of major dependency changes: JDK 1.6+ is now required Spring 3.x+ is now required if using Spring slf4j is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs. Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile. Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured. Spring Integration is upgraded to Spring Integration 2.0. Spring Web Services is upgraded to Spring Web Services 2.0. Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder wiki page. In the Java DSL there is a new placeholder option on each EIP you can leverage. The camel-jdbc-aggregator component is merged into the camel-sql component. Fix in Mail component for duplicate attachments. Maven 3 is now supported for building Tidy up the XML DSL to not allow nesting tags where it doesn't make sense. Internal cleanup in route preparation
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* [Spring Web Services] is upgraded to Spring Web Services 2.0. * Added {{endChoice()}} to the Java DSL to be able to use any [EIP]s inside the [Content Based Router]. See more [details here|Why can I not use when or otherwise in a Java Camel route]
* [Property placeholders|Using PropertyPlaceholder] can now be use for any kind of attributes/options in the [EIP]s in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the [Using PropertyPlaceholder] wiki page. In the Java DSL there is a new {{placeholder}} option on each [EIP] you can leverage.
h3. New [Enterprise Integration Patterns]
...
* {{setFaultBody}} added to XML DSL * {{endChoice}} added to Java DSL
* {{placeholder}} added to Java DSL
h3. New Annotations
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Christian Mueller
Changes (1)
...
* The {{ref}} attribute on {{redeliveryPolicy}} has been removed. Instead use {{redeliveryPolicyRef}} attribute on {{onException}} or {{errorHandler}} tags. * The {{batch-config}} and {{stream-config}} tags in XML DSL in the [Resequencer] EIP must now be configured in the top, and not in the bottom. So if you use those, then move them up just below the {{resequence}} [EIP] starts in the XML.
* The {{JdbcAggregationRepository}} is moved from the {{camel-jdbc-aggregator}} component to the {{camel-sql}} component. The full qualified class name changed from {{org.apache.camel.component.jdbc.aggregationRepository.JdbcAggregationRepository}} to {{org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository}}.
h2. Known Issues
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
Property placeholders can now be use for any kind of attributes/options in the EIPs in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the Using PropertyPlaceholder
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* [Property placeholders|Using PropertyPlaceholder] can now be use for any kind of attributes/options in the [EIP]s in the Camel routes. For example in the Spring XML file you can now use placeholders for timeout attributes etc. This is possible using the specialized placeholder namespace. See more details at the [Using PropertyPlaceholder] wiki page. In the Java DSL there is a new {{placeholder}} option on each [EIP] you can leverage. * The {{camel-jdbc-aggregator}} component is merged into the {{camel-sql}} component.
* Maven 3 is now supported for building
h3. New [Enterprise Integration Patterns]
...
* The [Tracer] may not output all details for some situations such as when using {{onCompletion}} or {{intercept}} etc. * Not all [Examples] have ANT build.xml files to run the example using ANT.
* Project cannot be fully build using Maven 3.0
* {{camel-script}} which uses {{ScriptEngineManager}} from the JDK, cannot load script engines from packages outside the JDK. * Stopping a route after using {{adviceWith}} maybe cause issues with error handlers, see [CAMEL-3534|https://issues.apache.org/jira/browse/CAMEL-3534]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* [Spring Integration|SpringIntegration] is upgraded to Spring Integration 2.0. * [Spring Web Services] is upgraded to Spring Web Services 2.0.
* Added {{endChoice()}} to the Java DSL to be able to use any [EIP]s inside the [Content Based Router]. See more [details here|Why can I not use when or otherwise in a Java Camel route]
h3. New [Enterprise Integration Patterns]
...
* {{setFaultBody}} added to XML DSL
* {{endChoice}} added to Java DSL
h3. New Annotations
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
Added endChoice() to the Java DSL to be able to use any EIPs inside the Content Based Router. See more details here
New Enterprise Integration Patterns
None
New Components
Context
MyBatis
New DSL
setFaultBody added to XML DSL
endChoice added to Java DSL
New Annotations
None
New Data Formats
None
New Languages
Spring _expression_ Language
New Examples
camel-example-osgi-rmi
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (3)
...
* [Context]
* [MyBatis]
h3. New DSL
* None
* {{setFaultBody}} added to XML DSL
h3. New Annotations
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Improved the XML based Error Handlers to validate configuration on startup, to fail if they have been misconfigured.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
New Enterprise Integration Patterns
None
New Components
Context
MyBatis
New DSL
setFaultBody added to XML DSL
New Annotations
None
New Data Formats
None
New Languages
Spring _expression_ Language
New Examples
camel-example-osgi-rmi
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Removed getLeftValue and getRightValue methods on BinaryPredicate.
The ref attribute on redeliveryPolicy has been removed. Instead use redeliveryPolicyRef attribute on onException or errorHandler tags.
Known Issues
The Tracer may not output all details for some situations such as when using onCompletion or intercept etc.
Not all Examples have ANT build.xml files to run the example using ANT.
Project cannot be fully build using Maven 3.0
camel-script which uses ScriptEngineManager from
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting [CamelContext] or starting new routes. This avoids registering too many MBeans if using dynamic [EIP] patterns such as [Recipient List] using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the {{registerAlways}} or {{registerNewRoutes}} options on {{ManagementAgent}} to control this behavior. See [Camel JMX] for more details. * Redelivery policy and OnException now supports [property placeholders|Using PropertyPlaceholder] in both Java and XML DSLs.
* Introduced {{redeliveryPolicyProfile}} to easily define common profiles for redelivery policies, which you can refer to from {{errorHandler}} or {{onException}} using the {{redeliveryPolicyRef}} attribute. Also Spring Frameworks property placeholders works with {{redeliveryPolicyProfile}}.
* [Spring Integration|SpringIntegration] is upgraded to Spring Integration 2.0. * [Spring Web Services] is upgraded to Spring Web Services 2.0.
...
* {{org.apache.camel.processor.Logger}} has been renamed to {{org.apache.camel.processor.CamelLogger}}, and it now uses [slf4j|http://www.slf4j.org/] as the logger. * Removed {{getLeftValue}} and {{getRightValue}} methods on {{BinaryPredicate}}.
* The {{ref}} attribute on {{redeliveryPolicy}} has been removed. Instead use {{redeliveryPolicyRef}} attribute on {{onException}} or {{errorHandler}} tags.
h2. Known Issues
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting [CamelContext] or starting new routes. This avoids registering too many MBeans if using dynamic [EIP] patterns such as [Recipient List] using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the {{registerAlways}} or {{registerNewRoutes}} options on {{ManagementAgent}} to control this behavior. See [Camel JMX] for more details. * Redelivery policy and OnException now supports [property placeholders|Using PropertyPlaceholder] in both Java and XML DSLs.
* Introduced [{{redeliveryPolicyProfile}}|RedeliveryPolicy] to easily define common profiles for [redelivery policies|RedeliveryPolicy], which you can refer to from {{errorHandler}} or {{onException}} using the {{redeliveryPolicyRef}} attribute. Also Spring Frameworks property placeholders works with {{redeliveryPolicyProfile}}.
* [Spring Integration|SpringIntegration] is upgraded to Spring Integration 2.0. * [Spring Web Services] is upgraded to Spring Web Services 2.0.
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Introduced redeliveryPolicyProfile to easily define common profiles for redelivery policies, which you can refer to from errorHandler or onException using the redeliveryPolicyRef attribute. Also Spring Frameworks property placeholders works with redeliveryPolicyProfile.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
New Enterprise Integration Patterns
None
New Components
Context
New DSL
None
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
* New JdbcMessageIdRepository for the idempotent consumer EIP in [SQL|SQL Component] * Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting [CamelContext] or starting new routes. This avoids registering too many MBeans if using dynamic [EIP] patterns such as [Recipient List] using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the {{registerAlways}} or {{registerNewRoutes}} options on {{ManagementAgent}} to control this behavior. See [Camel JMX] for more details.
* Redelivery policy and OnException now supports [property placeholders|Using PropertyPlaceholder] in both Java and XML DSLs.
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
New Enterprise Integration Patterns
None
New Components
Context
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
Spring _expression_ Language
New Examples
camel-example-osgi-rmi
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Removed getLeftValue and getRightValue methods on BinaryPredicate.
Known Issues
The Tracer may not output all details for some situations such as when using onCompletion or intercept etc.
Not all Examples have ANT build.xml files to run the example using ANT.
Project cannot be fully build using Maven 3.0
camel-script which uses
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Richard Kettelerij
Changes (1)
...
* Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting [CamelContext] or starting new routes. This avoids registering too many MBeans if using dynamic [EIP] patterns such as [Recipient List] using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the {{registerAlways}} or {{registerNewRoutes}} options on {{ManagementAgent}} to control this behavior. See [Camel JMX] for more details. * Redelivery policy and OnException now supports [property placeholders|Using PropertyPlaceholder] in both Java and XML DSLs.
* [Spring Integration|SpringIntegration] is upgraded to Spring Integration 2.0. * [Spring Web Services] is upgraded to Spring Web Services 2.0.
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details.
Redelivery policy and OnException now supports property placeholders in both Java and XML DSLs.
Spring Integration is upgraded to Spring Integration 2.0.
Spring Web Services is upgraded to Spring Web Services 2.0.
New Enterprise Integration Patterns
None
New Components
Context
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
Spring _expression_ Language
New Examples
camel-example-osgi-rmi
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Removed getLeftValue and getRightValue methods on BinaryPredicate.
Known Issues
The Tracer may not output all details for some situations such as
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page edited by Claus Ibsen Changes (3) ... h3. New [Components] * None [Context] h3. New DSL ... h3. New [Languages] * None * [Spring _expression_ Language|SpEL] h3. New [Examples] ... Full Content Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) Dependency changesThe Camel 2.7.0 release has a number of major dependency changes: JDK 1.6+ is now required Spring 3.x+ is now required if using Spring slf4j is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. Switched to use slf4j as the logger instead of commons logging. Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state. Added support for MDC logging with Camel JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown. Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation. Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint. Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation. HTTP4 is upgraded to use Apache HttpClient 4.1 Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well Fixed concurrent append to the same file in the File producer Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs. Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader. Quartz update checker is now always disabled, see more details here Fixed potential issue installing camel-ftp feature in Apache ServiceMix New JdbcMessageIdRepository for the idempotent consumer EIP in SQL Relaxed how aggressive Camel was registering services as MBeans in JMX. Now Camel will by default only registeres MBeans when starting CamelContext or starting new routes. This avoids registering too many MBeans if using dynamic EIP patterns such as Recipient List using different endpoint urls, causing new endpoints and its associated services to be registered in JMX. This would keep growing over time and consume memory as well. You can use the registerAlways or registerNewRoutes options on ManagementAgent to control this behavior. See Camel JMX for more details. New Enterprise Integration Patterns None New Components Context New DSL None New Annotations None New Data Formats None New Languages Spring _expression_ Language New Examples camel-example-osgi-rmi New Tutorials None API breaking FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead. org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger. Removed getLeftValue and getRightValue methods on BinaryPredicate. Known Issues The Tracer may not output all details for some situations such as when using onCompletion or intercept etc. Not all Examples have ANT build.xml files to run the example using ANT. Project cannot be fully build using Maven 3.0 camel-script which uses ScriptEngineManager from the JDK, cannot load script engines from packages outside the JDK. Stopping a route after using adviceWith maybe cause issues with error handlers, see CAMEL-3534 Important changes to consider when upgrading Java 1.6 or better is required Spring 3.0.x or better is required, when using Spring Apache CXF 2.3.2 or better is required, when using CXF Switched to use slf4j as the logger instead of commons logging. That means you may have to included slf4j-log4j12 as dependency if you are using log4j. See documentation at slf4j for more details. If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* [HTTP4] is upgraded to use Apache HttpClient 4.1 * Fixed an issue with [File|File2] consumer having absolute starting directory and using absolute paths in the {{move}} option as well
* Fixed concurrent append to the same file in the [File|File2] producer
* Fixed issue with restarting [Quartz] causing a failure due trigger name already exists issue for stateful jobs. * Its now possible to use multiple QuartzSchedulers when deploying multiple Camel applications in the same JVM classloader. * [Quartz] update checker is now always disabled, see more [details here|http://forums.terracotta.org/forums/posts/list/3395.page#19058]
* Fixed potential issue installing {{camel-ftp}} feature in Apache ServiceMix
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New Enterprise Integration Patterns
None
New Components
None
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
None
New Examples
None
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Known Issues
The Tracer may not output all details for some situations such as when using onCompletion or intercept etc.
Not all Examples have ANT build.xml files to run the example using ANT.
Project cannot be fully build using Maven 3.0
camel-script which uses ScriptEngineManager from the JDK, cannot load script engines from packages outside the JDK.
Stopping a route after using adviceWith maybe cause issues with error handlers, see CAMEL-3534
Important changes to consider when upgrading
Java 1.6 or better is required
Spring 3.0.x or better is required, when using Spring
Apache CXF 2.3.2 or better is required, when using CXF
Switched to use slf4j as the logger instead of commons logging. That means you may have to included slf4j-log4j12 as dependency if you are using log4j.
See documentation at slf4j for more details.
If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start and stop.
Getting the Distributions
Binary Distributions
Description
Download Link
PGP Signature file of download
Windows Distribution
apache-camel-2.7.0.zip
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by willem jiang
Changes (1)
...
See documentation at [slf4j|http://www.slf4j.org/] for more details. * If you have developed custom Camel [Component]s and your {{Endpoint}} class extends {{DefaultEndpoint}} then its advised to use the {{doStart}} and {{doStop}} instead of {{start}} and {{stop}}.
* camel-cxf endpoint will copy the attachments between the camel message and cxf message when it works in POJO data format, please access the attachment objects from the camel message body.
h2. Getting the Distributions
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New Enterprise Integration Patterns
None
New Components
None
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
None
New Examples
None
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Known Issues
The Tracer may not output all details for some situations such as when using onCompletion or intercept etc.
Not all Examples have ANT build.xml files to run the example using ANT.
Project cannot be fully build using Maven 3.0
camel-script which uses ScriptEngineManager from the JDK, cannot load script engines from packages outside the JDK.
Stopping a route after using adviceWith maybe cause issues with error handlers, see CAMEL-3534
Important changes to consider when upgrading
Java 1.6 or better is required
Spring 3.0.x or better is required, when using Spring
Apache CXF 2.3.2 or better is required, when using CXF
Switched to use slf4j as the logger instead of commons logging. That means you may have to included slf4j-log4j12 as dependency if you are using log4j.
See documentation at slf4j for more details.
If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start and stop.
camel-cxf endpoint will copy the attachments between the camel message and cxf message when it works in POJO data format, please access the attachment objects from the camel message body.
Getting the Distributions
Binary Distributions
Description
Download Link
PGP Signature file of download
Windows Distribution
apache-camel-2.7.0.zip
apache-camel-2.7.0.zip.asc
Unix/Linux/Cygwin Distribution
apache-camel-2.7.0.tar.gz
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (1)
...
h3. New [Examples]
* None {{camel-example-osgi-rmi}}
h3. New [Tutorials]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New Enterprise Integration Patterns
None
New Components
None
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
None
New Examples
camel-example-osgi-rmi
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Known Issues
The Tracer may not output all details for some situations such as when using onCompletion or intercept etc.
Not all Examples have ANT build.xml files to run the example using ANT.
Project cannot be fully build using Maven 3.0
camel-script which uses ScriptEngineManager from the JDK, cannot load script engines from packages outside the JDK.
Stopping a route after using adviceWith maybe cause issues with error handlers, see CAMEL-3534
Important changes to consider when upgrading
Java 1.6 or better is required
Spring 3.0.x or better is required, when using Spring
Apache CXF 2.3.2 or better is required, when using CXF
Switched to use slf4j as the logger instead of commons logging. That means you may have to included slf4j-log4j12 as dependency if you are using log4j.
See documentation at slf4j for more details.
If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start and stop.
camel-cxf endpoint will copy the attachments between the camel message and cxf message when it works in POJO data format, please access the attachment objects from the camel message body.
Getting the Distributions
Binary Distributions
Description
Download Link
PGP Signature file of download
Windows Distribution
apache-camel-2.7.0.zip
apache-camel-2.7.0.zip.asc
Unix/Linux/Cygwin Distribution
apache-camel-2.7.0.tar.gz
apache-camel-2.7.0.tar.gz.asc
The above URLs use redirectionThe above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox
Source Distributions
Description
Download Link
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Christian Mueller
Changes (1)
...
* [Quartz] update checker is now always disabled, see more [details here|http://forums.terracotta.org/forums/posts/list/3395.page#19058] * Fixed potential issue installing {{camel-ftp}} feature in Apache ServiceMix
* New JdbcMessageIdRepository for the idempotent consumer EIP in [Sql]
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
Fixed concurrent append to the same file in the File producer
Fixed issue with restarting Quartz causing a failure due trigger name already exists issue for stateful jobs.
Its now possible to use multiple QuartzScheduler's when deploying multiple Camel applications in the same JVM classloader.
Quartz update checker is now always disabled, see more details here
Fixed potential issue installing camel-ftp feature in Apache ServiceMix
New JdbcMessageIdRepository for the idempotent consumer EIP in SQL
New Enterprise Integration Patterns
None
New Components
None
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
None
New Examples
camel-example-osgi-rmi
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Known Issues
The Tracer may not output all details for some situations such as when using onCompletion or intercept etc.
Not all Examples have ANT build.xml files to run the example using ANT.
Project cannot be fully build using Maven 3.0
camel-script which uses ScriptEngineManager from the JDK, cannot load script engines from packages outside the JDK.
Stopping a route after using adviceWith maybe cause issues with error handlers, see CAMEL-3534
Important changes to consider when upgrading
Java 1.6 or better is required
Spring 3.0.x or better is required, when using Spring
Apache CXF 2.3.2 or better is required, when using CXF
Switched to use slf4j as the logger instead of commons logging. That means you may have to included slf4j-log4j12 as dependency if you are using log4j.
See documentation at slf4j for more details.
If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start and stop.
camel-cxf endpoint will copy the attachments between the camel message and cxf message when it works in POJO data format, please access the attachment objects from the camel message body.
Getting the Distributions
Binary Distributions
Description
Download Link
PGP Signature file of download
Windows Distribution
apache-camel-2.7.0.zip
apache-camel-2.7.0.zip.asc
Unix/Linux/Cygwin Distribution
apache-camel-2.7.0.tar.gz
apache-camel-2.7.0.tar.gz.asc
The above URLs use redirectionThe above
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
* Switched to use [slf4j|http://www.slf4j.org/] as the logger instead of commons logging. * Camel now checks state of {{Service}} during starting/stopping the [Lifecycle] of the {{Service}}. This avoids double starting/stopping in case the service was already in the desired state.
* Added support for [MDC logging] with Camel
* [JMS] consumer now eager checks if Camel is shutting down and signals that to its {{DefaultMessageListenerContainer}} which avoids trying to re-connect/failover during shutdown. * Introduced option to automatic [Mock] endpoints during testing. This makes testing without having to add [Mock] endpoints in your routes a breeze. See more details at [Mock] component documentation.
...
* Added {{arrives}} DSL to [Mock] endpoint to allow you to setup expectations about timespan between messages arriving on the [Mock] endpoint. See more details at [Mock] component documentation. * [HTTP4] is upgraded to use Apache HttpClient 4.1
* Fixed an issue with [File|File2] consumer having absolute starting directory and using absolute paths in the {{move}} option as well
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
Added support for MDC logging with Camel
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
Fixed an issue with File consumer having absolute starting directory and using absolute paths in the move option as well
New Enterprise Integration Patterns
None
New Components
None
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
None
New Examples
None
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Known Issues
None
Important changes to consider when upgrading
Switched to use slf4j as the logger instead of commons logging. That means you may have to included slf4j-log4j12 as dependency if you are using log4j.
See documentation at slf4j for more details.
If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start and stop.
Getting the Distributions
Binary Distributions
Description
Download Link
PGP Signature file of download
Windows Distribution
apache-camel-2.7.0.zip
apache-camel-2.7.0.zip.asc
Unix/Linux/Cygwin Distribution
apache-camel-2.7.0.tar.gz
apache-camel-2.7.0.tar.gz.asc
The above URLs use redirectionThe above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox
Source Distributions
Description
Download Link
PGP Signature file of download
Source for Windows
apache-camel-2.7.0-src.zip
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (4)
...
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
{info:title=Dependency changes} The Camel 2.7.0 release has a number of major dependency changes: - JDK 1.6+ is now required - Spring 3.x+ is now required if using Spring - [slf4j|http://www.slf4j.org/] is used as logger instead of commons logging In other words support for JDK 1.5 and Spring 2.x has been dropped. {info} * Switched to use [slf4j|http://www.slf4j.org/] as the logger instead of commons logging.
* Camel now checks state of {{Service}} during starting/stopping the [Lifecycle] of the {{Service}}. This avoids double starting/stopping in case the service was already in the desired state. * [JMS] consumer now eager checks if Camel is shutting down and signals that to its {{DefaultMessageListenerContainer}} which avoids trying to re-connect/failover during shutdown.
...
h2. API breaking
* None
* {{FATAL}} has been removed from {{org.apache.camel.LoggingLevel}}. Use {{ERROR}} instead. * {{org.apache.camel.processor.Logger}} has been renamed to {{org.apache.camel.processor.CamelLogger}}, and it now uses [slf4j|http://www.slf4j.org/] as the logger.
h2. Known Issues
...
h2. Important changes to consider when upgrading
* Switched to use [slf4j|http://www.slf4j.org/] as the logger instead of commons logging. That means you may have to included {{slf4j-log4j12}} as dependency if you are using log4j. See documentation at [slf4j|http://www.slf4j.org/] for more details.
* If you have developed custom Camel [Component]s and your {{Endpoint}} class extends {{DefaultEndpoint}} then its advised to use the {{doStart}} and {{doStop}} instead of {{start}} and {{stop}}.
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Dependency changesThe Camel 2.7.0 release has a number of major dependency changes:
JDK 1.6+ is now required
Spring 3.x+ is now required if using Spring
slf4j is used as logger instead of commons logging
In other words support for JDK 1.5 and Spring 2.x has been dropped.
Switched to use slf4j as the logger instead of commons logging.
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
New Enterprise Integration Patterns
None
New Components
None
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
None
New Examples
None
New Tutorials
None
API breaking
FATAL has been removed from org.apache.camel.LoggingLevel. Use ERROR instead.
org.apache.camel.processor.Logger has been renamed to org.apache.camel.processor.CamelLogger, and it now uses slf4j as the logger.
Known Issues
None
Important changes to consider when upgrading
Switched to use slf4j as the logger instead of commons logging. That means you may have to included slf4j-log4j12 as dependency if you are using log4j.
See documentation at slf4j for more details.
If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start and stop.
Getting the Distributions
Binary Distributions
Description
Download Link
PGP Signature file of download
Windows Distribution
apache-camel-2.7.0.zip
apache-camel-2.7.0.zip.asc
Unix/Linux/Cygwin Distribution
apache-camel-2.7.0.tar.gz
apache-camel-2.7.0.tar.gz.asc
The
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Christian Mueller
Changes (1)
...
* Added {{assertPeriod}} option to [Mock] endpoint, which is a period im milliseconds, that the [Mock] will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that *exactly* a given number of messages should arrive on the [Mock] endpoint. * Added {{arrives}} DSL to [Mock] endpoint to allow you to setup expectations about timespan between messages arriving on the [Mock] endpoint. See more details at [Mock] component documentation.
* [HTTP4] is upgraded to use Apache HttpClient 4.1
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
HTTP4 is upgraded to use Apache HttpClient 4.1
New Enterprise Integration Patterns
None
New Components
None
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
None
New Examples
None
New Tutorials
None
API breaking
None
Known Issues
None
Important changes to consider when upgrading
If you have developed custom Camel Components and your Endpoint class extends DefaultEndpoint then its advised to use the doStart and doStop instead of start and stop.
Getting the Distributions
Binary Distributions
Description
Download Link
PGP Signature file of download
Windows Distribution
apache-camel-2.7.0.zip
apache-camel-2.7.0.zip.asc
Unix/Linux/Cygwin Distribution
apache-camel-2.7.0.tar.gz
apache-camel-2.7.0.tar.gz.asc
The above URLs use redirectionThe above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox
Source Distributions
Description
Download Link
PGP Signature file of download
Source for Windows
apache-camel-2.7.0-src.zip
apache-camel-2.7.0-src.zip.asc
Source for Unix/Linux/Cygwin
apache-camel-2.7.0-src.tar.gz
apache-camel-2.7.0-src.tar.gz.asc
Getting the Binaries using Maven 2
To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is:
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
version2.7.0/version
/dependency
SVN Tag Checkout
svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.7.0
Changelog
For a more detailed view of new features and bug fixes, see the:
release notes for 2.7.0
Change Notification Preferences
View Online
|
View Changes
|
Add Comment
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release Page added by Claus Ibsen Camel 2.7.0 release (currently in progress) New and Noteworthy Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...) TODO: add here New Enterprise Integration Patterns None New Components None New DSL None New Annotations None New Data Formats None New Languages None New Examples None New Tutorials None API breaking None Known Issues None Important changes to consider when upgrading None Getting the Distributions Binary Distributions Description Download Link PGP Signature file of download Windows Distribution apache-camel-2.7.0.zip apache-camel-2.7.0.zip.asc Unix/Linux/Cygwin Distribution apache-camel-2.7.0.tar.gz apache-camel-2.7.0.tar.gz.asc The above URLs use redirectionThe above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox Source Distributions Description Download Link PGP Signature file of download Source for Windows apache-camel-2.7.0-src.zip apache-camel-2.7.0-src.zip.asc Source for Unix/Linux/Cygwin apache-camel-2.7.0-src.tar.gz apache-camel-2.7.0-src.tar.gz.asc Getting the Binaries using Maven 2 To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is: dependency groupIdorg.apache.camel/groupId artifactIdcamel-core/artifactId version2.7.0/version /dependency SVN Tag Checkout svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.7.0 Changelog For a more detailed view of new features and bug fixes, see the: release notes for 2.7.0 Change Notification Preferences View Online | Add Comment
[CONF] Apache Camel Camel 2.7.0 Release
Camel 2.7.0 Release
Page edited by Claus Ibsen
Changes (2)
...
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
* TODO: add here
* Camel now checks state of {{Service}} during starting/stopping the [Lifecycle] of the {{Service}}. This avoids double starting/stopping in case the service was already in the desired state. * [JMS] consumer now eager checks if Camel is shutting down and signals that to its {{DefaultMessageListenerContainer}} which avoids trying to re-connect/failover during shutdown. * Introduced option to automatic [Mock] endpoints during testing. This makes testing without having to add [Mock] endpoints in your routes a breeze. See more details at [Mock] component documentation. * Added {{assertPeriod}} option to [Mock] endpoint, which is a period im milliseconds, that the [Mock] will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that *exactly* a given number of messages should arrive on the [Mock] endpoint. * Added {{arrives}} DSL to [Mock] endpoint to allow you to setup expectations about timespan between messages arriving on the [Mock] endpoint. See more details at [Mock] component documentation.
h3. New [Enterprise Integration Patterns]
...
Full Content
Camel 2.7.0 release (currently in progress)
New and Noteworthy
Welcome to the 2.7.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
Camel now checks state of Service during starting/stopping the Lifecycle of the Service. This avoids double starting/stopping in case the service was already in the desired state.
JMS consumer now eager checks if Camel is shutting down and signals that to its DefaultMessageListenerContainer which avoids trying to re-connect/failover during shutdown.
Introduced option to automatic Mock endpoints during testing. This makes testing without having to add Mock endpoints in your routes a breeze. See more details at Mock component documentation.
Added assertPeriod option to Mock endpoint, which is a period im milliseconds, that the Mock will pause and then re-assert itself to ensure the assertion is still valid. This can be used as a threshold when testing with expectations that exactly a given number of messages should arrive on the Mock endpoint.
Added arrives DSL to Mock endpoint to allow you to setup expectations about timespan between messages arriving on the Mock endpoint. See more details at Mock component documentation.
New Enterprise Integration Patterns
None
New Components
None
New DSL
None
New Annotations
None
New Data Formats
None
New Languages
None
New Examples
None
New Tutorials
None
API breaking
None
Known Issues
None
Important changes to consider when upgrading
None
Getting the Distributions
Binary Distributions
Description
Download Link
PGP Signature file of download
Windows Distribution
apache-camel-2.7.0.zip
apache-camel-2.7.0.zip.asc
Unix/Linux/Cygwin Distribution
apache-camel-2.7.0.tar.gz
apache-camel-2.7.0.tar.gz.asc
The above URLs use redirectionThe above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox
Source Distributions
Description
Download Link
PGP Signature file of download
Source for Windows
apache-camel-2.7.0-src.zip
apache-camel-2.7.0-src.zip.asc
Source for Unix/Linux/Cygwin
apache-camel-2.7.0-src.tar.gz
apache-camel-2.7.0-src.tar.gz.asc
Getting the Binaries using Maven 2
To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is:
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
version2.7.0/version
/dependency
SVN Tag Checkout
svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.7.0
Changelog
For a more detailed view of new features and bug fixes, see the:
release notes for 2.7.0
Change Notification Preferences
View Online
|
View Changes
|
Add Comment
