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

[tony . q . weddle]

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.

Tony

"Nige White" <[EMAIL PROTECTED]> wrote on 02/12/2004 14:22:51:

> Nige White wrote:
>
> > Will the Axis HTTP client classes follow redirects?
> >
> No it doesn't! It just throws a "(301)Moved Permanently" error.
>
> This means standard, generated Axis clients won't be able to use our
> Soap server. The programmers of the client will have to modify the
> BindingStub class do the extra step of talking straight TCP/IP on a
> known port to the host to access my manager service which spawns a new
> server process, and sends back the port on which that server is
> listening, and creating the endpoint URL from that. BAH! :-(
>
> _____________________________________________________________________
> 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]
>
>
>