I just uploaded a new zip (v0.3.1) - found a few tiny bugs. The first fix changes generateXMLDataFile.cfm. Removed the cfflush which was interfering with the cflocation. Another minor fix in cfcFlexplorer.cfc to the tree generator. If you left a trailing "\" in your path in the settings.xml file the function was not properly removing it.

Also I deleted the xml config file from my localhost that shouldn't have been uploaded and reset settings.xml to be generic.

Since I'm brand spankin new to Flex (aren't we all really?) I have had a few reports of issues with running cfcFlexplorer that I'm not too sure how to advise people to resolve. Here are a few notes that I've found that you should keep in mind:

1. This one is obvious, but make sure you're running CF 7.0.2.
2. cfcFlexplorer is designed to run in the webroot. If you place it anywhere else, you must create a mapping (/cfcFlexplorer) and you must edit the services-config.xml file on your server (located at wwwroot\web-inf\flex\services-config.xml) and set true (it is false by default).
3. Another obvious one, but make sure "Enable Flash Remoting Support" is checked in your CF Admin under Data & Services - Flex Integration.
4. Obscure - but possible - in your mappings, if you've ever updated from a previous version of CF, make sure that your "/" mapping points to "C:\CFusionMX7\wwwroot" (or whatever is appropriate) and NOT C:\CFusionMX\wwwroot (note the missing '7').

Also keep an eye on the comments over here at Brian Rinaldi's blog. Some folks have reported similar issues with his latest project.

I've started working on an enhancement that will support the creation proxy components. Basically the feature will take an existing component and generate a skeleton proxy that would work with your existing component. I think it would be nice to have cfcFlexplorer do some of the heavy lifting for the creation of the proxy component. I've never been real big on code generators, but much of the work of creating the proxy seems redundant. Post some feedback in the comments if you have an opinion on this one.

There's an undocumented feature in release 0.3 that I wanted to blog about to let people test if they're interested. I've started to add support for passing complex objects as arguments to your methods. Basically I've only added support for structs, so if your param is a struct you can simply enter a key value list and it will be auto parsed and passed on while invoking the method.

For Example:

In the value column of the param grid will create a simple structure with the keys foo and fooya with the corresponding values.

Any thoughts? It's a pretty cool feature, but I'm not sure how often it will be necessary. I'm hesitant on adding support for other objects (queries, arrays) since I think it's even more rare that a public or remote method expects these as a parameter.

Last night I checked the project into SVN. I'd consider this version 0.2 since it includes some minor changes. The MXML source files are located in the FlexSource folder for those interested in modifying them so they can recompile locally. I'm not going to be updating the zip just yet. Hopefully soon...

Tariq "CFLEX" Ahmed has offered to collaborate on the project so I'm looking forward to a bright future for this tool!

I've made a few changes locally that I wanted to share. I hope to package everything and ship a new version by next week.

Done:

• Added PDF/Flaspaper output of components
• Added filtering to component grid. This will allow you to search/filter the grid based on any column. For example if you wanted to filter the grid to show only those methods that return a query.
• Misc refactoring/code clean up

To Do:

• Check files into SVN
• Clean up zip - very messy - sorry :(
• Other cool stuff.

If you have any feedback, drop it here or in the forum.