I've had this trouble before as well, I seem to recall it may be something to do with AXIS (bit that actually gets the WS). I'm not sure if clearing out the stubs would do it or if you can change the config somewhere. I know a restart fixes it but that's not a valid solution in a live environment and still a pain in dev.
Ian On Fri, 14 Jan 2005 09:18:05 -0500, Matthew Small <[EMAIL PROTECTED]> wrote: > Hi all, > I've built a webservice in .Net that I intend to consume from CF. As > I'm building it, I've noticed that the .NET Web service's arguments are > cached by CF - that is, if I make a change to the .NET WS, then CF doesn't > "realize" it. > I know this sounds sort of strange, but as I'm troubleshooting the > connection between CF and .NET, I might see one error message from CF. I'll > continue to see the same error message repeatedly, even if I change the .NET > webservice to work with what CF is passing. When I restart the CF server, > it then acts appropriately - either by throwing a different error or > working. > Is there a setting to change in CF to prevent "Webservice caching"? > > Thank you, > Matthew Small > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:190436 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
