David, As I said in a previous message my Struts app has an Axis-based SOAP service. The business logic behind the WS needs to know a/the URL that can be used to access the WS. This is a requirement of the WS. This part can't be changed. It is part of the protocol of the answer sent back by the WS.
So the question becomes: if the web container, port number, IP address(es) and WAR file name can all cahnge, how does the Struts PlugIn figure out a/the URL to access the WS? As stated earlier, if a human were to log in then the Request object would contain all of the necessary info. But the PlugIn does not have a Request object. So the question becomes: what is the trick to get the PlugIn to generate a Request object? Clearly you could use something like HttpClient to make an HTTP call back to the main app, but how do you construct the URL at run time? You can't contact yourself unless you make at least a few assumptions. And I can't make those in this case. The other good answer was to force the user to supply the URL via an external file or via an installer. That is the solution I have adopted for the time being. --Marty --- "David G. Friedman" <[EMAIL PROTECTED]> wrote: > >>Martin Wegner wrote: > >>In have a Struts PlugIn that needs to determine the > >> URL for the containing web application > >> (http://localhost:8080/BlahBlahBlah/). > > Martin, since you seem firm on this issue, can we/I ask WHY you need > this > information in your webapp during initialization? What are you doing > that > you cannot set that information per request (HTTP/SOAP) in your output? > (Or > use relative URLS of some sort) Knowing WHY, perhaps someone on the list > can > suggest an alternate, yet equally effective, solution for the issue. > > Regards, > David > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
