[
https://issues.apache.org/activemq/browse/CAMEL-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Bouer updated CAMEL-2199:
------------------------------
Attachment: CAMEL-2199.zip
×Here is a basic implementation of this component.
Basic usage goes like:
from("direct:a").to("elog:Hello ${header.FOO}")
This component uses the logcomponent formatter so it can accept the same format
options, However since exchange logging is optional. it must be on for the
formatter options to have any effect. e.g:
from("seda:b")
.to("elog:Whassup ${header.FOO}?showExchange=true&showBody=true");
This component lacks groupSize option for throughput logging control.
P.S
WireTap can't really do the same as I said on the description.
The only way to achieve the same functionality without this component is using
.recipientList(new SimleExpression("log:hello ${header}")) , this has the
downside of creating a new endpoint for each message with a different header
value.which this component solves.
> Introduce a new log component for dynamic logging.
> --------------------------------------------------
>
> Key: CAMEL-2199
> URL: https://issues.apache.org/activemq/browse/CAMEL-2199
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Eric Bouer
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: CAMEL-2199.zip
>
>
> It's a common task to preform logging of human message with dynamic content
> like headers/properties or anything else that can be produced with one of the
> dynamic languages.
> Right now the way to do it is .wireTap("log:mylog", new
> SimpleExpression("Processing ${header.ID}")
> It would be nice to have something more simple like :
> from("somewhere").to("humanlog:Processing ${header.ID}")
> or even:
> from("somewhere").hlog("Processing ${header.ID}") that allows the same
> functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
