Asankha, wireshark is fantastic! Thanks for the tip.
All, Wireshark seems to be a generic port sniffer, with advanced filtering capabilities. Easier than TCPMon: http://www.wireshark.org/ Just use the "Following TCP Streams" feature in order to see the request / response SOAP envelopes. http://www.wireshark.org/docs/wsug_html_chunked/ChAdvFollowTCPSection.html Henrik 2008/12/11 Asankha C. Perera <[EMAIL PROTECTED]> > Hi Henrik > >> thank you very much, it looks like this will work. Using >> '*useOriginalwsdl*' >> and '*modifyUserWSDLPortAddress*' (correctly...), we now get this soap >> webservice location: >> >> <soap:address location="http://SERVERNAME:8280/services/ValidateCLI"/> >> >> where *8280 *is the port on which Synapse runs. >> >> I would very much like to use *TPMonitor *to spy on both the GET wsdl >> call, >> as well as the webservice call itself. Is it possible to have the >> (proxied) >> wsdl, returned by Synapse, to specify a different port number than 8280? >> >> > Yes, it basically spits out whatever WSDL you give it now.. > >> Such that I can configure a Synapse redirection? Or perhaps a different >> server name? >> >> > If you have any problems, run the two on two machines and use tcpdump, > wireshark etc.. > >> Many thanks for all your help! >> >> > np! glad it helped > > > cheers > asankha > > -- > Asankha C. Perera > http://adroitlogic.org > > http://esbmagic.blogspot.com > >
