In honor of Mark Drew's visit to the Philly CFUG last night, and Sean Corfield's announcement about the new Railo beta today, I've just posted a new version of ColdFire with a debugging template for Railo. This is a beta release. For more info on installation and what's supported in this release see my blog post on the RIAForge site.
Just a quick post to let folks know I've just uploaded a extension only update for ColdFire which fixes a stored procedure related issue with the DB Queries tab. Check out the RIAForge site for more info.
Here is a interesting bug I ran into today while using CF No Debug. If you use the <cftrace> tag with the _cf_nodebug parameter set to true, the tag will throw the following error:
Variable DEBUGGER is undefined.
In ColdFusion, the <cftrace> tag is implemented in CFML via the pre-complied WEB-INF/cftags/trace.cfm template. Now, this is simply a guess, but I bet that trace.cfm uses the IsDebugMode() function to determine if it should attempt to write trace info to the debugging query. Possibly something like the following:
As I previously noted there is a bug with IsDebugMode() where it returns true when using _cf_nodebug = true, even though the debugging service is disabled. If something like the above code is used in trace.cfm, IsDebugMode() would return a false positive when _cf_nodebug is true and the ColdFusion ServiceFactory would return null for the debugger variable. When a null value is assigned to a ColdFusion variable it can lead to the undefined error we see in this case.
I've logged a bug with Adobe for this, but it is something to look out for if you use CF No Debug and start seeing "Variable DEBUGGER is undefined" errors.
I just uploaded a new version of ColdFire to RIAForge. This release is an extension only update so there is no need to update the server bits.
Here is a quick rundown of what is new/fixed:
Also, one thing I noticed while working on this release is that the variables tab does not correctly display child components. If you have a component that extends another component, you will only see the methods defined on the child component and the display will not indicate that the component extends another component. I'll have to look into what can be done to fix this, but in the meantime it is something to be aware of if you depend on ColdFire to give you the API for a component.
As always, keep the bug reports and feature requests coming.
Last week I updated my CF No Debug extension so that it will remember what state it was last in when you open Firefox. Before, when you closed and re-opened Firefox the extension was always disabled, allowing ColdFusion request debugging to execute. Now if you have the extension enabled when you close Firefox, it will remain enabled when you open Firefox again. This is an extension only update, so there is no need to update the servlet filter.
Yesterday uploaded the latest 1.3 release of ColdFire to RIAForge. Since it has been awhile since I've blogged about ColdFire here, I thought I'd take some time and share the new features that have been introduced in the 1.3 version of ColdFire.
So in my last post I talked about the _cf_nodebug parameter and how it can be used for disabling ColdFusion request debugging for single requests. Today I'm announcing a new Firefox extension and servlet filter that allow you to disable request debugging without appending the _cf_nodebug parameter to your URL. Install the servlet filter on your development server and the extension in Firefox and you can easily disable debugging for requests made through Firefox as needed via a nice little status bar icon. You can find out more and see screen shots at cfnodebug.riaforge.org.
Recently I went back to doing Flex work and one of the things I immediately missed was ColdFire. So I decided to take a look to see what could be done to get my favorite debugging tool working with CF powered Flex applications. Turns out it wasn't all that hard. First though, check out the video below to get an idea of what I'm talking about. (Sorry, no sound as I recorded this at work.)
Last night I released a new version of ColdFire, 1.2.117.126. This is an extension only bug fix release which:
I also realized I never announced the previous 1.2.117.117 release on this blog. That release had quite a few improvements and new features which I'll detail below.
A new version of ColdFire is up on RIAForge. This is an extension only update that fixes a bug related to JSON serialization/deserialization of queryparam values.
The problem was reported and fixed by Shane Bradly. He noticed that he was not seeing the SQL for some of his queries in the ColdFire Query tab. His investigation found that passing a numeric value for a text queryparam type such as cf_sql_varchar or cf_sql_char caused the following JavaScript in the ColdFire extension to fail:
