[
https://issues.apache.org/jira/browse/CAMEL-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984259#action_12984259
]
Hadrian Zbarcea commented on CAMEL-3566:
----------------------------------------
@james, I have no issue with configuring things to work as they wish. We
configure a bunch of stuff in camel.
However, you know this better than anybody, camel is about simplifying
integration. That's why camel has a brilliant way of using convention over
configuration to achieve that. Thanks in most part to you!
In this particular way, I personally see no value in extra configuration to not
warn of something we should not warn in the first place. It looks like the
thing we need to clarify is if that WARN should really be a warn or not. Let
alone that committing patches while there are outstanding issues to resolve is
not exactly community friendly.
> camel-jms - Add option logWarnWhenReplyToIsDiscarded to disable WARN log if
> JMSReplyTo is being discarded
> ---------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3566
> URL: https://issues.apache.org/jira/browse/CAMEL-3566
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 2.5.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
>
> If you dont care about an InOnly MEP exchange which uses an jms endpoint that
> has a replyTo set, then it woud log that at WARN that the reply to is being
> discarded. This happens at WARN level. Some people may just want to ignore
> this, and thus we need a {{logWarnWhenReplyToIsDiscarded}} option they can
> set to false.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
