camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Confusing cxf log messages after upgrading to 2.14.0
Date Thu, 25 Sep 2014 14:12:33 GMT

Yeah INFO logging per message is a bad idea. Feel free to log a JIRA
so we can tone it down. And also if you get that option set, then
there is a bug in that code check.

Maybe there is a case sensitive issue with DefaultXXX vs defaultXXX

On Thu, Sep 25, 2014 at 2:56 PM, Preben.Asmussen <> wrote:
> After upgrade the CXF producer info logs like
> CxfProducer                    INFO  CxfProducer cannot find the
> operationName from message header, try to use the defaultOperationName
> This is due to change in in
> The defaultOperationName is actually set on my endpoint like
> cxf:bean:mybean?synchronous=true&amp;DefaultOperationName=MyDefaultOperationName
> The Info log statement i kind of misleading you to think something is
> broken.
> IMHO the log statment should be debug or trace at best, or even better see
> only log if the defaultOperationName is not present as a header or set as a
> endpoint DefaultOperationName option.
> Best,
> Preben
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Red Hat, Inc.
Twitter: davsclaus
Author of Camel in Action:

View raw message