Marty,
If you want to make major assumptions such as a) the client will always use
port 80 AND b) the client will always use the same /whatever context name
even when mapping through a web server to your Java application server, then
this line in your plugIn.init() will solve your problems:
url = arg0.getServletContext().getResource("/");
I tried it using my default Tomcat setup which uses "localhost" and saw
"jndi:/localhost/myapp/". I then changed Tomcat's configuration to name my
host something else (and changed my Windows "hosts" file as required). The
"localhost" changed appropriately. This means the pattern of that resource,
at least on Tomcat 5.0.2X, is "jndi:/HOSTNAME/APPNAME/". That means you can
split it into http://HOSTNAME/APPNAME for your app-loading SOAP steps.
Again, the big IF requires the leap of faith for conditions a) and b) above.
How does that idea work for you?
Regards,
David, happy at finding a conditional answer that works on his one-tested
Java server.
-----Original Message-----
From: Martin Wegner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 26, 2005 3:57 PM
To: Struts Users Mailing List
Subject: RE: PlugIn and the base URL
David,
Right. I cannot guarantee that any human will hit the web server before
an SOAP based application contacts the WS. So I am still stuck with the
same problem: no access to a Request object until a human points their
browser at the container.
--Marty
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
