Flex 3 Remoting: Server Technology option not needed

Flex 3 Remoting: Server Technology option not needed

Yesterday I was pinged on IM by John Farrar about an issue he was having connecting Flex to ColdFusion on his new system. He’d done this many times before but hit a bump so we jumped on Adobe Connect and looked into it. One of the issues he was having, which went unresolved, was in him setting his server location info. It asks for things like server root, etc (see below). The main problem is in his setup, it seemed. He is using Apache as his web server and server docs out of a separate folder on his system, not the standard c:\ColdFusion8\wwwroot (for standalone). Typing in the CF location expects your “Output folder” to be within the CF\wwwroot folder. The problem with that is he using a completely separate folder (c:\foo\whatever\localhost). Maybe there was a way around it but after fooling with it for a second I fell back to old faithful. From my first time playing with Flex 2 remoting I attempted to use this screen but didn’t want to use my localhost CF (I stopped doing that a while back; have come back to local dev though). I learned how to set my endpoint, destination, and source all on my mx:RemoteObject directly so I took that approach in helping Senor Farrar. Here is some simple code to point out the ease of writing Remoting code in mxml. 1 2 3 <mx:RemoteObject id="service" destination="ColdFusion" endpoint="http://localhost/flex2gateway" source="com.katapultmedia.test.SomeCFC" fault="trace(event.message.body)"> <mx:method name="lookMa" result="trace(event.result)" /> </mx:RemoteObject> That’s it. This would work for PHP or any other backend by simply setting the endpoint, destination, and source. In the case I’m pointing to...