Page History

...

Welcome to the 2.15.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

• Component, data format, language and eip 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, eip configuration and what all those configured options mean.  In other words the same level of complete documentation of your Camel apps at both design and runtime, accessible from Java / JMX and tooling.
• Component, data format, language and eip 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.
• Asynchronous routing engine that are forced to block threads now exposes this using a manager that offers runtime insight using JMX. And as well attempts to free blocked threads during graceful shutdown, to avoid any threads hanging in the JVM.
• Swagger now supports any kind of runtime environment, as only JMX being enabled is required.
• XML Security component supports now  XAdES-BES/EPES in the signer endpoint.
• HL7 MLLP codec now supports Netty4 based transport.
• Inflight repository now allows to browse the current inflight exchanges to obtain information where these exchanges are inflight and for how long. Expose this information in JMX and Camel commands as well.
• Graceful Shutdown now logs information about the inflight exchanges that are still present during shutdown and a timeout was hit.
• Message History which dumps Exchange information not supports the Exchange.LOG_DEBUG_BODY_MAX_CHARS option to limit the max chars outputted in the logs.
• DefaultClassLoader now fallback and use the application context classloader that may have been set on CamelContext to better be able to load classes/resources from classpath in different runtime environments.
  
• Camel JMX now includes current inflight exchanges at processor level, which means we can have a complete breakdown where exchanges are, and as well from the improved InflightRegistry which has APi and JMX api to browse the current inflight with details of the exchange and processing times etc.

...