Yes, those two lines of code are all you need on the client
side to support SSL. Don't forget to change your URL to
https (not http).
 
I had the same socket error just the other day. I was connecting
to the server using SSL on a non-standard port (ie not 443)
but the server was not configured properly. My server is
Apache  so I can't offer direct help on the server side, but
I did most of my debugging by accessing the SOAP admin client
via SSL in a browser (https://localhost/soap). Hope this helps.
 
 
Eric
 
-----Original Message-----
From: Naveen Kulkarni [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 30, 2001 2:57 AM
To: [EMAIL PROTECTED]
Subject: SSL & SOAP: Error Opening socket: null

 
Hi,
   My java Client for a .Net WebService using SSL throws a error Caught SOAPException (SOAP-ENV:Client): Error opening socket: null  WHY ?
I am using a java client to use a .Net WebService (on IIS 5.0) which uses SSL for its data security and Client authorization is not required, now after reading articles on how to use SSL with SOAP using JSSE, I could gather that it is sufficient for me to include this piece of code:
 
<code>
   System.setProperty( "java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol" );
   Security.addProvider( new com.sun.net.ssl.internal.ssl.Provider() );
</code>
 
After I included the above code, complied and executed it gave the error:
Caught SOAPException (SOAP-ENV:Client): Error opening socket: null 

Can any one please explain me why is this causing problem, am I missing anything or do I have to add more code to handle sockets etc?


TIA,
Naveen


Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com

Reply via email to