[
https://issues.apache.org/jira/browse/CXF-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090834#comment-13090834
]
Freeman Fang edited comment on CXF-3720 at 8/25/11 7:11 AM:
------------------------------------------------------------
Yeah, actually we have SOAPJMS_soapAction property correctly when use soap11,
but only miss it when use soap12.
And currently implementation doesn't throw missingSoapAction fault(though this
is an optional fault), I'll add it also.
Freeman
was (Author: ffang):
Yeah, actually we have SOAPJMS_soapAction property correctly when use
soap11, but only miss it when use soap12.
Freeman
> 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
