cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akitoshi Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-5738) given soap action does not match any operation
Date Tue, 01 Dec 2015 17:19:11 GMT


Akitoshi Yoshida commented on CXF-5738:

as far as I remember, this stricter check was added in cxf to prevent certain attacks.
you can also disable this check by activating property allowNonMatchingToDefaultSoapAction
at the endpoint (see CXF-5738)

this ticket was not attended for a long time and i don't know if there is some issue left
to address.
please let me know if we can close this ticket.

regards, aki

> given soap action does not match any operation
> ----------------------------------------------
>                 Key: CXF-5738
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.7.11
>            Reporter: Nicola
> I'm generating a service from an existing wsdl (,
after creating the service the cxf generated wsdl has some small difference from the original
one (, if I create client methods, using for
example soapui, from the cxf generated wsdl all is fine but if I use the original wsdl the
requests fail with the error:
> "the given soapaction does not match an operation"
> the problem is the SOAPAction http header:
> cxf expects no SOAPAction header or an empty one, if you look at the wsdl generated by
cxf you can see a section not present in the original wsdl that define an empty soap action:
> <soap:operation soapAction="" style="document"/>
> after this section there is also the original one that define:
> <soap:operation soapAction=""/>
> I defined an interceptor that remove the SOAPAction http header if present and this workaround
the problem
> cxf should not modify the original wsdl or however should accept calls generated using
the provided wsdl

This message was sent by Atlassian JIRA

View raw message