Hi, I see that generated WSDL contains two bindings and two services(WSTEST, WSTESTService) using different bindings. Do you see any reason of that? Could you post your code configuration and used to create a service?
Regards, Andrei. > -----Original Message----- > From: Mailing List SVR [mailto:[email protected]] > Sent: Donnerstag, 8. Mai 2014 12:46 > To: [email protected] > Subject: the given soapaction does not match an operation, cxf bug? > > Hi, > > 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:operationsoapAction=""style="document"/> > > after this section there is also the original one that define: > > <soap:operationsoapAction="http://test.example.com//updateList"/> > > I defined an interceptor that remove the SOAPAction http header if present and > this workaround what seems a cxf bug to me. > > Obviously if someone give you a wsdl the same wsdl is used to generate the > client methods ... > > What do you think about? Why cxf modify the original wsdl used to generate > java code? Is this a cxf bug or am I missing something? > > thanks > Nicola > > P.S. tested with both cxf 2.7.8 and 2.7.11
