3.5. Component Updates

Since Apache Camel version 2.11, upgraded to use Apache Mina 2.x.

Since Apache Camel version 2.11, the default value of the convertLFtoCR option of the HL7 MLLP codec has been changed from true to false. Likewise, the HL7 DataFormat and TypeConverter classes do not perform this conversion anymore.

Since Apache Camel version 2.11, the type for file last modified header is changed from java.util.Date to long.

Since Apache Camel version 2.12, when using idempotent repository, the file and FTP components invoke the contains method for a file name, but not for a directory name.

Since Apache Camel version 2.11, added support to parse a CSV, if a field begins with a ' (single quote) character.

Since Apache Camel version 2.11, MINA2 uses OrderedThreadPoolExecutor by default. There is a new option, orderedThreadPoolExecutor, which you can configure to false, in order to revert back to unordered. If using SSL, however, an ordered thread pool must be used.

Since Apache Camel version 2.11, Netty uses OrderedThreadPoolExecutor by default. There is a new option, orderedThreadPoolExecutor, which you can configure to false, in order to revert back to unordered. If using SSL, however, an ordered thread pool must be used.

Since Apache Camel version 2.11, Netty requires commons-pool as a dependency.

Since Apache Camel version 2.11, the default value of the delay option on the Timer component has changed from 0 to 1000.

Since Apache Camel version 2.11, for any VM (or SEDA) endpoints with the same name, if the endpoints specify a queue size, the queue size must be the same. The queue names and their corresponding queue size values are logged at INFO level, in order to help you spot any mis-configuration of the queue sizes.

Since Apache Camel version 2.11, the getter and setter for the awaitExistence bean property from the org.apache.camel.component.zookeeper.ZooKeeperEndpoint class have been marked as @deprecated and removed from the API documentation (the property has no effect).

Since Apache Camel version 2.11, if you define an XSLT script that has xi:include elements, the included files are found by searching the same scope as the endpoint (by default). That is, if the endpoint URI is specified using the file: scheme, the included files are found by searching the file system; or if the endpoint is specified using the classpath: scheme, the included files are found by searching the classpath. You can override this behavior by specifying the file: or classpath: scheme explicitly in the href attribute of xi:include. Before Apache Camel version 2.11, the default behavior was to search the classpath for included files, irrespective of the scheme used in the endpoint URI.

Since Apache Camel version 2.11, GAE components no longer have any dependency on the Spring framework.

Since Apache Camel version 2.12, if you want to support the RSA v1.5 key transport algorithm at run time, you must configure it explicitly. If not, requests to use this algorithm are rejected, by default.

Since Apache Camel version 2.12, the userConfigURL option loads resources from the classpath by default.