[Josh Korn]

I’m using a neat tool called Fiddler2 (www.fiddlertool.com) to examine packets exchanged during web service invocation.

The actual web service is built with .NET. For convenience’s sake, it helps to debug that using the ASP.NET Development Web server (which randomly assigns port numbers and is visible only on the local machine).

One of the common techniques used to convince Fiddler2 to monitor local conversations is for the client to use the fully qualified name “localhost.” (that’s localhost-period) instead of just “localhost” (no period). So “http://localhost.:<someport>” gets captured while “http://localhost:<someport>&#8221; doesn’t.

The generated web service client handles this as you’d expect — properly. When you set the URL to “http://localhost.:<port>…”, you get a conversation that Fiddler captures.

But for whatever reason, the Web Services Explorer (which, btw, I loved at first sight) parses out the period and connects to “http://localhost:<port>&#8221;, which of course makes the whole thing invisible to Fiddler2 … 8-(

Any chance of fixing this?

Thx
Josh

[Loyal Water]

Josh,
Fiddler is not certified to run with MyEclipse but I’ll make a note of this and take this to the dev team.

[Author]

Posts