I attended this years Scotch of the Rocks with a press pass from Fusion Authority, and they have just published the articles that I and fellow "member of the press" Kola Oyedeji wrote as reviews of the conference.

Read them at A Tale of CFML, Flex and a Pineapple and A Review of Scotch on the Rocks 2007 respectively.

I have just installed my first Railo CFML Engine in a production environment.

There was a problem with changing the licence from Community to Profressional. So I emailed Railo and within minutes they came back with a custom solution to my problem.

Now thats what I call Customer Service!!

ColdFusion Query of Queries does not natively support OUTER JOINs. The following code demonstrates a work around to perform a LEFT OUTER JOIN between two CF queries, QueryA and QueryB.

i.e. To do this;

SELECT *
FROM QueryA
LEFT OUTER JOIN QueryB ON QueryA.ID = QueryB.ID

One can use;

<cfquery name="joinQuery" dbtype="query" >
SELECT *
FROM QueryB
WHERE QueryB.ID = -1
</cfquery>

<cfset QueryAddRow(joinQuery) />

<cfquery name="result" dbtype="query" >
SELECT *
FROM QueryA, QueryB
WHERE QueryA.ID = QueryB.ID

UNION

SELECT QueryA.*, joinQuery.*
FROM QueryA, joinQuery
WHERE QueryA.ID NOT IN (#ValueList(QueryB.ID)#)
</cfquery>

A common use of an OUTER JOIN is to find the non-matching records between two record sets, a so called NULL Based OUTER JOIN.

e.g.

SELECT *
FROM QueryA
LEFT OUTER JOIN QueryB ON QueryA.ID = QueryB.ID
WHERE QueryB.ID IS NULL

This situation can be more efficiently implemented in Query of Queries by using the following technique;

SELECT *
FROM QueryA
WHERE QueryA.ID NOT IN (#ValueList(QueryB.ID)#)

After much experimentation, I have finally managed to get Microsoft SQL 2005 Mirroring with automatic failover working with ColdFusion MX 6/7.

The following steps describe how to setup ColdFusion.

1. Install the latest version of the DataDirect drivers by following these instructions on the Adobe web site - Updated DataDirect JDBC drivers (version 3.5)
2. Create a new ColdFusion datasource of type "Other".
3. Enter the following settings, replacing XXXs with your details;

You should now be able to manually failover the mirrored database and, after an initial ColdFusion connection reset error, your application to run as normal.

Simple when you now how!

Although simple types such as string and int will be automatically handled by ColdFusion's SOAP mechanisms, the complex types "made up" by .NET are not. This results in "type mismatch" errors.

The following describes the steps needed to use a .NET service with complex types. The ArrayOfString type and a MyDotNetComp Sales API are used as an example.

1. Try to use the service and get a "type mismatch" error. The Java AXIS system will create .class files for each interface in the service.
2. Browse the "C:\CFusionMX7\stubs\" folder for these files. They will be under a folder structure unique to the service being called. For example the folder for Travelex is "C:\CFusionMX7\stubs\sometemp\com.mydotnetcomp.www\".
3. Copy the whole of this folder to "C:\CFusionMX7\wwwroot\WEB-INF\classes\". For example, "C:\CFusionMX7\wwwroot\WEB-INF\classes\com.mydotnetcomp.www\"
4. Add the path "C:\CFusionMX7\wwwroot\WEB-INF\classes\" to the 'ColdFusion Class Path' in the ColdFusion Administrator in the 'Server Settings > Java and JVM' section and restart the ColdFusion server. This step is required for AXIS to access the .class files.
5. One of the .class files in this example folder will be ArrayOfString.class which maps the ArrayOfString complex type defined for the web service.
6. This .class file can be used as an object type and used in the call to the web service, as shown in the example below;

<cfset ary = listToArray("abc", "def", "ghi") />

<cfset aofs = createObject("java", "com.mydotnetcomp.www.ArrayOfString").init() />

<cfset aofs.setString(ary) />