If the clients can be told by some other means what URL to use to access your service, and all know to ignore what's in the wsdl, then anything goes. If *any* client (existing now or in future) must figure it out from the wsdl, then the wsdl must contain a usable URL for the service, in the sense that Axis or some other WS engine is invoked at that URL and can determine the correct class and method to use on any web service call (using the URL or SOAPAction or body element name in a doc/lit invocation, or something custom). These are the "requirements" from a practical point of view.
Jeff ----- Original Message ----- From: "Sheptunov, Bogdan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 29, 2004 12:14 PM Subject: value of soap:address attribute Hello, I am trying to determine what the value of (wsdl)soap:address attribute should be, and to what extent that value is supposed to reflect the real URL at which the corresponding service is avaliable.
