Spring Boot automagically loads XML routes definitions from classpath.
Spring Boot applications now block the main thread of the execution. CamelContext now also includes a getManagedProcessor API to easily get the mbean client api for the processor, so you can access the runtime JMX statistics from Java code. The runtime route processors and their corresponding model definition are now linked by their id using HasId, so its easier to obtain the processor or model definition from the getProcessor(id) and getProcessorDefintion(id) api on CamelContext. This ensures the consumer can deal with mail boxes that has problematic mails that otherwise will cause no mails to be retrieve by the consumer in the batch. Added options to Mail consumer so it can skip or handle a mail message that cannot be read from the mail server in the batch and then move on to read the next message. If completed the group is emitted as-is, and the new incoming Exchange is used to start a new group from scratch. This supports the use-case where an incoming Exchange are used to determine if the current aggregated group is completed or not. The Aggregator2 now supports pre-completion mode if the aggregation strategy implements PreCompletionAwareAggregationStrategy. The Aggregator2 now includes more runtime statistics which can be accessed from Java and JMX about number of incoming and completed exchanges, and per different completion triggers. The Aggregator2 now enlists in JMX using a ManagedAggregateProcessorMBean which has more information, and also allows using the aggregate controller to control it. A default controller is provided out of the box if none has been configured. The Aggregator2 EIP now allows an external source using a AggregateController to control the aggregator, such as for forcing completing a group or all groups, or query runtime information from the aggregator. #Google app engine sdk 1.9.30 download#
Added receviveBufferSize option to the FTP component to make download faster.properties files using a specific charset such as UTF-8. The Properties component (property placeholder) now supports an encoding option to allow reading the.Added SEARCH operation to Elasticsearch component.JMS component now allows configuring concurrentConsumers/maxConcurrentConsumers separately between from(jms) vs to(jms) using request/reply over JMS.Also the created producer/consumer is stopped when CamelContext is stopping to cleanup properly. POJO Producing and POJO Consuming lifecycle is now in sync with CamelContext which ensures it works as similar to Camel Routes does.Any misconfiguration now throws an exception explaining the problem. Java DSL using choice with end vs endChoice now validates you use them as intended.Using setFaultBody / setFaultHeader behaves similar to setBody / setHeader to preserve existing headers/attachments by setting on existing IN or OUT message.MongoDB tailable consumers now allow setting the readPreference option.Added onPrepareFailure option to Dead Letter Channel to allow a custom processor to prepare the Exchange before sending to the dead letter queue.The route models (definition classes) preserve property placeholders, which allows round trip editing, and also prevents showing potential sensitive information.Welcome to the 2.16.0 release which approx 600 issues resolved (new features, improvements and bug fixes such as.)
0 kommentar(er)
