On Sun, Sep 26, 2010 at 7:24 AM, Moss <[email protected]> wrote: > The WSDL shows <wsdlsoap:address location="http:// > local.daylocker.com:8080/ws/daylocker.cfc" /> > > which apparently is being used when Visual Studio tries to connect to > the web service--it says it can't connect. > (Visual Studio adds the web reference fine, but a runtime exception is > thrown) >
Sorry, catching up on a few back messages--did you get this resolved? I just did a quick test and I don't see this behavior. Is it possible you hit the web service, thereby generating the WSDL, before you set up the proxying (i.e. you hit it using the port number)? If so, it may be that it just never generated a new WSDL after you set up the proxying. There may be other ways to do this, but one way of forcing the WSDL to regenerate is to call your web service using cfinvoke and use the refreshwsdl attribute (set to true obviously). -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
