cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Puli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5738) given soap action does not match any operation
Date Mon, 09 Mar 2015 15:32:39 GMT

    [ https://issues.apache.org/jira/browse/CXF-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353113#comment-14353113
] 

Suresh Puli commented on CXF-5738:
----------------------------------

We are facing the same issue. If we run the soap request form SOAP UI, the response is returned,
but if we hit the web service from 3rd party environment (actual web service consumer's machine),
the following error is returned.

We user Service Mix 5.3.0 & the request is thru Camel Route.

09:39:02,752 | WARN  | tp553450599-1646 | PhaseInterceptorChain            | 135 - org.apache.cxf.cxf-api
- 2.7.11 | Interceptor for {WISDL URL.wsdl}XXXAPIService#{WSDL URL.wsdl}GetBCUserProfile has
thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: The given SOAPAction /getBCUserProfile does not match an
operation.

Thanks.

> given soap action does not match any operation
> ----------------------------------------------
>
>                 Key: CXF-5738
>                 URL: https://issues.apache.org/jira/browse/CXF-5738
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.7.11
>            Reporter: Nicola
>
> I'm generating a service from an existing wsdl (http://195.250.34.59/temp/original.wsdl),
after creating the service the cxf generated wsdl has some small difference from the original
one (http://195.250.34.59/temp/cxf_generated.wsdl), 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="http://test.example.com//updateList"/>
> 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
(v6.3.4#6332)

Mime
View raw message