Hi 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 <p...@dr.dk> 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 https://issues.apache.org/jira/browse/CAMEL-7503 > https://fisheye6.atlassian.com/changelog/camel-git?cs=75dfe61edc1d6f9e2837056189dea5f7e20f1090 > > The defaultOperationName is actually set on my endpoint like > cxf:bean:mybean?synchronous=true&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: > http://camel.465427.n5.nabble.com/Confusing-cxf-log-messages-after-upgrading-to-2-14-0-tp5757014.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
