[
https://issues.apache.org/jira/browse/CXF-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390300#comment-14390300
]
Le Van Lang commented on CXF-2612:
----------------------------------
HI Christian,
Could you please help to check this issue on CXF version 3.0.4 ?
I also used interceptor to add custom "SoapAction" property to JMS header but
CXF replaced it by default standard name ("SOAPJMS_soapAction")
Thanks,
Lang
P/S:
I create an issue about this before seeing this issue log:
https://issues.apache.org/jira/browse/CXF-6326
> Interceptor to work around SoapAction bug in Tibco Business Works
> -----------------------------------------------------------------
>
> Key: CXF-2612
> URL: https://issues.apache.org/jira/browse/CXF-2612
> Project: CXF
> Issue Type: Improvement
> Components: Soap Binding
> Affects Versions: 2.2.5
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.2.6
>
>
> Tibco Business Works expects the soap action header to be spelled in
> CamelCase. By default CXF uses the SOAPAction header which is soap standard
> compliant.
> So we should add an interceptor that adds a header SoapAction for Tibco BW
> with the contents of the header of SOAPAction. This way people working with
> Tibco BW can simply add this interceptor to make CXF compatible with Tibco BW.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
