You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/07 14:32:58 UTC
[jira] [Commented] (CAMEL-10449) Set CXF SoapAction header
correctly
[ https://issues.apache.org/jira/browse/CAMEL-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644333#comment-15644333 ]
ASF GitHub Bot commented on CAMEL-10449:
----------------------------------------
GitHub user johnpoth opened a pull request:
https://github.com/apache/camel/pull/1254
CAMEL-10449 - Set CXF SoapAction header correctly
https://issues.apache.org/jira/browse/CAMEL-10449
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/johnpoth/camel CAMEL-10449
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1254.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1254
----
commit 3d1541d100a95c3fba12e901b1272489f0e5f30b
Author: jpoth <po...@gmail.com>
Date: 2016-11-07T14:30:54Z
CAMEL-10449 - Set CXF SoapAction header correctly
----
> Set CXF SoapAction header correctly
> -----------------------------------
>
> Key: CAMEL-10449
> URL: https://issues.apache.org/jira/browse/CAMEL-10449
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.18.0
> Reporter: John Poth
> Assignee: John Poth
>
> As of [CXF-6732|https://issues.apache.org/jira/browse/CXF-6732], CXF will by default always [set|https://github.com/apache/cxf/blob/master/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapPreProtocolOutInterceptor.java#L121] the SoapAction header with the value found at key SoapBindingConstants.SOAP_ACTION. See [comment|https://issues.apache.org/jira/browse/CXF-6732?focusedCommentId=15502206&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15502206] for more details. Workaround can be either adding a custom CXF OutInterceptor or use a different Camel/CXF binding.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)