...
Camel
...
1.5.0
...
release
Div | ||||||
---|---|---|---|---|---|---|
| =
| }
!http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png!
{div}
{div:style=|||||
Div | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New and NoteworthyWelcome to the } h2. New and Noteworthy Welcome to the1.5.0 release which approx 266 issues resolved (new features, improvements and bug fixes such as...) *
New Enterprise Integration PatternsNew Components
New DSLNew Annotations
New Data FormatsNew Languages
New ExamplesAPI breakings
Known Issues
Important changes to consider when upgradingProducerTemplateThe ProducerTemplate has refined its sendBody and requestBody methods to throw The old behavior in Camel 1.4 or older was just plain wrong! JMXOption usePlatformMBeanServer has changed its default value from false to true. TypeConverterAn implementation of TypeConverter should now throw a NoTypeConversionAvailableException if conversion is not possible. The semantical ambiguity of null (both valid result and indication of no conversion) is now resolved, but this may impact existing code in that it should now catch the exception instead of checking for null. setHeader element in Spring DSL changedYou can no longer use a 'value' attribute like this to set a header to a constant:
Now, you can use a []expression to do the same thing: {
Notice that this constant expression is also possible in the Java DSL: {code:java}
redeliveryPolicy specification in Spring DSL changedInstead of
You now set redelivery policy settings with attributes {
Data format specification in Spring DSL changedThe way you specify data formats in the Spring DSL has changed. You could do this in Camel 1.4:
Now, you specify the same as: {
CXF ProducerThe result of CXF producer has changed to use MessageContentsList instead of Object array to hold the response. CXFMessage will check the list members and chose the most right answer for you. CXF Producer before Camel 1.5 {
CXF Produer in Camel 1.5 {
Now the CXF Producer(in Camel 1.5) will throw the exception after the CXF client gets the exception, in this way you can leverage the Camel [|Error Handler]for handling the exception.
you don't want camel redeliver the message when your producer got the common SOAP fault, specially you are using CXF producer and CXF consumer as a proxy, you'd better override the Camel default [|Error Handler]. You can do it with DSL {code:language=java}. You can do it with DSL
Or Spring {
FTP componentThe option has changed the default value from *true *to *false *. Now throws {{
with the FTP error code and reason. For instance error code 530 is not authorized. This applies for both consumer and producer. The consumer will now also regard failing move or rename operations as a severe error throw a {{
instead of {{
logging. As a consumer you will *not *receive an Exchange, as opposed to the situation in Camel 1.4.0. Bottom line: all the FTP operations should succeed before the consumer will process the Exchange. h3.FileConsumerThe option {{
has changed the default value from *true *to *false *. h3.HttpProducerNow the http producer will throw a {{
if the response code is not 1xx or 2xx. You can get the status code, status line and location for the exception.
the Camel < 1.5.0 , http producer does not check the response code and puts the response message into the out message. Http producer has better algorithm to compute if either GET or POST should be used. h3.camel-minaIn Camel 1.5 the sync option has changed its default value from *false *to *true *, as we felt it was confusing for end-users when they used Mina to call remote servers and Camel wouldn't wait for the response. To remedy this you had to add the sync=true option before it worked, we want this to work out-of-the-box without having to specify this option. h3.camel-mailIn Camel 1.5 the following default options has changed in camel-mail: - {{deleteProcessedMessages}} is now *false* as we felt Camel should not delete mails on the mail server by default. - {{processOnlyUnseenMessages}} is now *true* as we felt Camel should only poll new mails by default. h3. removeOutHeader DSL method removed Since any exchange coming into the removeOutHeader processor would have an IN message only, this method was useless and so was removed. h3. [Aggregator] and {{AggregationCollection}} The AggregationCollection used by [Aggregator] is changed to an interface instead of a class. This allows end-users to provide their own collections that isn't a subclass of the default. The old AggregationCollection class is renamed to DefaultAggregationCollection. Aggregator must be configured directly on the consumer: - This is valid: {{
removeOutHeader DSL method removedSince any exchange coming into the removeOutHeader processor would have an IN message only, this method was useless and so was removed. Aggregator and |
Getting the Distributions
Binary Distributions
Description | Download Link | PGP Signature file of download |
---|---|---|
Windows Distribution |
...
Unix/Linux/Cygwin Distribution |
...
...
Info | ||
---|---|---|
| ||
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 |
Source Distributions
Description | Download Link | PGP Signature file of download |
---|---|---|
Source for Windows |
...
...
Source for Unix/Linux/Cygwin |
...
...
...
...
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:
Code Block | ||||
---|---|---|---|---|
| ||||
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
<version>1.5.0</version>
</dependency>
|
SVN Tag Checkout
Code Block |
---|
svn co http://svn.apache.org/repos/asf/activemq/camel/tags/]| [apache-camel-1.5.0.tar.gz.asc|http://www.apache.org/dist/activemq/apache-camel/1.5.0/apache-camel-1.5.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|http://www.mozilla.com/en-US/firefox/] {info} h3. Source Distributions ||Description||Download Link||PGP Signature file of download |Source for Windows| [apache-camel-1.5.0-src.zip|http://www.apache.org/dyn/closer.cgi/activemq/apache-camel/1.5.0/apache-camel-1.5.0-src.zip]| [apache-camel-1.5.0-src.zip.asc|http://www.apache.org/dist/activemq/apache-camel/1.5.0/apache-camel-1.5.0-src.zip.asc]| |Source for Unix/Linux/Cygwin| [apache-camel-1.5.0-src.tar.gz|http://www.apache.org/dyn/closer.cgi/activemq/apache-camel/1.5.0/apache-camel-1.5.0-src.tar.gz]| [apache-camel-1.5.0-src.tar.gz.asc|http://www.apache.org/dist/activemq/apache-camel/1.5.0/apache-camel-1.5.0-src.tar.gz.asc]| h3. 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|http://maven.apache.org/guides/introduction/introduction-to-the-pom.html] is: {code:xml} <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-core</artifactId> <version>1.5.0</version> </dependency> {code} h3. SVN Tag Checkout {code} svn co http://svn.apache.org/repos/asf/activemq/camel/tags/camel-1.5.0 {code} h2. Changelog For a more detailed view of new features and bug fixes, see the [release notes|http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11020&styleName=Html&version=11922] {jiraissues:url=http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=11020&fixfor=11922&sorter/field=issuekey&sorter/order=DESC&tempMax=1000} |
Changelog
For a more detailed view of new features and bug fixes, see: