[
https://issues.apache.org/jira/browse/CXF-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502206#comment-15502206
]
Freeman Fang commented on CXF-6732:
-----------------------------------
Hi David,
IMO each invocation request should carry correct SOAPAction, and your
suggestion won't work in the case that if the SOAPAction is intended to be
reset as ""(empty string). So to me this is something need be fixed in
camel-cxf to always carry correct SOAPAction for each request(In Apache Camel
project). Would you please create a jira ticket in Apache Camel and append a
reproducer there?
Thanks
Freeman
> Allow SOAPAction to be overwritten via RequestContext property
> --------------------------------------------------------------
>
> Key: CXF-6732
> URL: https://issues.apache.org/jira/browse/CXF-6732
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 2.7.18, 3.2.0
> Reporter: Tomohisa Igarashi
> Assignee: Freeman Fang
> Fix For: 3.1.5, 3.0.8, 3.2.0
>
>
> SoapPreProtocolOutInterceptor sets SOAPAction into PROTOCOL_HEADERS only when
> it's not yet set here:
> https://fisheye6.atlassian.com/browse/cxf/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/SoapPreProtocolOutInterceptor.java?hb=true#to121
> If user reuses the client like Dispatch instance, the PROTOCOL_HEADERS is
> carried over multiple invocations including SOAPAction specified for the
> first invocation, thus the "javax.xml.ws.soap.http.soapaction.uri" property
> is ignored afterward. IMO the "javax.xml.ws.soap.http.soapaction.uri"
> standard property should precede existing SOAPAction in PROTOCOL_HEADERS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
