When you are building an application that uses the Flex FDS or ColdFusion servers as a back-end you need to define in your FlexBuilder project properties an additional compiler argument, -services. Why? FlexBuilder needs this argument/path to your services-config.xml file so it can pull just a few pieces of information out of the xml file.

A friendly URL reminder for myself and everyone who finds this first. Now I don’t have to go searching for it next time. This pdf covers how to Configure Flex2 and ColdFusion to work with FlashRemoting, Flex Data Services, and Flex Messaging. Using CF with Flex2 Did you like this? Share it:Tweet !function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=”//platform.twitter.com/widgets.js”;fjs.parentNode.insertBefore(js,fjs);}}(document,”script”,”twitter-wjs”)

They say a picture is worth a thousand words and I figure some code is too (ok maybe 500 words, but who is counting). To help understand how an application that uses FDS works compared to Flash Remoting, I’ve taken a Flash Remoting application and re-written it use FDS instead. Hopefully this will help you

A common configuration question with Flex2 developers who are trying to use the Flex Data Server and CF is “How do I use FDS and Flash Remoting calls with CF, in the same app?”. The reason this gets confusing is because both Flex and CF have their own version of the services-config.xml file, and you