We are currently working on a Web Services client program which sits within WebSphere as a number of EJB's and makes WebService calls to the outside world.
In order to create and make the WebService call we are trying to use a combination of JWSDP 1.4 and Axis 1.2. The reason for this is that we need some of the more advanced facilities of both of the solutions. So basically we use JWSDP 1.4 for everything, except for the Web Service transport itself, which we use Axis for.
The solution works perfectly well under normal circumstances, however if we configure an http proxy (using the JVM params http.proxyHost and proxyPort) the whole thing starts failing. The reason for this seems to be that Axis is making an invalid request to the HTTP Proxy, as it returns "Invalid Http Header".
I've tried various different HTTP proxies so I'm pretty sure that they aren't at fault. I think the problem is that Axis is omitting part of the URL when it makes the Web Service request. If I use Axis's TCP Monitor as my proxy, the invalid call looks something like:
Where as a normal request just using URL Connection looks like:
My guess is that the omitting the machine section of the URL for some reason, but why I don't know! I've looked through the Log4j output that Axis throws out, and all looks well until the actual call is made - I can see further up the log that it has identified the machine correctly, so at some point it did know!
My question is, has anyone else encountered this problem. Alternatively, has anyone tried to mix JWSDP 1.4 and Axis - if so what combination of libraries did you use, as that seems to be the key to the problem.
Thanks in advance for any help