I was looking to do exactly what you describe, and your information was very valuable, thanks. One difference is that I didn’t need to use the Dispatch stuff you described – it was enough for me to get the JAX-WS request context and set the factory as my customize factory like so:

( (BindingProvider) port ).getRequestContext().put(
“com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory”, factory);

Thanks,
Bill

Sorry to disappoint you, but I don’t know anything about this problem… it sounds like a really serious bug on the API, but anyway, I strongly recommend you to use this version only to do testing, not in the real environment. So, you really should try putting this on an application server or anything like that if you want to move this to production, OK?

Once again, sorry.

Thank you for following up on this. I was able to resolve the problem last week. You are absolutely right. It was because the path for the trust store was not correct. After that was fixed, I was able to get the SSL handshake to work.

I did run into another problem, however. It seems like after soap operation calls from the client are returned from my web service server, the socket is kept open. For some existing client programs, they expect to have the socket closed in order to return from their read operation.

The web service is published using Sun’s built-in HttpServer package, and the Endpoint class. Is there a way to force the server to close the socket connection after it returns a soap call? I tried setting the system property http.keepAlive to false to no avail.

Currently I have a way around this problem, but it’s not very elegant. Essentially I get the HttpHandler object from the HttpContext after it’s been created by the Endpoint.publish operation. And I call its handle() method from another HttpHandler class I wrote, which follows it up by sending a HttpHeader with “Connection” set to “close”. Something like this:

HttpServer server = HttpServer.create(myInetSocketAddress, 5);
HttpContext context = server.createContext(mySoapPath);
Endpoint endpoint = Endpoint.create(mySoapImpl);
endpoint.publish(context);
MyHandler handler = new MyHandler(context.getHandler());
server.removeContext(mySoapPath);
server.createContext(mySoapPath, handler);
server.start();

private class MyHandler implements HttpHandler {
private HttpHandler h;
public MyHandler(HttpHandler in) {
h = in;
}
public void handle(HttpExchange t) throws IOException {
h.handle(t);
Headers closing = t.getResponseHeaders();
closing.set(“Connection”, “close”);
t.sendResponseHeaders(200, 0);
t.close();
}
}

It works for my current needs, but it just seems like there’s got to be a better way…

Thanks again

Regards,
Alexandre

I wrote a web service server using JAX-WS just like this here. But I am having trouble with the client program that would access the soap port via HTTPS and SSL. Here is what my client code looks like:

System.setProperty(“javax.net.ssl.trustStore”, “certificate.p12″);
System.setProperty(“javax.net.ssl.trustStorePassword”, “password”);
System.setProperty(“javax.net.ssl.trustStoreType”, “PKCS12″);
System.setProperty(“javax.net.ssl.TrustManagerFactory.algorithm”, “SunX509″);

System.setProperty(“javax.net.ssl.keyStore”, “certificate.p12″);
System.setProperty(“javax.net.ssl.keyStorePassword”, “password”);
System.setProperty(“javax.net.ssl.keyStoreType”, “PKCS12″);
System.setProperty(“javax.net.ssl.KeyManagerFactory.algorithm”, “SunX509″);

URL theURL = new URL(“https://192.28.1.1:8888/test/TestSoap?wsdl”);
QName theQName = new QName(“http://TestSoap.test”, “TestSoapPortType”);
Service theService = Service.create(theURL, theQName);
TestSoapPortType handle = theService.getPort(TestSoapPortType.class);

handle.soapMethod(null);

But it’s throwing an exception at the Service.create invocation:
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Can you please help?

[]´s

@Resource
private WebServiceContext context;

And the other one is as shown in “How to intercept web services ingoing/outgoing messages.

Once again, congratulations!

MessageContext context = wsContext.getMessageContext();
HttpsExchange hse = (HttpsExchange)wsContext.getMessageContext().get(“com.sun.xml.internal.ws.http.exchange”);
hse.getSSLSession().getPeerPrincipal().getName();

Guess I was looking in the wrong place