THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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.
- Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.
- Mail component no longer includes headers starting with
Camel
in their keys, as those are consider internal headers and should not be included in the sent emails.
New Enterprise Integration Patterns
...
- Spring 4.1.x is now the default out of the box Spring version.
- Unit testing with Spring 4.0.x requires using camel-test-spring40, as camel-test-spring is for Spring 4.1 or better.
- Remember to add
@BootstrapWith
(CamelTestContextBootstrapper.
class
)
if upgrading from Spring 3.x or 4.0.x to Spring 4.1 onwards, and using the camel-test-spring module. - XSLT component now require configuring
transformerFactory
using URIs with the #syntax to refer to a bean. Just like any other component would do. - Slight refactor in
camel-metrics
component which may affect users who are using the java endpoint types instead of configuring using uris camel-csv
upgraded to Commons CSV 1.x which has a different API than the old 0.x version. End users may need to adjust their code.camel-sjms
has been refactored a bit to further harden this component. End users may need to adjust their code.- The simple function properties:locations:key has been renamed to properties-location:locations:key, as it would clash with the new functionality to specify a default value after the key name, eg properties:key:default
- Removed the backlog tracer commands from the Karaf Camel commands as they are not suitable for a CLI environment
- The need for runtime specific servlets in Swagger has been removed, and instead just use the default servlet which is provided out of the box.
org.apache.camel.spi.InflightRepository
now includes additional methods for browsing in-flight exchanges.- Using ?exchangePattern=InOnly or InOut in endpoint uris now take precedence as the pattern in use when sending to the endpoint, using to/recipient list.
DefaultClassLoader
now fallback and use the application context classloader that may have been set onCamelContext
to better be able to load classes/resources from classpath in different runtime environments.- Mail component no longer includes headers starting with
Camel
in their keys, as those are consider internal headers and should not be included in the sent emails.
Getting the Distributions
...