> Right, which works fine to pull the WSDL, but I needed to see > what was actually being sent to the soap service. Because > WSDL can specify an endpoint address other than the local > address, once the web service had retrieved the WSDL, all > calls to the actual web service itself were routed to the > external address before the proxy could intercept them.
Yeah, I forgot about that. A packet sniffer makes that kind of thing a little easier, as you can just record all traffic without forcing it through a specific proxy port. I mentioned Ethereal earlier, but there are HTTP-specific sniffers like Effetech's (http://www.effetech.com/) which can let you see this sort of thing. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ phone: 202-797-5496 fax: 202-797-5444 ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
