Whenever I've had to call a .NET web-service, where any of the arguments are complex, I've always had to construct the SOAP envelope manually. In the end, this took less time than trying to call it directly -- and failing, and failing, and failing.
Cheers, Kris > This isn't my web service: it's a third-party thing that was implemented in > .NET. I haven't seen the source, but I strongly suspect that it's declared as > taking an XmlNode for that third parameter. (Like the proxy method that .NET > generates.) > > Worse comes to worst, I suppose I can build the (very simple) SOAP envelope > myself, and use CFHTTP, but I *really* don't want to do that if I can avoid > it. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:320474 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
