Hello, Looks like there's more than 1 David on this list. I'm the one who originally asked the question that you gave responses to. I guess all David's think alike and ask the same startup questions... ;-)
Anyway, from the fogginess so far this is what I can conjure up as a make pretend example that may be something similar to what you're trying to do: You have a user application that you are distributing that is sending messages to a known server for some reason. Let's make pretend it's for licensing checks. That's all good and fair and there's no issue with your application sending the soap request to your known server. Just the same, it's likely not a problem for your server to figure out where the request came from if that is needed for the protocol (the receiver of the initial message). It's the callback that you have a problem with and it sounds like it's for a reason... It doesn't make sense to assume that the web service installed on the client inside some network will be reachable from the external network. If this is what you're doing, configuration (having the client app user set the URL) is the only way to set it up because they (the client) will likely need to open up some incoming requests that they normally would not allow through their firewalls anyway. Not to mention whatever you grab would be the "internal" ip addresses. If your server grabs the ip from the request, it is likely to a proxy somewhere and not to your app. I think the answer here would be configuration is the only way in the scenario above. The question is, do you really need the call backs for what you're really doing? In the licensing example above, you likely only need to send the request to the public server. The public server can check and respond if the license is valid. There's no need for it to send you a request later. Again, just some thoughts to help you think through what you're doing, hopefully it helps you figure out the right course of action. Regards...djsuaerz -----Original Message----- From: Martin Wegner [mailto:[EMAIL PROTECTED] Sent: Thursday, January 27, 2005 11:17 PM To: Struts Users Mailing List Subject: RE: PlugIn and the base URL David, Also, as I said early the Axis architecture is such that it does not provide any of the information related to the HTTP layer beneath SOAP. The only think you know is that your dispatcher gets called. So my problem may be considered a limitation in Axis. --Marty > 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
