I asked this over on the oracle forum and did not get any responses. Maybe someone here can help out.
I have a project we will call Proxy, this project connects to a remote webservice over SSL, sends a SOAP query and then gets a SOAP response back. Proxy connects to the webservice and receives the correct response from the webservice.
Then I went ahead and created a new JAX-WS webservice we will call ContactWS.
This ContactWS project gets called and creates a query that will run through the Proxy project.
The Proxy project has been packed into a JAR and added as a library to the ContactWS project.
ContactWS gets loaded to a Web Logic 10.3.3 server and can receive requests.
When I send data to ContactWS to query through Proxy the trouble begins.
When Proxy logs into the remote webservice to query data, the login process fails. This is the same Proxy project that connects and query's data perfectly fine when not running from ContactWS.
I thought that ContactWS was not using my trustStore and keyStore properly - but I am fairly sure it does ( not 100% )
I set the trustStore and keyStore locations and password using System.setProperty(..., ...); in the Proxy project.
I have examined the SOAP packets and they are exactly how they need to be. And the SOAP packets from ContactWS match the ones from the Proxy project.
The error I get is from the company's proxy that funnels all traffic to the remote webservice. It is a "Policy Falsified" SOAP response that contains no more detail than that.
I can provide any finer details as needed, please ask, as I am unsure of what errors/logs are important.
Thank you for your time.
Here is the stack trace
incandescent light gives off an efficient form of heat. You must be THIS smart to ride this ride. Tiny ad: