Camel 1.5.0 release (work in progress)
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. - introduced new JT400, HL7, LDAP and Smooks components.
- Mail can now send html mails with the new
contentType
option. - Camel Maven Archetypes now available in m2eclipse Maven project creation.
- Java WebStart support
- 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.
New Enterprise Integration Patterns
- None
New Components
- JT400 for integration with AS/400 dataqueues
- HL7 for working with the HL7 MLLP protocol and the HL7 model using the HAPI library
- LDAP to perform searches in LDAP servers
- Smooks for working with EDI parsing using the Smooks library
New DSL
- Scala (work in progress, not fully feature complete)
New Data Formats
New Languages
New Examples
- None
API breakings
- None
Known Issues
- None
Important changes to consider when upgrading
JMX
Option usePlatformMBeanServer has changed its default value from false to true.
setHeader element in Spring DSL changed
You can no longer use a 'value' attribute like this to set a header to a constant:
<route> <from uri="seda:a"/> <setHeader headerName="theHeader" value="the value"> <expression/> </setHeader> <to uri="mock:b"/> </route>
Now, you can use a Constant expression to do the same thing:
<route> <from uri="seda:a"/> <setHeader headerName="theHeader"> <constant>the value</constant> </setHeader> <to uri="mock:b"/> </route>
Notice that this constant expression is also possible in the Java DSL:
.setHeader("theHeader", constant("the value"))
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
Object[] oldResult = (Object[])oldExchange.getOut().getBody(); BankQuote oldQuote = (BankQuote) oldResult[0];
CXF Produer in Camel 1.5
BankQuote oldQuote = oldExchange.getOut().getBody(BankQuote.class);
FTP Consumer
The option consumer.recursive
has changed the default value from true to false.
File Consumer
The option consumer.recursive
has changed the default value from true to false.
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.
Getting the Distributions
Binary Distributions
Description |
Download Link |
PGP Signature file of download |
---|---|---|
Windows Distribution |
||
Unix/Linux/Cygwin Distribution |
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
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:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-core</artifactId> <version>1.5.0</version> </dependency>
SVN Tag Checkout
svn co http://svn.apache.org/repos/asf/activemq/camel/tags/camel-1.5.0
Changelog
For a more detailed view of new features and bug fixes, see the release notes