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

...

• 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 with from endpoints defined using ref's 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
• Added support for using OSGi Blueprint property placeholder 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
• 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 installation.
• Fixed an issue with Recipient List in parallel mode, not reusing background aggregator thread
• Fixed an issue with dependency ordering when using Spring's depends-on attribute between multiple <camelContext>.
• Servlet SERVLET component doesn't 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 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.
• 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.

...

• Java 1.6 or better is required
• Spring 3.0.5 or better is required, when using Spring
• Apache CXF 2.3.3 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.
• 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 has been upgraded from Restlet 1.1.x to 2.0.5
• Servlet 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.

...

...

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>
  <groupId>org.apache.camel</groupId>
  <artifactId>camel-core</artifactId>
  <version>2.7.0</version>
</dependency>

SVN Tag Checkout

svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.7.0

...