Alter target service url in SoapExtension

[Paul]

Hello,

I am trying to write a client side SoapExtension to change the target web
service url based on information from UDDI.
Does any one know how to do it? I tried to set the url in the
SoapHttpClientProtocol (SOAPClientMessage.Client), but it did not do
anything.
I know you could change the target url in client proxy class, but change
client proxy code is NOT an option.

Thanks,
Paul

[Marvin Smit]

Hi,

have you considered make your WebService a gateway? So, instead of
modifying the request from the client, accept it. Call the WS that was
needed based on your UDDI discovery and return the response to the
client?

Hope this helps,

Marvin Smit.
On Fri, 21 Oct 2005 11:35:06 -0700, "Paul"
<Pa**@discussions.microsoft.com> wrote:

Hello,

I am trying to write a client side SoapExtension to change the target web
service url based on information from UDDI.
Does any one know how to do it? I tried to set the url in the
SoapHttpClientProtocol (SOAPClientMessage.Client), but it did not do
anything.
I know you could change the target url in client proxy class, but change
client proxy code is NOT an option.

Thanks,
Paul

[Paul]

Hello,

One of the requirement I have is to NOT change existing client application
(no source code modification). So the idea way is to implement a
SoapExtension to do the UDDI lookup and then forward the request to the new
target. Unfortunately I could not get it to work.

It seems the communication "socket" between client and service is already
opened when the soap extension gets called. So any changes to the url is
ignored. Is there a work around for this?

Thanks,
Paul
"Marvin Smit" wrote:

Hi,

have you considered make your WebService a gateway? So, instead of
modifying the request from the client, accept it. Call the WS that was
needed based on your UDDI discovery and return the response to the
client?

Hope this helps,

Marvin Smit.
On Fri, 21 Oct 2005 11:35:06 -0700, "Paul"
<Pa**@discussions.microsoft.com> wrote:

Hello,

I am trying to write a client side SoapExtension to change the target web
service url based on information from UDDI.
Does any one know how to do it? I tried to set the url in the
SoapHttpClientProtocol (SOAPClientMessage.Client), but it did not do
anything.
I know you could change the target url in client proxy class, but change
client proxy code is NOT an option.

Thanks,
Paul

[Marvin Smit]

Hi,

Ahh, i thought you had control of the server recieving the call on the
original URL. Then you'de could do the "gateway" approach.

Modifying this on the client's stack (without the client noticing)
would be a serious security risc. (Who says you're the last to modify
the target URL?).

I have had no circumstance in which this functionality was required.

Marvin Smit.

On Tue, 25 Oct 2005 08:44:02 -0700, "Paul"
<Pa**@discussions.microsoft.com> wrote:

Hello,

One of the requirement I have is to NOT change existing client application
(no source code modification). So the idea way is to implement a
SoapExtension to do the UDDI lookup and then forward the request to the new
target. Unfortunately I could not get it to work.

It seems the communication "socket" between client and service is already
opened when the soap extension gets called. So any changes to the url is
ignored. Is there a work around for this?

Thanks,
Paul
"Marvin Smit" wrote:

Hi,

have you considered make your WebService a gateway? So, instead of
modifying the request from the client, accept it. Call the WS that was
needed based on your UDDI discovery and return the response to the
client?

Hope this helps,

Marvin Smit.
On Fri, 21 Oct 2005 11:35:06 -0700, "Paul"
<Pa**@discussions.microsoft.com> wrote:

>Hello,
>
>I am trying to write a client side SoapExtension to change the target web
>service url based on information from UDDI.
>Does any one know how to do it? I tried to set the url in the
>SoapHttpClientProtocol (SOAPClientMessage.Client), but it did not do
>anything.
>I know you could change the target url in client proxy class, but change
>client proxy code is NOT an option.
>
>Thanks,
>Paul