http://www.everythingflex.com/blog/1/2006/03/WebService-setup-for-FES.cfm and http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=60&catid=583&threadid=1177997&highlight_key=y&keyword1=proxy both chronicle the solution, but I'll admit it even took me a while to see what was the source of my issue.
In order to access the named services you must chose the project option to build your files on the server. If you build locally it doesn't see the named connection. Although the everythingflex article claims "If you wish to use a named service within FlexBuilder (non FDS application) you will need to add an argument to your Flex Compiler arguments under the project properties: mxmlc --services=./mypath/to/flex-enterprise-services.xml etc" I haven't tested. But my issue was resolved by building on server. Hope yours does too. --- In [email protected], "Jamie O" <[EMAIL PROTECTED]> wrote: > > I have had an identical issue that I'm unable to resolve. Here are the > 4 samples I've tried in my proxyConfig.xml file: > <destination id="DefaultHTTP"> > <properties> > <dynamic-url>http://URLGOHERE/WS.asmx?WSDL</dynamic-url> > </properties> > </destination> > > <destination id=Sample0> > <properties> > <dynamic-url>http://URLGOHERE/WS.asmx?WSDL</dynamic-url> > </properties> > </destination> > > <destination id="Sample1"> > <properties> > <wsdl>http://URLGOHERE/WS.asmx?WSDL</wsdl> > <soap>*</soap> > </properties> > <adapter ref="soap-proxy"/> > </destination> > > <destination id="Sample2" adapter="soap-proxy"> > <properties> > <wsdl>http://URLGOHERE/WS.asmx?WSDL</wsdl> > <soap>http://URLGOHERE/WS.asmx?WSDL</soap> > </properties> > </destination> > > <destination id="Sample3" adapter="soap-proxy"> > <properties> > <wsdl>http://URLGOHERE/WS.asmx?WSDL</wsdl> > <soap>http://URLGOHERE/WS.asmx?WSDL</soap> > </properties> > <channels> > <channel ref="my-amf"/> > </channels> > </destination> > > I've tried with the soap-proxy as default="true" and the general > state. When I call the URL direct from a web service it does work. As > soon as I try to do the named proxy approach, it fails. > > What am I missing??? I bet it's obvious :( > Jamie > > --- In [email protected], "nmsflex" <nmsflex@> wrote: > > > > > > i have .net web service api example > > > > http://190.100.1.102/ws/Service.asmx > > > > wsdl address: http://190.100.1.102/ws/Service.asmx?WSDL > > > > is anyone can show me how to set up webservice in fds to access > > my .net web service api > > > > if configure flex-proxy-service.xml by adding > > > > <destination id="myWS" adapter="soap-proxy"> > > <properties> > > <wsdl>http://190.100.1.102/ws/Service.asmx?WSDL</wsdl> > > <soap>http://190.100.1.102/ws/Service.asmx</soap> > > </properties> > > <channels> > > <channel ref="my-amf"/> > > </channels> > > </destination> > > > > but i still get error when i run my app > > Error: can not send and can not load success wsdl > > > > Thanks > > >
