THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Component documentation now included in the built component JARs. And Java API and JMX API to access that documentation. And APIs to explain an endpoint uri and what all those configured options mean.
- Component can now have associated label(s) which are used for grouping components into: core, database, messaging, http, rest, etc.
- Provide Configurer for user to configure the CXF conduit and CXF destination from Java code
- Added a
DelegateEndpoint
interface into Camel API - Support to setup the SslContextParameters in the camel-restlet component
- Java DSL - Should support nested choice in doTry .. doCatch
- MongoDb component now stores OIDs of the inserted records in the message header
- Recipient List now supports specifying custom Exchange Pattern in the endpoint ur's
- Type Converter to enum's is now case insensitive, so you can convert safely level=info to an enum with name Level.INFO etc.
- XSLT and Validation components now provides all their endpoint configurations in the endpoint, and not only in the component, making these components like any other components.
- Made the Camel Karaf Commands reusable by moving common code into a
camel-commands-core
module that SPI can extend and plugin Camel commands for other environments. - Further hardening of the SJMS component.
- Rest DSL with embedded routes now supports onException, intercept etc in use for those embedded routes, just like any regular routes.
- Rest DSL now by default uses custom error message as-is without attempting to binding output (requires a HTTP error code of 300+ is set as a header)
- Camel Using PropertyPlaceholder now supports specifying a default value together with the key to lookup.
- Camel Using PropertyPlaceholder now supports not having to define a PropertiesComponent if all the placeholder keys has default values which are to be used (less configuration needed in those situations).
- Camel Using PropertyPlaceholder now supports 3rd party functions to lookup the property values, this allow end users to implement their own logic - we provide 3 out of the box functions to lookup values from OS environment variable, JVM system properties, or the service name idiom.
- RabbitMQ now pools Channels for the producer to avoid sharing same Channel among concurrent producers which are not recommended by RabbitMQ client.
- Camel commands is now reusable outside Apache Karaf as a base by the
commands-core
module. - Camel commands using Jolokia for remote communication by the
commands-jolokia
module. - More minor processors such as setHeader, removeHeader, removeHeaders and ditto for properties is now also enlisted in JMX under processors.
- Optimized usage of type conversion during routing reducing the number of attempts needed.
Fixed issues
- Fixed processors was not enlisted in JMX when routes was transacted.
- Fixed the NullPointerException when using CXF endpoint with enrich
- Fixed the endpointProperty of restConfiguration doesn't work issue
- Fixed the issue that CircuitBreakerLoadBalancer fails on async processors
- Fixed MyBatis consumer ignoring maxMessagesPerPoll option
- Fixed potential issue with pollEnrich not triggering error handler if an exception was thrown in the polling.
- Fixed a memory leak if using Dynamic Router that loops many times, and uses any of
convertBodyTo
orsetBody
ortransform
in the loop, causing memory to stack up until the Exchange is done. - Fixed and improved how Bean component and Simple language invoking beans detect methods that are overridden, and able to filter and apply this as a single method, to be invoked. Avoids AmbiguousMethodCallException being thrown.
- Fixed a thread leak if restarting routes using stop/start and the routes is a scheduled poll consumer, such as file/ftp components.
...