After upgrade the CXF producer info logs like
CxfProducerINFO 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
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
Yep, perhaps try setting it as a cxf:property / in your bean...
*Raúl Kripalani*
Apache Camel PMC Member Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On
Hi
created https://issues.apache.org/jira/browse/CAMEL-7863
I actually still works as expected when setting the DefaultOperationName as
an endpoint option, so there is no new bug.
But to avoid the info logging pr. message you currently have to set a header
'operationName' too.
Best,
Preben
The info log is try to tell the user that the CxfProducer is looking up the
operation name.
I’m OK to change the log level to DEBUG, I will update the Java doc and Wiki
page for operation name look up processing.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog:
