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, 188.8.131.52. This is an extension only bug fix release which:
- fixed issues with execution times tab summary rows (issues 42 and 44)
- fixed issue with variables tab (issue 43)
- improved multiple tab support.
I also realized I never announced the previous 184.108.40.206 release on this blog. That release had quite a few improvements and new features which I'll detail below.
Just a quick post to let folks know the code and unit tests for JSONUtil are now in SVN at RIAForge.
After getting into another discussion last week about the problems with Serialize/DeserializeJSON and ColdFusion's implicit type conversion I decided to try to do something about it. Over the weekend I put together a proof of concept which I've released as JSONUtil. From the RIAForge project site:
The JSONUtil project currently consists of the JSONUtil component. This component has two public methods, serialize and deserialize, which have method signatures similar to ColdFuison 8's built in Serialize/DeserializeJSON functions. The JSONUtil deserialize method takes the same parameters as DeserializeJSON, JSONVar and strictMapping, and should produce the same results as that function. The JSONUtil serialize method takes the var and serializeQueryByColumns parameters, just as ColdFusion 8's built in SerializeJSON function, however this method also takes an optional third parameter, strictMapping. If the strictMapping parameter is ignored the serialize method should produce the same results as ColdFusion 8's built in SerializeJSON function. If the Boolean strictMapping parameter is set to true then the serialize method attempts to convert the ColdFusion data to a JSON string using underlying Java/SQL data types as opposed to using ColdFusion's implicit type conversion conventions.
The code for the JSONUtil component is based on that of the json.cfc from the CFJSON project, http://www.epiphantastic.com/cfjson. This project probably would not have happened were it not for CFJSON. Thank you to Jehiah Czebotar, Thomas Messier, and everyone who has contributed to the CFJSON project.
To expand on the RIAForge description a bit further, the strictMapping attribute I've added to the serialize method forces the CF data to be serialized based on it's underlying Java data type. For example the following code:
<cfset x = "123" />
<cfoutput> #JSONUtil.serialize(var=x, strictMapping=true)# </cfoutput>
will produce the following JSON string:
SerializeJSON or JSONUtil.serialize without the strictMapping attribute will produce the following JSON string:
The strictMapping attribute also applies to query data as well. If you have a varchar column, its data will always be serialized as string data, even if the string is a numeric or Boolean value in ColdFusion. The strictMapping option also allows you to use JavaCast to help ensure your data values are serialized properly.
There is, however, one caveat to the strictMapping option. In ColdFusion most values are stored as strings. This means that both x and y below:
<cfset y = 123 />
will be serialized as:
If you want numeric values to be serialized as such when using strictMapping you will need to use the Val or JavaCast functions:
<cfset y = JavaCast("int",123) />
(Note: you do not need to do this for query values as query columns are automatically cast to the appropriate Java type by JSONUtil.)
So head over to RIAForge and check it out, and be sure to report any issues via the bug tracker.