| Wiki Markup |
|---|
h1. Camel 1.5.0 release (work in progress)
{div:style=padding-right:20px;float:left;margin-left:-20px;}
!http://activemq.apache.org/camel/download.data/camel-box-v1.0-150x200.png!
{div}
{div:style=min-height:200px}
h2. New and Noteworthy
Welcome to the 1.5.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)
* various improvements in [FTP], [File], [Flatpack] and [XMPP] components
* minor improvements in [CXF], [SpringIntegration], [Mail] and [Mina] components
* [File] consumers now default uses exclusive read locking when it consume files, meaning that they wont consume files that are in the progress of being written by third part. The [FTP] consumer has this support as well, however it is disabled by default as it requires write privileges.
* [File] component supports expression to set dynamic filename patterns instead of using the {{FileComponent.HEADER_FILE_NAME}} header. See [File Language] for samples and use cases.
* important changes in ProducerTemplate (see below)
* splitter() now handles streaming avoiding reading entire content into memory (consuming very big 1gb files is now possible)
* introduced new [jt400], [HL7], [LDAP] and [Smooks] components.
* introduced [Delay Interceptor] to slow down processing to show how things is happening nice and slow, so you are not bombarded with zillions of logging output.
* [Mail] can now send html mails with the new {{contentType}} option.
* [Camel Maven Archetypes] now available in [m2eclipse|http://m2eclipse.sonatype.org] [Maven project creation|http://docs.codehaus.org/display/M2ECLIPSE/Creating+Maven+projects].
* [Java WebStart support|How do I run Camel using Java WebStart]
* refinements in loading resources using OSGi bundles, should now handle different OSGi platforms much better
* [Type Converter] now supports Exchange as 2nd parameter to allow converters access to the Exchange and thus the [CamelContext] as well. To be used for setting encoding in the future.
h3. New [Enterprise Integration Patterns]
* None
h3. New [Components]
* [jt400] for integration with AS/400 dataqueues
* [HL7] for working with the HL7 MLLP protocol and the [HL7 model|http://www.hl7.org] using the [HAPI library|http://hl7api.sourceforge.net]
* [LDAP] to perform searches in LDAP servers
* [Smooks] for working with EDI parsing using the [Smooks library|http://milyn.codehaus.org/Smooks]
h3. New [DSL]
* [Scala|Scala DSL] (work in progress, not fully feature complete)
h3. New [Data Formats|Data Format]
* [Flatpack]
* [HL7]
* [EDI]
h3. New [Languages]
* [Constant]
* [Header]
* [File Language]
h3. New Examples
* [camel-example-axis|http://activemq.apache.org/camel/tutorial-axis-camel.html]
h2. API breakings
* ProducerTemplate now throws {{RuntimeCamelException}} for sendBody/requestBody methods.
h2. Known Issues
* None
h2. Important changes to consider when upgrading
h3. ProducerTemplate
The [ProducerTemplate|http://activemq.apache.org/camel/maven/camel-core/apidocs/org/apache/camel/ProducerTemplate.html] has refined its sendBody and requestBody methods to throw {{RuntimeCamelException}}, with the caused exception wrapper, in case the Exchange failed with an exception. Also if the exchange has set an {{FAULT}} message then the {{FAULT}} message is returned.
The old behavior in Camel 1.4 or older was just plain wrong!
h3. JMX
Option usePlatformMBeanServer has changed its default value from *false* to *true*.
h3. setHeader element in Spring DSL changed
You can no longer use a 'value' attribute like this to set a header to a constant:
{code:language=xml}
<route>
<from uri="seda:a"/>
<setHeader headerName="theHeader" value="the value">
<expression/>
</setHeader>
<to uri="mock:b"/>
</route>
{code}
Now, you can use a [Constant] expression to do the same thing:
{code:language=xml}
<route>
<from uri="seda:a"/>
<setHeader headerName="theHeader">
<constant>the value</constant>
</setHeader>
<to uri="mock:b"/>
</route>
{code}
Notice that this constant expression is also possible in the Java DSL:
{code:java}
.setHeader("theHeader", constant("the value"))
{code}
h3. Data format specification in Spring DSL changed
The way you specify data formats in the Spring DSL has changed. You could do this in Camel 1.4:
{code}
<camelContext id="camel" xmlns="http://activemq.apache.org/camel/schema/spring">
<jaxb id="myJaxb" prettyPrint="true" contextPath="org.apache.camel.example"/>
<xstream id="xs" prettyPrint="true"/>
<route>
<from uri="direct:start"/>
<marshal ref="myJaxb"/>
<to uri="direct:marshalled"/>
</route>
...
{code}
Now, you specify the same as:
{code}
<camelContext id="camel" xmlns="http://activemq.apache.org/camel/schema/spring">
<dataFormats>
<jaxb id="myJaxb" prettyPrint="true" contextPath="org.apache.camel.example"/>
<xstream id="xs" prettyPrint="true"/>
</dataFormats>
<route>
<from uri="direct:start"/>
<marshal ref="myJaxb"/>
<to uri="direct:marshalled"/>
</route>
...
{code}
h3. CXF Producer
The result of CXF producer has changed to use MessageContentsList instead of Object array to hold the response.
If you use the exchange.getOut.getBody(YourType.class), CXFMessage will check the list members and chose the most right answer for you.
CXF Producer before Camel 1.4
{code:language=java}
Object[] oldResult = (Object[])oldExchange.getOut().getBody();
BankQuote oldQuote = (BankQuote) oldResult[0];
{code}
CXF Produer in Camel 1.5
{code:language=java}
BankQuote oldQuote = oldExchange.getOut().getBody(BankQuote.class);
{code}
h3. FTP component
The option {{consumer.recursive}} has changed the default value from *true* to *false*.
Now throws {{FtpOperationFailedException}} 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 {{FtpOperationFailedException}} instead of {{WARN}} 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. File Consumer
The option {{consumer.recursive}} has changed the default value from *true* to *false*.
h3. camel-mina
In 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-mail
In 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.
{div}
h2. Getting the Distributions
h3. Binary Distributions
||Description||Download Link||PGP Signature file of download
|Windows Distribution| [apache-camel-1.5.0.zip|http://www.apache.org/dyn/closer.cgi/activemq/apache-camel/1.5.0/apache-camel-1.5.0.zip]| [apache-camel-1.5.0.zip.asc|http://www.apache.org/dist/activemq/apache-camel/1.5.0/apache-camel-1.5.0.zip.asc]|
|Unix/Linux/Cygwin Distribution| [apache-camel-1.5.0.tar.gz|http://www.apache.org/dyn/closer.cgi/activemq/apache-camel/1.5.0/apache-camel-1.5.0.tar.gz]| [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}
|
Page History
Overview
Content Tools
Apps