Illudium Flex Remoting Templates

I'm probably the laziest programmer on the face of the planet. As such, I am habitually looking for shortcuts and the fastest ways to accomplish things within the scope of all that I consider "acceptable" programming practices (a shockingly lax set of self-imposed development guidelines). For this reason, I spent the better part of the day customizing some Illudium PU-36 Code Generator templates to produce CRUD components for Flex development. Why would I do this, you ask? Because the ColdFusion Application wizards are not supported on the Mac platform and I spend at least 30% of my coding time writing the CFC interfaces needed by my Flex applications. The templates essentially create the same type of CFC files that the Windows version of Flex Builder generates. The resulting components are nearly identical to the default components that Illudium supports "out of the box" with a couple of exceptions. They have been slightly modified to support Flex RemoteObject calls. The code also instantiates objects in a slightly different way so that Flex can run everything through the Service CFC that Illudium creates. If you've used the CF application wizards on the Windows version of Flex Builder, the Illudium generated version is very similar (but better, I think) to the components created by it.

The enclosed zip file contains a folder that you should copy to your xsl\projects folder at the root of your Illudium directory. A new Template type entitled "FlexRemoting" should appear in the drop down box when you run Illudium. Point Illudium to your database table, choose the FlexRemoting template type, enter your dot notation to the CFCs (as they will be referred to in the RemoteObject function in Flex) and click the "Generate" button. Four files will be created (Bean, DAO, Gateway, and Service). Once you save these to the appropriate folder in your Flex project directory, open the Service CFC file and go to the bottom of the file. Find the function named "initCRUD" and replace the DSN place holder with the actual DSN you'll want to call with your components. Then, simply point your Flex RemoteObject (get, create, save, delete) functions to the appropriate function in the Service CFC.

Illudium appears to be a great tool and it has the potential to save substantial time when coding Flex applications if you, like me, don't have access to the full suite of ColdFusion extensions within Flex Builder. The FlexRemoting templates are my first attempt at customizing Illudium since I've only been working with it for about a day. If you have any recommendations as to how the templates could be improved, I'd love to hear them.

CFExchange* - The forgotten tag.

Over the last couple of months, I've seen quite a bit written about the great new features of ColdFusion 8. It amazes me, however, that the cfexchange* tags have not received the kind of notoriety that I expected they would have since hearing that this functionality would be included in Scorpio. These tags are nothing short of freaking awesome. I used to write hooks into Exchange mailboxes and calendars using CDO/CDONTS back in my ASP programming days. The effort and upkeep associated with this task almost made the added functionality of making my web apps talk to user Exchange accounts not worth the effort. I remember spending hours getting Exchange integration modules set up correctly only to have some minor change in code or O/S updates break the whole shooting match. The new CFExchange tags in CF 8 are so simple to use and maintain, however, I honestly don't see myself writing an application without them. In just a few lines of code, I can take data from a ColdFusion (or Flex) application and put it exactly where it needs to be within an Exchange mail store. It used to take PAGES of code to do this with ASP. If you haven't looked at these tags yet, get busy!

BlogCFC was created by Raymond Camden. This blog is running version 5.9. Contact Blog Owner