CXF doesn't set the SOAPAction header in Fuse 6.3
Issue
- The issue, CXF-6732 removed the below codes, if condition from the SoapPreProtocolOutInterceptor
class and this is causing the
SOAPAction` header to an "" (empty String). - The reason for this seems to be that
Dispatch
client instances seem to include multipleSOAPAction
headers in the PROTOCOL while its first invocation, so that check is removed.
However, this is causing the normal camel-cxf route with PAYLOAD data format to not set the SOAPHeader.
This is the difference,
Fuse 6.2:
if (!reqHeaders.containsKey(SoapBindingConstants.SOAP_ACTION))
{ reqHeaders.put(SoapBindingConstants.SOAP_ACTION, Collections.singletonList(action)); }
Fuse 6.3:
reqHeaders.put(SoapBindingConstants.SOAP_ACTION, Collections.singletonList(action));
Environment
- Red Hat JBoss Fuse
- 6.3.x
- Camel-CXF component
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.