Given that I cannot control certain aspects of the legacy clients that take apart a provided URL and insist on calling it a certain way: GET https://my.webservice.com/services/myService
My question is a) How can I setup the server side (CXF handling I should be able to control) to do something other than throw the default error: org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown. b) How can I instead choose to always return something like a WSDL file when no binding operations are specified? I'm not asking how to make the client do it cause I do not control that, - Pulkit On Wed, Jan 8, 2014 at 9:41 PM, Freeman-2 [via CXF] < [email protected]> wrote: > Hi, > > The SOAP request should use POST, to GET the wsdl, use url like > https://my.webservice.com/services/myService?wsdl > －－－－－－－－－－－－－ > Freeman(Yue) Fang > > Red Hat, Inc. > FuseSource is now part of Red Hat > > > > On 2014-1-9, at 上午5:07, pulkitsinghal wrote: > > > Consumers of my webservice, validate its certificate by pinging the > endpoint: > > `https://my.webservice.com/services/myService` but they are unable to > do so > > because they get a 500 http error code generated by the CXF component of > the > > server: > > > > WARNING: Interceptor for {http://my.webservice.com/}MyWebService has > > thrown exception, unwinding now > > org.apache.cxf.interceptor.Fault: No binding operation info while > > invoking unknown method with params unknown. > > > > > org.apache.cxf.binding.soap.interceptor.Soap12FaultOutInterceptor$Soap12FaultOutInterceptorInternal > > > handleMessage > > ... > > INFO: class > > > org.apache.cxf.binding.soap.interceptor.Soap12FaultOutInterceptor$Soap12FaultOutInterceptorInternalapplication/soap+xml > > > at > > > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1686) > > > > > Now the webservice itself works fine when its invoked by SOAP clients at > > `https://my.webservice.com/services/myService` ... its just that a > simple > > GET operation which is trying to figure out the certificate situation, > > screws up. > > > > Is there some way to configure this endpoint to simply send back 200 OK > or > > the WSDL file when its hit up with a simple GET? I'm using CXF version > 2.7.7 > > right now. > > > > > > > > -- > > View this message in context: > http://cxf.547215.n5.nabble.com/How-to-setup-a-default-response-when-no-bindings-are-specified-by-request-tp5738403.html > > Sent from the cxf-user mailing list archive at Nabble.com. > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://cxf.547215.n5.nabble.com/How-to-setup-a-default-response-when-no-bindings-are-specified-by-request-tp5738403p5738406.html > To unsubscribe from How to setup a default response when no bindings are > specified by request, click > here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5738403&code=cHVsa2l0c2luZ2hhbEBnbWFpbC5jb218NTczODQwM3wxOTg5MzI4Mzc0> > . > NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://cxf.547215.n5.nabble.com/How-to-setup-a-default-response-when-no-bindings-are-specified-by-request-tp5738403p5738470.html Sent from the cxf-user mailing list archive at Nabble.com.
