We've added endpointURLs to each service definition
<endpointURL>https://url.server.com/axis/services/api/myClass</endpointURL>
This causes axis to disregard the incoming url when generating WSDLs.
--Barry Shah, Soniya M. wrote:
We use Apache web server and weblogic with the same configuration (axis deployed as servlet in weblogic inside the firewall) using http tunneling. Weblogic has a patch for apache web server to do this. We just followed the configuration details provided by Weblogic and it is working.
Soniya
-----Original Message-----
From: Linus Kamb [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 2:16 PM
To: [EMAIL PROTECTED]
Subject: apache, axis, proxypasses, and firewalls.
Hi.
In my development environment, I want to run tomcat/axis on my local machine
behind our firewall and have Apache running on a machine outside the firewall
configured with a ProxyPass to pass the approproate requests through to my machine.
The problem is that the AxisServlet gets the server name out of the HTTP
Request and uses that to generate URLs (as in for the ?wsdl queries from the list
services page.) The server name is, of course, my local machine name, which is not
directly accessible from outside the firewall.
Is there some tomcat or axis configuration setting that might handle this
situation, or is this just a bad way to do this?
Thanks, Linus
