Karin,
After further investigation, I'm afraid the situation is a good deal more
complicated than that. In summary:
This is a client-side problem: I have an applet trying to send SOAP
messages
I cannot know in advance what sort of environment the applet will find
itself in
Even if I _could_ read proxy information from the Java Plug-In (and that
in itself seems difficult), I get security exceptions when trying to
point Apache SOAP _at_ that proxy address (because it is not the address
the applet was served from)
I am not in a position to be able to modify security settings on client
machines
Of course, Java has proxy support built in, but it seems the problem stems
from the fact that Apache use their own SOAPHTTPConnection instead of the
JDK's URLConnection class. I am not sure why they do this, although
apparently it allows better error handling for them, but it doesn't
alleviate my security headaches.
Anyway, this doesn't seem possible using Apache SOAP - I'm currently
considering alternate implementations.
Many thanks,
Richard.
Karin Stadler
<karin.stadle To: [EMAIL PROTECTED]
[EMAIL PROTECTED]> cc:
Subject: Re: SOAP blocked by a firewall?!
22/05/2002 Isn't that the whole POINT of SOAP?
05:16 PM
Hello Richard,
it is a firewall problem! And you have to use the proxy to go through the
firewall and not to "break throught the proxy".
Now is the question if you have the http-request in the server-class or in
the client-class: Because you have to input different code in (depends on
server- or clientside) in the java-file. Look for them to:
http://xml.apache.org/soap/faq/faq_chawke.html#Q2_30
(But the example CATALINA_OPTS=..... , doesn't work for me, the other are
going well in my case)
Bye
Karin
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
