Versions Compared

Old Version 103

changes.mady.by.user Claus Ibsen

Saved on

compared with

New Version 104

changes.mady.by.user Claus Ibsen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The component documentation generated from the source code has been double checked to be up to date and include all the options the endpoints supports.
  • Camel commands for Spring Boot
  • Many improvements to Camel Kura
  • Added transacted option to SQL Component when used as a consumer in a transacted route.
  • Added support for UPDATE operation to ElasticSearch.
  • Allow to reuse existing configured Elasticsearch Client on the ElasticSearch component, instead of creating a client per endpoint. 
  • The include and exclude options on File2 and FTP endpoints is now case in-sensitive out of the box.
  • Resource based component such as XSLT, Velocity etc can load the resource file from the Registry by using ref: as prefix.
  • Upgraded camel-amqp to the latest qpid-jms-client (also AMQP < 1.0 is not supported anymore).
  • Many improvements to Camel AMQP component.
  • The Metrics Component allows to capture Message History performance statistics with the MetricsMessageHistoryFactory 
  • Reduced the number of mbeans enlisted in the services tree, to only include mbeans that has value to be managed.
  • The Elasticsearch Component now supports MultiGet operation
  • The Throttler has been improved to be more performant and use a rolling window for time periods which gives a better flow.
  • The setHeader and setExchangeProperty allows to use a dynamic header key using the Simple language if the name of the key is a Simple language expression.
  • Add collate function to Simple language to make it easier to split a message body into sub lists of a specified size. The function is similar to the collate function from Groovy.
  • The Camel Run Maven Goal is able to auto detect if its a OSGi Blueprint or CDI project so end users no longer have to explicit configure this on the plugin.
  • Camel-Elasticsearch now supports Multiget, Multisearch and exists operation
  • Camel-Git now supports Cherry-pick operation
  • Stopping the Main class from JMX will now trigger shutdown of the Main class/JVM also, as it does when hitting ctrl + c.
  • Added option to skipFirst to the Tokenizer language to make it easy to skip the very first element, when for example splitting a CSV file using the Splitter EIP.
  • The Rest DSL now supports default values for query parameters
  • The Rest DSL now only binds from POJO to JSon/XML if the content-type is for json or xml. This allows you to specify a custom content-type and omit the binding, such as when having binary payloads.
  • Exchange and Message only output id in their toString method to avoid outputting any message details such as sensitive details from message bodies.
  • Camel Error Handler no longer log message body/header details when logging the Message History. This avoids logging any sensitive details from message bodies.
  • Camel Exception Clause and Error Handler now supports using a custom Processor to be invoked right after an exception was thrown using the new onExceptionOccurred option.
  • RabbitMQ consumer more resilient to auto re-connect in case of connection failures
  • The JSON camel-jackson can be used as a type converter to convert json to/from POJO and String/byte[] types, if enabled.
  • The SQL Component now supports loading the SQL queries from external files on the classpath or file system, where you can format the queries using newlines and indenting.
  • The Mail consumer allows to use an idempotent repository which allows to cluster consuming from the same mailbox, and let the repository coordinate whether a mail message is valid for the consumer to process.
  • Added support for completion interval on the SJMS Batch component, which allows to trigger batch completion in a fixed scheduled interval.
  • The HTTP and HTTP4 producers now support the disableStreamCache option to allow to use the raw response stream as the message body instead of wrapping using Stream caching
  • The Camel CDI component has been improved to better fit into the CDI programming model, cover a larger set of containers, and provide these new features:
    • The Camel events from the org.apache.camel.management.event package (like CamelContextStartedEvent) can be observed as CDI events
    • The new CDI event Camel endpoint enable CDI events to be seamlessly consumed from (respectively produced by) Camel consumers (respectively Camel producers)
    • CDI beans annotated with the @Converter annotation are automatically registered as type converters
    • The CDI Camel contexts can be properly customised programmatically in bean constructor or @PostConstruct lifecycle callback
    • Camel routes configured in RouteBuilder beans are added before the corresponding Camel contexts get started
    • CDI Camel contexts are now properly adapted when deployed in OSGi containers and are registered as OSGi services
    • Proper support of multiple Camel contexts across all the features
  • The XSLT component now supports Saxon's integrated extension functions.
  • Added option reuseChannel to Netty4 which allows to reuse existing Channel when using a netty producer to call a server multiple times during routing an Exchange.
  • Idempotent Repository now supports optional serialized headers 
  • Rest DSL adjusted to swagger spec 2.0 and Swagger Java as well.
  • Camel-quartz2 now supports customCalendar to avoid specific range of dates (Holidays for example) in Scheduler and Triggers.

...

  • This is the last release that will support Java 1.7. Releases after this is expected to require Java 1.8+. 
  • Some changes in Rest DSL to adjust naming and types to the Swagger Spec 2.0
  • Any custom component that supports suspension in doSuspend/doResume should implement the new Suspendable marker interface, so Camel knows there is custom logic for suspension in the component.
  • Exchange and Message only output id in their toString method to avoid outputting any message details such as sensitive details from message bodies.
  • Removed camel-hbase as Karaf feature as it did not really work well in OSGi
  • Upgraded camel-hbase to Hadoop 2.x and HBase 1.1.x
  • camel-infinispan requires Java 8.
  • camel-mustache requires Java 8.
  • Support for Spring 4.0.x is deprecated. Support for Spring 3.x is being removed in the next release.
  • Support for Karaf 2.x and 3.x is deprecated. And removed in next release, where Karaf 4.x onwards is only supported.
  • camel-jetty8 is deprecated and being removed in next release.
  • Moved some Camel tooling related dependencies (such as maven/plexus) from the Camel Parent BOM to the tooling BOM (to have them separated).
  • camel-amqp do not support 0.9 anymore. 
  • camel-spring-integration feature has been removed from the Camel karaf.
  • The Mail component now requires to configure to, cc, and bcc using lower case keys, eg to=foo@bar.com, instead of To=foo@bar.com as previously.
  • The File consumer no longer probe the file content by default. See the option probeContentType for more details.
  • If using Bean or Class component and specifying additional parameters in the endpoint uri to configure on the bean, then these options should now be prefixed with bean., eg foo=123 is now bean.foo=123.
  • The Twitter delay option is changed from seconds to milli seconds by default, eg 10 should be 10000 to indicate 10 seconds. This is aligned how other components with delay option behaves. 
  • The options attributeNames and messageAttributeNames on AWS-SQS is changed to a string type where you can separate multiple values using comma. Before the type was a Collection which was much harder to configure in the Camel uris.
  • The hbase component now require row mapping from the endpoint uri to be prefixed with row. as prefix.
    Before: family=info&qualifier=firstName&family2=birthdate&qualifier2=year. After: row.family=info&row.qualifier=firstName&row.family2=birthdate&row.qualifier2=year.
  • As part of the Camel CDI component refactoring, DeltaSpike is not used anymore for the sourcing of the configuration properties. This new version of the component is agnostic to any configuration sourcing mechanism and delegates that concern to the application so that it can declare a custom PropertiesComponent bean whose sourcing is tailored to its need. DeltaSpike can still be used by the application by declaring a PropertiesComponent bean configured with a PropertiesParser relying on DeltaSpike. See the camel-example-cdi-properties example for more details.

...