One side note here. You should remember you are always by default using the proxy unless you explicitly say not to. A lot of people don't realize this.
You can do this inside your service tag by setting the attribute useProxy="false" There are also settings in flex-config which control proxy use. See the <proxy-use-policy> tags inside flex-config.xml >From the comments; determine whether the proxy is used or bypassed by client - up to the client via the useProxy attribute on the WebService, if unspecified will use the proxy always - always use the proxy, useProxy='false' on the WebService will generate a Warning never - never use the proxy, useProxy='true' on WebService will generate a Warning By default the tag looks like: <proxy-use-policy>client</proxy-use-policy> Which is actually saying that unless useProxy="false" is set, the proxy gets used. -- Dave Wolf Cynergy Systems, Inc. Macromedia Flex Alliance Partner http://www.cynergysystems.com Email: [EMAIL PROTECTED] Office: 866-CYNERGY < --- In [email protected], "Raheen M Shabbazz" <[EMAIL PROTECTED]> wrote: > > Thanks for the reply. > > I am using v1.5. I don't believe that I am using any proxy at all. > > This is the REST service that I have created :: > > ======================== > <mx:HTTPService id="my_rest_ws" > url="http://www.mydomain.com/services/restsvc"; method="GET"> > > <mx:request> > <param1>val1</param1> > <param2>val2</param2> > <param3>val3</param3> > </mx:request> > </mx:HTTPService> > ========================= > > Below, I've got two simple controls :: > > ========================= > <mx:Canvas width="550" height="400"> > > <mx:Image source="{my_rest_ws.result}" width="400" height="400" /> > <mx:Button label="Button" click="my_rest_ws.send()"/> > > </mx:Canvas> > ========================= > > > The idea is to hit the button and have the mx:image dynamically load > the image returned from call to the web service. The web service > exists on a production server (a system completely seperate from my > development machine and entirely out of my control). If I manually > type the service URL with parameters into the address bar, I get the > image that I expect. So, for example > http://www.mydomain.com/services/restsvc?param1=val1¶m2=val2¶m3=val3 > returns the image with no trouble. When trying the web service code > above, however, I get the generic error mentioned before -- "Could Not > Retrieve Data". (NOTE -- I thought that the problem may be with the > mx:image tag loading the results, but the error remains even when I > remove the mx:image tag altogether.) > > In the flex-config.xml file, I changed the HTTPServices section to > read <url>http://*</url> That fixed the error I was getting before > which said (paraphrased) that the URL was not legal and needed to be > added to the allow list. > > I'm not sure about your crossdomain.xml question? > > I'm guessing the problem lies with either my code or my Flex settings > as I believe the server gets hit with a number of service requests on > a regular basis and can accomodate a wide variety of flavors and > implementations. > > I'm totally stumped. For a simple example, it sure is giving me a run > for my money! Been tinkering with it all night! I just keep getting > that same generic and uninformative error. > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
