Thanks again to everybody who is assisting...
The trace utility as far as i can tell is designed to reside on the "host"
of the webservice...
Is there a way to configure the utility to grab the request "before it
leaves"?
> Then the trace tool MSSoapT shipped with the Soap Toolkit [0] that Dilip
> mentioned or tcpTrace [1] should do just fine.
[quoted text clipped - 59 lines]
> accomplish
> > > > this?
PokerJoker - 29 Dec 2004 19:49 GMT
Nevermind... I changed the wsdl to send the request to localhost... then i
forwarded it using the trace utility to its final destination (our vendor).
Great little utility, thanks for the help guys!
> Thanks again to everybody who is assisting...
>
[quoted text clipped - 67 lines]
> > accomplish
> > > > > this?
Christoph Schittko [MVP] - 29 Dec 2004 19:50 GMT
The trace tools can run on any server, but you have to point your proxy
to the location/port where the tool is listening.
You should configure your proxy to dynamically pull the web service
location from the application's config file. Right click on the web
service node under Web References in the solution explorer and set the
URL Behavior to dynamic. Now rebuild your service consumer and you'll be
able to quickly configure the URL for the web service proxy to invoke.
HTH,
Christoph Schittko
MVP XML
http://weblogs.asp.net/cschittko
> -----Original Message-----
> From: PokerJoker [mailto:PokerJoker@discussions.microsoft.com]
[quoted text clipped - 20 lines]
> >
> > [0]
http://www.microsoft.com/downloads/details.aspx?FamilyId=C943C0DD-CEEC-4
> > 088-9753-86F052EC8450&displaylang=en
> > [1] http://www.pocketsoap.com
[quoted text clipped - 28 lines]
> > > >
> > > > [0]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/h
> > > > tml/frlrfsystemwebservicesprotocolssoapextensionclasstopic.asp
> > > > > -----Original Message-----
[quoted text clipped - 15 lines]
> > accomplish
> > > > > this?
Christoph Schittko [MVP] - 29 Dec 2004 19:50 GMT
The trace tools can run on any server, but you have to point your proxy
to the location/port where the tool is listening.
You should configure your proxy to dynamically pull the web service
location from the application's config file. Right click on the web
service node under Web References in the solution explorer and set the
URL Behavior to dynamic. Now rebuild your service consumer and you'll be
able to quickly configure the URL for the web service proxy to invoke.
HTH,
Christoph Schittko
MVP XML
http://weblogs.asp.net/cschittko
> -----Original Message-----
> From: PokerJoker [mailto:PokerJoker@discussions.microsoft.com]
[quoted text clipped - 20 lines]
> >
> > [0]
http://www.microsoft.com/downloads/details.aspx?FamilyId=C943C0DD-CEEC-4
> > 088-9753-86F052EC8450&displaylang=en
> > [1] http://www.pocketsoap.com
[quoted text clipped - 28 lines]
> > > >
> > > > [0]
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/h
> > > > tml/frlrfsystemwebservicesprotocolssoapextensionclasstopic.asp
> > > > > -----Original Message-----
[quoted text clipped - 15 lines]
> > accomplish
> > > > > this?