Hi Julie,
I'm not sure if this can help you.
The product SoapScope does something similar, it registers a HttpProxy in
order to intercept all http messages.
<system.net>
<!-- this allows the routing for the test tool support... -->
<defaultProxy>
<proxy proxyaddress="http://localhost:5049" bypassonlocal="false" />
<module type="Mindreef.Net.WebProxyEx, MrTools, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=90f6595dbbe888f3" />
</defaultProxy>
</system.net>
As you can see, the proxy is specified declaratively in the config file. I
don't know a way of doing the same in WSE.
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com
> In my client application, I can change the destination of a proxy to point
> to a sniffer to read the binary coming over the wire and then have it send
[quoted text clipped - 19 lines]
>
> julie
Julie Lerman - 22 Nov 2005 02:11 GMT
thanks - perhaps I'll try it out with SoapScope. It's mostly curiousity at
this point since I am only using the TCP Trace for demos but really it's
just not right that I have to compile it into the client app. Then i can't
easily turn it on and off if I really wanted to in production.
This can be done in WCF of course ;-), but I was curious about it for WSE.
If you are curious Pablo, check out this blog post and the comment from
Christian Weyer who loves to tease me about WSE now that Indigo is so close.
(http://www.thedatafarm.com/blog/CommentView.aspx?guid=2e959b4e-68a0-4819-b133-74
0e851406d1
julie
> Hi Julie,
> I'm not sure if this can help you.
[quoted text clipped - 50 lines]
>>
>> julie