Adobe adds .NET interoperability to Cold Fusion

Adobe ColdFusion 8 brings built-in .NET integration tools to developers working with the widely used server. Clearly, this is an example of how ISVs can drive forward the cause of platform interoperability. Adobe used JNBridge tools.

By Jack Vaughan

The type of interoperability Java brought to computing is somewhat forgotten. But much of the push behind the language was in its JVM’s ability to traverse operating systems, especially multiple Unix operating systems. This gained great initial traction because its was a boon to Independent Software Vendors (ISVs) that  were duplicating developer effort redoing releases for multiple platforms.

Today, ISVs remain a driver of interoperability. Here’s a notable recent example.

Adobe Systems has released ColdFusion 8. Its support for Windows Vista and JBoss, and its integration with the latest version of various databases are touted by Adobe. But what interests us here today at TheServerSide Interoperability blog is the new level of .NET integration support ColdFusion 8 brings to developers.

These developers have had a high-level of Java support for some time, as the ColdFusion Engine moved to run on J2EE some while ago. But the new ColdFusion 8 setup preps the stage for developers looking to incorporate both Java and .NET objects, hooking them together with relatively simpler ColdFusion markup, into apps.

“Some of our customers have been using J2EE objects in ColdFusion applications for a long time,” say Tim Buntel, senior product marketing manager for ColdFusion at Adobe.

He said these include, for example, pieces of corporate business logic. Microsoft, Sun, and IBM, too, are pursuing such hybrids of dynamic and static language. Apparently, GOCFM [Good Old ColdFusion Markup] has a leg up.

Now comes .NET support.

As Adobe fleshed out requirements for ColdFusion 8, it found many of its customers were part of organizations that had both Java and .NET development going on, said Buntel.

So, he continued, “we added a bridge between .NET and ColdFusion so developers can use .NET objects the same way they can use a Java object today.”

“The ColdFusion developers can use those native technologies in their application with the simple ColdFusion Markup language.”

Buntel confirmed that Adobe worked with JNBridge to create its .NET integration components in ColdFusion 8.

TSS Interop blog talked with JNBridge’s Wayne Citrin. “From our point of view we have provided a bridging technology, and .NET and Java will work in their environment, said JNBridge head Wayne Citrin. “We think it is a plus.”

“Theirs is not a translation between Java and .NET,” Citrin said of Adobe. “ One of the nice things about it is that Adobe didn’t have to change their Java code, and Adobe customers don’t have to change their .NET code .”

The ColdFusion server had a big role in developing the modern Web. Forged by Allaire Corp., ColdFusion was the first blindingly popular page rendering Web app server built with dynamic scripting language. It is important still, used by tens of thousands of developers, and also being the force behind the famed web site.  ColdFusion is further important, in our estimation as a potential show case for interoperable solutions that will save developer effort.

One Response to “Adobe adds .NET interoperability to Cold Fusion”

  1. Vince Bonfanti Says:

    BlueDragon.NET, a ColdFusion-compatible application server implemented completely in .NET (using a combination of J# and C#) was introduced by New Atlanta more than two years ago, in March 2005. BlueDragon.NET provides true integration of CFML (ColdFusion Markup Language) with .NET and ASP.NET, not just “interoperability” via a Java-.NET bridge. was the lead customer for BlueDragon.NET (

    For more info on BlueDragon:

Leave a Reply