Cedric, No doubt it is confusing. I admit it is an odd requirement.
The WS response has to contain the URL that was used to access the WS. This is a requirement of the XML Schema that defines the WS response payload. I have no control over this. So when the WS call comes in the Axis-based call dispatcher invokes some of the business objects that are shared by the Struts app. The business objects eventually create the WS response DOM. One of the attributes has to be the URL that was used to reach the WS. So if at startup my Struts app can figure out the URL it can configure the business objects with the SOAP URL and then the SOAP dispatcher can pick up that value to throw into the response DOM. Hope that makes sense. --Marty --- Cedric Levieux <[EMAIL PROTECTED]> wrote: > > My Struts app contains an Axis-based SOAP service. The Struts app > > initializes the call dispatcher for the SOAP service. This dispatcher > > needs to know the URL of itself. This is a requirement of the > semantics > > of the SOAP service (outside of my control). So a Listener or a Plug > In > > appear to be the only way to try to determine the URL before the SOAP > > service is open for business. > > I don't understand this point in fact, cause in ones of my working > struts > applications there are some > axis-soap web services and I didn't need to give my url path to > axis-soap. > > So i'm very confuse in fact .. > > Cedric > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
