This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
I have a SOAP implementation developed and tested OK with HTTP connections. I am using the low level api (not SOAP-RPC) whereby I get a URL connection and write the SOAP envelope to it. I have also been successfully getting the response SOAP Envelope (when using http). However, when I change the target URLs to HTTPs endpoints, I invariably get handshake error messages to the effect that there doesn't appear to be a trusted certificate available. The firewalls involved have had the appropriate holes poked in them and the security people at both sites have assured us that the appropriate certificates have been created. What steps can I take to address and fix this problem?
This may sound overly simplistic -- but you are using the SSLSocketFactory to get your secure socket, correct? Just checking.
Joined: Nov 02, 2000
Not directly using SSL Secure Sockets, but surely getting to the factory indirectly through instantiating a URL for the Https endpoint, getting a connection, getting an output stream from the connection, and writing to it. However, as of late, this approach is working ok even for Https endpoints. To fix the problem, I cleared all but one of the related .jar files from the classpath, recompiled, ran, and everything worked. (We must have had some conflicting functionality - the jar files we cleared out were from Oracle, Apache, BEA, IBM, SUN, etc. )