[
https://issues.apache.org/jira/browse/CXF-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090826#comment-13090826
]
Willem Jiang commented on CXF-3720:
-----------------------------------
According to SOAP/JMS specification, the SOAPJMS_soapAction header is optional.
And if using SOAP 1.2 binding, we need to check this property matches the one
within the content-type.
{code}
[Definition: If using SOAP 1.2, and the contentType property has an action
parameter, that parameter value is compared with the SOAPJMS_soapAction value.
A fault MUST be generated with fault subcode mismatchedSoapAction if the SOAP
1.2 action does not match the SOAPJMS_soapAction value.†]
{code}
> SOAP over JMS miss SOAPJMS_soapAction property
> ----------------------------------------------
>
> Key: CXF-3720
> URL: https://issues.apache.org/jira/browse/CXF-3720
> Project: CXF
> Issue Type: Improvement
> Components: Soap Binding
> Affects Versions: 2.4.1
> Environment: Windows Server 2008 R2
> Reporter: Jorge Flores
> Assignee: Freeman Fang
>
> I have created a service consumer using the CXF JMSConfigFeature. I notice
> the SOAP action in the generated request message is included in the JMS
> custom property SOAPJMS_contentType. For example,
> Properties={
> "SOAPJMS_isFault"={boolean:false}
> "SOAPJMS_contentType"={string:'application/soap+xml; action="sayHello";
> charset=UTF-8'}
> "SOAPJMS_bindingVersion"={string:'1.0'}}
> Is there any reason why the header property 'SOAPJMS_soapAction' is not
> included in the CXF SOAP/JMS implementation?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
