cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <>
Subject [jira] [Commented] (CXF-3720) SOAP over JMS miss SOAPJMS_soapAction property when use soap12
Date Thu, 25 Aug 2011 10:24:29 GMT


Freeman Fang commented on CXF-3720:

Per the spec
[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

But current implementation miss SOAPJMS_soapAction when use SOAP1.2(it has SOAPJMS_soapAction
when use SOAP1.1 on the contrary), so can't compare the soapAction with the action in contentType
at all, IMO this is a bug, so will change issue TYPE accordingly.


> SOAP over JMS miss SOAPJMS_soapAction property when use soap12
> --------------------------------------------------------------
>                 Key: CXF-3720
>                 URL:
>             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:


View raw message