Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 75ECBC74E for ; Mon, 29 Jul 2013 09:20:29 +0000 (UTC) Received: (qmail 4758 invoked by uid 500); 29 Jul 2013 09:20:29 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 4732 invoked by uid 500); 29 Jul 2013 09:20:28 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 4725 invoked by uid 99); 29 Jul 2013 09:20:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jul 2013 09:20:28 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jul 2013 09:20:26 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id F22FF2388860 for ; Mon, 29 Jul 2013 09:20:05 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r871680 - in /websites/production/camel/content: cache/main.pageCache camel-2120-release.html camel-jmx.html Date: Mon, 29 Jul 2013 09:20:05 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20130729092005.F22FF2388860@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Mon Jul 29 09:20:05 2013 New Revision: 871680 Log: Production update by buildbot for camel Modified: websites/production/camel/content/cache/main.pageCache websites/production/camel/content/camel-2120-release.html websites/production/camel/content/camel-jmx.html Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/camel-2120-release.html ============================================================================== --- websites/production/camel/content/camel-2120-release.html (original) +++ websites/production/camel/content/camel-2120-release.html Mon Jul 29 09:20:05 2013 @@ -94,7 +94,7 @@

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

-
  • Endpoint Annotations along with automatically created HTML documentation for the endpoint parameters; this makes it easier for component developers to add a few refactoring-safe annotations to their Endpoint or Consumer implementations and, (along with javadoc comments on the field or setter method), get nice user documentation on how to use the endpoint for free.
  • ComponentConfiguration API provides a handy API for tools developers to introspect on a Component to find all the possible parameters, their types and any extra annotations (like Bean Validation Annotations) to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for configuring endpoints than just letting folks edit Strings.
  • Endpoi ntCompleter API provides a hook so that command line tools (like Karaf's shell), IDEs and web tools can get (bash tab like) auto-completion on endpoint paths (such as file or directory names, message queue names, database table names) when creating or using new endpoints
  • Reduced stack-frames in use during routing, that also makes Camel's stack traces being logged much less verbose. This also allows people to easier debug the internals of Camel as less AsyncCallback callbacks are in use during routing.
  • Easy to use Message History out of the box. And included message history as "route stack-trace" when exceptions logged by Error Handler to make it easier for end users to spot where the exception o ccurred.
  • Spring Web Services now supports setting/receiving SOAP headers more easily using a header on the Camel Message.
  • Evaluating Groovy expressions is faster as we cache the compiled scripts.
  • Added base64 option to Shiro Security to allow transferring security token over JMS and other transports as base64 encoded representation.
  • Made it easier to use Shiro Security as the credentials can be provided in headers, when sending a message to a secured route.
  • Bindy now supports enums.
  • Added new BacklogDebugger to perform live debugging of messages during routing. The BacklogDebugger has JMX API allows tooling to control the debugger.
  • While using the Jackson library through the JSON Dataformat there's now a jsonView attribute you could make use of directly inside the DSL itself.
  • SMPP now supports optional parameters in all commands where they are possible.
  • JDBC now supports named parameters.
  • Added timeout support for Direct producers to wait for cons umer to become active.
  • Added stats action to ControlBus to easily get performance statics in a single XML message.
  • Added support for request timeout on Netty producer, and to configure logging level on Netty consumer to be less noisy for ChannelClosedException which can flood the logs when client disconnects abruptly.
  • Spring Batch component producer now returns the JobExecution instance as the output message. Users can use the JobExecution instance to perform some operations using the Spring Batch API directly.
  • Added support for NULL values in SQL with named parameters.
  • Optimized Jetty streaming responses in non-chunked mode; and as well using buffer sizes based on HttpServletResponse.getBufferSize() instead of fixed size of 4kb.
  • Added greedy option to scheduled polling consumer.
  • Added support for accessing the length field on Java arrays in Simple language.
  • Added support for using JAXB annotations with Camel's Jackson JSON component.
  • Added the ability for Bindy to skip content when parsing fixed-length records.
  • MongoDB now supports aggregation queries.
  • Netty allows to use shared Netty boss and worker thread pools.
  • The Camel Maven Archetypes for component and data format now packages as OSGi bundles out of the box.
  • Easier Stream caching configuration using StreamCachingStrategy. Also allows spool directory per CamelContext instead of shared per JVM. And insight at runtime using JMX management. As well allowing to plugin 3rd party implementations.
  • Improved Netty to be able to join an UDP multicast group.
  • Using Camel Spring is now setting up Camel routes later in the process allow Spring to complete all of its dependency injection, before Camel RouteBuilder instances is configured. This allows to safely use Spring dependency injection in these RouteBuilder classes.
  • Services in a CamelContext which can only be enlisted once (eg it similar to a static in a JVM) has simpler and fixed MBean names in JMX.
  • JDBC based aggregation repository for the Aggregate EIP now supports optimistic locking, allows clustered Camel applications to use a shared database for the aggregation repository.
  • Recipient List stores a property (Exchange.RECIPIENT_LIST_ENDPOINT) on the Exchange with the [URI] of the Endpoint the message was sent to.
+
  • Endpoint Annotations along with automatically created HTML documentation for the endpoint parameters; this makes it easier for component developers to add a few refactoring-safe annotations to their Endpoint or Consumer implementations and, (along with javadoc comments on the field or setter method), get nice user documentation on how to use the endpoint for free.
  • ComponentConfiguration API provides a handy API for tools developers to introspect on a Component to find all the possible parameters, their types and any extra annotations (like Bean Validation Annotations) to be able to create/edit endpoints or URI strings so that tools can generate nicer UIs for configuring endpoints than just letting folks edit Strings.
  • Endpoi ntCompleter API provides a hook so that command line tools (like Karaf's shell), IDEs and web tools can get (bash tab like) auto-completion on endpoint paths (such as file or directory names, message queue names, database table names) when creating or using new endpoints
  • Reduced stack-frames in use during routing, that also makes Camel's stack traces being logged much less verbose. This also allows people to easier debug the internals of Camel as less AsyncCallback callbacks are in use during routing.
  • Easy to use Message History out of the box. And included message history as "route stack-trace" when exceptions logged by Error Handler to make it easier for end users to spot where the exception o ccurred.
  • Spring Web Services now supports setting/receiving SOAP headers more easily using a header on the Camel Message.
  • Evaluating Groovy expressions is faster as we cache the compiled scripts.
  • Added base64 option to Shiro Security to allow transferring security token over JMS and other transports as base64 encoded representation.
  • Made it easier to use Shiro Security as the credentials can be provided in headers, when sending a message to a secured route.
  • Bindy now supports enums.
  • Added new BacklogDebugger to perform live debugging of messages during routing. The BacklogDebugger has JMX API allows tooling to control the debugger.
  • While using the Jackson library through the JSON Dataformat there's now a jsonView attribute you could make use of directly inside the DSL itself.
  • SMPP now supports optional parameters in all commands where they are possible.
  • JDBC now supports named parameters.
  • Added timeout support for Direct producers to wait for cons umer to become active.
  • Added stats action to ControlBus to easily get performance statics in a single XML message.
  • Added support for request timeout on Netty producer, and to configure logging level on Netty consumer to be less noisy for ChannelClosedException which can flood the logs when client disconnects abruptly.
  • Spring Batch component producer now returns the JobExecution instance as the output message. Users can use the JobExecution instance to perform some operations using the Spring Batch API directly.
  • Added support for NULL values in SQL with named parameters.
  • Optimized Jetty streaming responses in non-chunked mode; and as well using buffer sizes based on HttpServletResponse.getBufferSize() instead of fixed size of 4kb.
  • Added greedy option to scheduled polling consumer.
  • Added support for accessing the length field on Java arrays in Simple language.
  • Added support for using JAXB annotations with Camel's Jackson JSON component.
  • Added the ability for Bindy to skip content when parsing fixed-length records.
  • MongoDB now supports aggregation queries.
  • Netty allows to use shared Netty boss and worker thread pools.
  • The Camel Maven Archetypes for component and data format now packages as OSGi bundles out of the box.
  • Easier Stream caching configuration using StreamCachingStrategy. Also allows spool directory per CamelContext instead of shared per JVM. And insight at runtime using JMX management. As well allowing to plugin 3rd party implementations.
  • Improved Netty to be able to join an UDP multicast group.
  • Using Camel Spring is now setting up Camel routes later in the process allow Spring to complete all of its dependency injection, before Camel RouteBuilder instances is configured. This allows to safely use Spring dependency injection in these RouteBuilder classes.
  • Services in a CamelContext which can only be enlisted once (eg it similar to a static in a JVM) has simpler and fixed MBean names in JMX.
  • JDBC based aggregation repository for the Aggregate EIP now supports optimistic locking, allows clustered Camel applications to use a shared database for the aggregation repository.
  • Recipient List stores a property (Exchange.RECIPIENT_LIST_ENDPOINT) on the Exchange with the URIs of the Endpoint the message was sent to.
  • Added sanitize option to Camel JMX to hide sensitive information such as passwords.

Fixed Issues

Modified: websites/production/camel/content/camel-jmx.html ============================================================================== --- websites/production/camel/content/camel-jmx.html (original) +++ websites/production/camel/content/camel-jmx.html Mon Jul 29 09:20:05 2013 @@ -93,7 +93,7 @@ Camel also provides a Activating JMX in Camel
-
+
Spring JAR dependency, required for Camel 2.8 or older
spring-context.jar, spring-aop.jar, spring-beans.jar, and spring-core.jar are needed on the classpath by Camel to be able to use JMX instrumentation. If these .jars are not on the classpath, Camel will fallback to non JMX mode. This situation is logged at WARN level using logger name org.apache.camel.impl.DefaultCamelContext. @@ -670,6 +670,35 @@ context.getManagementNameStrategy().setN ]]> + +

Hiding sensitive information

+

Available as of Camel 2.12

+ +

By default Camel enlist MBeans in JMX such as endpoints configured using URIs. In these configuration there may be sensitive information such as passwords.
+These information can be hidden by enabling the sanitize option as shown below:

+ +

Using Java DSL you turn this on by:

+
+ +
+ +

And from Spring DSL you do:

+
+ +
+ +

This will mask [URI]s having options such as password and passphrase, and use xxxxxx as the replacement value.

+ +
Setting sanitize=true will only mask password and passphrase configured in URIs. If any custom Camel Component exposes custom JMX attributes then these attributes is shown as is.
+

See Also