Welcome to the 2.21.0 release which resolved 400 issues including new features, improvements and bug fixes.
This release supports only Spring Boot 1.5.x. Support for Spring Boot 2.0.x is coming in Camel version 2.22 which is planned for early summer 2018.
javax.jms.StreamMessage
types in JMS component.useList
option which can be used to download a single known file without use LIST operation on the FTP server (which can be slow if the FTP server has many files in the LIST results)ExtendedStartupListener
that allows a callback just after the CamelContext has been fully started.DirectConsumerNotAvailableException
being thrown during startup etc.FileIdempotentRepository
so the internal in-memory cache is only used for quick lookup of the most frequent file names, and lookup from disk as well. See more details in the class javadoc of the file.AggregationStrategy
implementation. .to("bean:myBean::myMethod")
The following issues has been fixed
Fixed afterApplicationStart callback on camel-spring-boot to be called later and after CamelContext has been fully started.
Fixed an issue testing with @UseAdviceWith and Camel on Spring Boot.
Fixed OnCompletion would not be triggered from a route using Split EIP and an exception was thrown during splitting.
Fixed Kafka consumer stops consuming messages when exception occurs during offset commit.
Fixed Netty4 consumer to stop taking in new requests while being shutdown, as otherwise it cannot graceful shutdown if new requests come in faster than it can process existing in-flight messages.
Fixed an issue with Routing Slip and Dynamic Router when using context scoped error handler, could cause the error handler to become stopped.
Fixed Rest DSL with Jetty security via custom define security handler and turned on api-doc as well would not startup Jetty server due missing NoLoginService error.
Fixed Blueprint error: “name is already instanciated as null and cannot be removed”
Fixed a CXF continuation timeout issue with camel-cxf consumer could cause the consumer to return a response with data instead of triggering a timeout to the calling SOAP client.
Fixed camel-cxf consumer doesn't release UoW when using robust oneway operation
Fixed using AdviceWith and using weave methods on onException etc. not working.
Fixed Splitter in parallel processing and streaming mode may block, while iterating message body when the iterator throws exception in first invoked next() method call.
Fixed Kafka consumer to not auto commit if autoCommitEnable=false.
Fixed file consumer was using markerFile as read-lock by default, which should have been none.
Fixed using manual commit with Kafka to provide the current record offset and not the previous (and -1 for first)
Fixed Content Based Router in Java DSL may not resolve property placeholders in when predicates
Important changes to consider when upgrading
DirectConsumerNotAvailableException
being thrown during startup etc. The old beavhaior can be turned on by setting block=false
on the direct component level, or on endpoints where needed.camel-saxon
then the SaxonXpathFactory class is created in the https://www.saxonica.com/html/documentation/xpath-api/jaxp-xpath/factory.html[recommended way] from Saxon. It will fallback and create the factory the old way if not possible.camel-json-validator
component has switched from using Everit to NetworkNT JSon Schema validator library, as the former had ASF license implications and would not be allowed in future Camel releases. The NetworkNT supports v4 draft of JSon Schema as validation so make sure to use that draft version in your schemas.FileIdempotentRepository
so the internal in-memory cache is only used for quick lookup of the most frequent file names, and lookup from disk as well. See more details in the class javadoc of the file.endpoints.camelroutes.read-only = false