You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2019/05/03 14:25:00 UTC

[jira] [Updated] (CXF-7885) SOAP Action ignored by CXF JMS webservice method invoker

     [ https://issues.apache.org/jira/browse/CXF-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh updated CXF-7885:
-------------------------------------
    Fix Version/s: 3.3.2
                   3.2.9

> SOAP Action ignored by CXF JMS webservice method invoker
> --------------------------------------------------------
>
>                 Key: CXF-7885
>                 URL: https://issues.apache.org/jira/browse/CXF-7885
>             Project: CXF
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 3.2.6
>            Reporter: Robert
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>             Fix For: 3.2.9, 3.3.2
>
>
> I'm using CXF 3.2.6 and have a HTTP SOAP webservice that uses a 
> JaxWsProxyFactoryBean to call a (one-way) webservice over SOAP JMS. The 
> wsdl for this webservice has non-unque body parts; it is not 
> WSI-BasicProfile compliant, therefore the SOAP Action is important to 
> determine which method of the target webservice must be called. 
> I can see that CXF sets the SOAP Action header "SOAPJMS_soapAction", and 
> this is received by the CXF JMS listener. However it then uses the 
> namespace and local part name to determine which method should be called, 
> instead of the SOAP Action.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)