davsclaus commented on code in PR #30232:
URL: https://github.com/apache/camel/pull/30232#discussion_r4599342543
##########
components/camel-cxf/camel-cxf-soap/src/main/java/org/apache/camel/component/cxf/jaxws/CxfProducer.java:
##########
@@ -483,16 +506,46 @@ private BindingOperationInfo
getBindingOperationInfo(Exchange ex) {
LOG.trace("Operation qname = {}", qname);
- answer =
client.getEndpoint().getEndpointInfo().getBinding().getOperation(qname);
+ answer = binding.getOperation(qname);
if (answer == null) {
throw new IllegalArgumentException(
"Can't find the BindingOperationInfo with operation
name " + qname
- + ". Please check the
message headers of operationName and operationNamespace.");
+ + ". Please check the " +
CxfConstants.OPERATION_NAME + " and "
+ +
CxfConstants.OPERATION_NAMESPACE
+ + " headers, or the
defaultOperationName and defaultOperationNamespace"
+ + " options. The operations
of the service are "
+ + operationNames(binding));
}
}
return answer;
}
+ private void warnOnFormerOperationHeaders(Exchange ex) {
+ if (formerOperationHeadersWarned) {
+ return;
Review Comment:
Same point as the earlier thread, which @Croway answered there: a new
producer is created each time the route starts (`SendProcessor.doStart`), so
after fixing `operationName` a restarted or reloaded route logs the
`operationNamespace` case, and the WARN text already names both former headers.
Keeping the single flag; resolving.
_Claude Code on behalf of davsclaus_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]