Jesse Pangburn created CXF-4339:
-----------------------------------
Summary: Dispatch client fails to set soap action header
automatically unless WS-Addressing is enabled
Key: CXF-4339
URL: https://issues.apache.org/jira/browse/CXF-4339
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 2.5.3
Reporter: Jesse Pangburn
Priority: Minor
If I have a Dispatch client and I have WS-Addressing enabled on it and I send a
request then I see the following:
{quote}
Content-Type: application/soap+xml;
*action="urn:ihe:iti:2007:RegistryStoredQuery"*
Headers: \{Accept=[*/*]}
Payload: <soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";><soap:Header><Action
xmlns="http://www.w3.org/2005/08/addressing";>urn:ihe:iti:2007:RegistryStoredQuery</Action>
{quote}
But when I just disable WS-Addressing then the content-type header changes to
the following:
{quote}
Content-Type: application/soap+xml; charset=UTF-8
{quote}
There's no action attribute any more. Manually setting the soap action uri on
the dispatch object puts it back:
{code}
disp.getRequestContext().put(Dispatch.SOAPACTION_URI_PROPERTY, soapAction);
{code}
So there's a workaround possible (where your dispatch use case can accommodate
it) but the problem is that CXF shouldn't require WS-Addressing enabled to set
the Content-Type header's action attribute automatically.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
