Fair point, Kai.
And in case one can't use the servicefactory approach described there (which is technically unsupported and often disabled by the Admin's on a shared host), here are a couple other solutions. The first is how one can do it with the Admin API (as of 7), but it does require knowing the Admin password: http://www.carehart.org/blog/client/index.cfm/2006/12/12/refreshing_web_serv ices_programmatically The second is a far simpler way that can be done from code, without Admin rights, which would serve like Matthew on his CF 8 hosted server: http://www.carehart.org/blog/client/index.cfm/2007/9/3/cf8_hiddengem_refresh wsdl Hope that helps, if the earlier note's ideas don't prove to find the source of the problem. /charlie From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf Of Kai Koenig Sent: Monday, June 22, 2009 11:01 PM To: cfaussie@googlegroups.com Subject: [cfaussie] Re: Web service not working after CF8 upgrade Matt, CF caches stub and skeleton Java classes generated from a published web service. I can't say for sure but it wouldn't surprise me at all if those are just kept during an server upgrade from CF 7 to CF 8 and now trigger the behaviour you're seeing. Here's a link of how to clear the WS cache programmatically: http://www.bloginblack.de/archives/000824.cfm Cheers Kai --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
