I’m having an interesting compatibility issue between a WCF client and a Java web service. In short I’ve found that the way the header is generated is causing the problem – the ActivityId and Action elements in the header as well as what WCF is doing with the namespace of the custom header is causing issues. I’ve successfully consumed the WSDL with wsdl.exe, but WCF seems to be manipulating the header in a way that the Java web service doesn’t like. Is there any way I can set up the bindings for the WCF client to not send the ActivityId and Action elements?
I’m having an interesting compatibility issue between a WCF client and a Java web
Share
Do you have tracing turned on in the client? I think that is what is adding the activity ID as its trying to flow the tracing activity to the service for end to end tracing. Turn off the activity tracing flag and it should go – see my comment for the action header