Have you thought about SOAP headers? The first response could include a header giving a new URL for subsequent calls. On the client, a handler could check for the header and, if present, store the value as the endpoint address. You could probably work out how to then modify the Service object or update the URL in the message context for each call. I'm sure there is a way to handle this without modifying the stub or doing any TCP/IP programming.

So I'd have to write an implementation of some kind of plugable interface that Axis offers to change its functionality, and provide this along with the WSDL of our service so that the programmers on the client side can plug it in?

Any idea what interface would do this? I could just extend the Axis default implementation if I knew what it was.

Apache Soap follows the redirect, but it does it for every request instead of seeing that 301 means moved *permanently* and changing its endpoint accordingly! So it's getting a brand new server for each call, which obviously isn't logged in and initialized.

_____________________________________________________________________
This message has been checked for all known viruses. Virus scanning
powered by Messagelabs http://www.messagelabs.com For more information
e-mail : [EMAIL PROTECTED]

Re: Changing the endpoint by sending redirects from the server?

Reply via email to