On Wed, Jul 30, 2008 at 7:01 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > I think the issue you might be seeing right now is that we currently are > unable to obtain the WSDL via https. That is something we've been > discussing a bit on the Dev list. If you create the client proxy with > a locally cached copy of the wsd, you should be able to use it to > communicate with the server if the http-conduit TLS stuff is setup properly. > > Dan > >
Sorry for my late reaction to you response and thank you for your answer. I had another round with CXF over HTTPS and unfortunately I'm still loosing. If I understand your response correctly, I should not user spring configuration to create a web service client. Instead, I should create it through the Java code, right? Maybe one more thing: while connecting to the web service provider I receive "org.apache.cxf.binding.soap.SoapFault: SOAPEXCEPTION" with no detailed description. I've done some debuging and found out that the real problem comes from org.apache.cxf.binding.soap.saaj.SAAJOutInterceptor$SAAJOutEndingInterceptor and "java.net.SocketException: Software caused connection abort: recv failed" Do you have any ideas what might cause the problem? One more question: in the http:conduit configuration there is no client certificate's alias/name statement. What will happen if client authentication is turned on? Cheers! Łukasz
