I am in Los Angeles today for customer meetings, and head back home tonight. This week’s usergroup presentations went really well, and attendees seemed really excited at the opportunities made possible by Flex 2, and the clean seamless integration between ColdFusion on the server and Flex generated Flash on the client.
The only real gotcha occurred last night, when Flex Builder 2 (which had been working for me perfectly all week) started throwing JVM errors on startup. Normally I’d have repeated the steps, capturing error logs in the process, and sent them to the engineers to look at – after all, that is what beta is for. But with attendees waiting for me to get started – well, after the obvious fixes (-clean, deleting the workspace, removing most recent plug-ins) didn’t work I uninstalled Flex Builder, cleaned up the folders, and performed a clean install. That did the trick, and the presentation started only 20 minutes late. To those of you sitting there patiently, thanks.
One question that came up repeatedly (in various forms) was “are Flex Enterprise Services needed for Flex apps to communicate with ColdFusion?”. And despite explaining this repeatedly, there still seems to be some confusion about this one. So … the answer is no. You can use <:mx:remoteobject> and