Welcome!

You will be redirected in 30 seconds or close now.

ColdFusion Authors: Yakov Fain, Jeremy Geelan, Maureen O'Gara, Nancy Y. Nee, Tad Anderson

Related Topics: ColdFusion, Microsoft Cloud

ColdFusion: Article

ColdFusion MX and .NET 101

COM Interop to a .NET assembly can be successfully implemented with CFMX

Some of you may be thinking, ColdFusion (CF) and .NET? Why do it? We hear you. It is understandable that CF, running on top of J2EE, adds a layer of complexity when integrating with interfaces written with Microsoft-centric technologies. The mission of this article is to decipher the complexities and shed some light on how CF can be coupled with .NET solutions to allow for interoperability throughout your IT universe.

.NET is breaking in big in the IT arena and many organizations are adopting it as a standard for developing the business modules associated with their applications. A benefit that .NET brings with it is a true object-oriented methodology to developing software. I liken the C# language as the fraternal twin to Java; though with these benefits, it also brings an increased level of complexity for doing routine tasks that ColdFusion programmers have grown to take for granted.

You can't knock Joe programmer for wanting to learn a new technology. This outlook is preached continually from both Macromedia and Microsoft. With constant new releases and their advantages, the standouts must increase their understanding in all facets of the industry to stay a millimeter ahead of the curve. "What's that you say?" "You're not certified in CFMX...?" "Wait, what?" "You're not working on your MCAD/MCSD?" "Well, what are you waiting for?" Enough with our attempts at lighting a fire under you to expand your horizons, you're reading this article and we commend you for it.

With the J2EE release of ColdFusion MX (CFMX) and the new version 6.1, code-named "Red Sky," Macromedia has continued to support COM (Component Object Model)-based solutions via a COM bridge. CFMX uses a Java-to-COM wrapper that was developed by Intrinsyc. The package is known as J-Integra and details on this component can be found at http://ja.net.intrinsyc.com/. Their product info area has some excellent examples on how to implement J-Integra with various combinations of Java/COM components. J-Integra is instantiated through the cfobject tag or with cfscript utilizing the function CreateObject.

In our example in Figure 1, the cfobject tag was used. Notice the class that is called and the name we assign to the object. Once the object is successfully created, the CreateBarCodeImage method is accessed and the appropriate required parameters are passed to the component. The resulting page output is seen in Figure 2. The application structure is dumped, displaying the contents of the applicationname key and bcg (barcodgen) key. Notice how the object information and available related methods are displayed. CreateBarCodeImage is the method used to generate the barcode image seen in the output.

The ColdFusion code used for the example is an enhanced methodology for instantiating a COM component with ColdFusion. This enhanced methodology outlined in the following Macromedia TechNote, www.macromedia.com/support/coldfusion/ts/documents/tn18210.htm, allows the initial creation of the object to be stored in memory via application or session variables. This also enables the object to be shared across requests and easily accessed with a custom tag or cfmodule. This solution came about due to the observation that there was an increase in creation time in CFMX compared to CF 5. For the sake of argument, this technique is being demonstrated only to provide information in case you come across this issue. No performance issues were witnessed with the .NET/COM component utilized in this article.

So you can create an instance of a COM object in CFMX; ColdFusion has always made this an easy task. This gets interesting when you look at how this is actually achieved. Let's peek under the hood, shall we? Figure 3 shows how CFMX and J-Integra hook into various automation components. There is a similar diagram at http://ja.net.intrinsyc.com/j-integra/info/.

Now for a little light on what might be happening behind the scenes when you call into a .NET object through COM. Just to get the high-level talk out of the way, all .NET languages are compiled into an intermediate language called Microsoft Intermediate Language, also known as MSIL. Like Java, MSIL runs in a virtual machine, called the Common Language Runtime (CLR).

For those who have not dealt with COM before, it provides a binary specification allowing interaction between languages. COM also provides facilities for dynamic discovery of interfaces that an object has exposed.

COM was designed to provide a standard means of marshalling between languages; both platforms must perform some degree of marshalling between types in the respective runtimes and the facilities for accessing them specified by COM. The CLR provides a transparent proxy allowing .NET assemblies to be called from COM clients, called the COM Callable Wrapper (CCW). It is through the CCW that ColdFusion is able to indirectly interface with a .NET assembly (see Figure 4).

For this example we have chosen to implement a very simple component in C#, which when given a series of parameters, will generate an image of a barcode for use within a Web page. The component happily creates images of barcodes on request; it is not the job of this component to manage the lifespan of the files it creates. That task is better left to the consuming application (CFMX).

There are only a few steps needed to have a .NET component ready to be consumed directly from CFMX. First, the code must be written. Second, the assembly must be signed with a strong name and compiled. We generate a strong name key and associate it with the assembly by using the command-line utility sn.exe. Third, as with any .NET component, in order to be visible to COM clients, the assembly must be registered as a COM component. In our example we use regasm.exe to fulfill this task. Finally, we add our assembly to the Global Assembly Cache (GAC) where it is cached and ready to be called by a COM client.

Let's start by taking a look at the C# source file. We will break down each section with a brief explanation and detail any portions of the code that have particular significance to COM interop.

In the code block shown in Figure 5, we are specifying the namespaces that we will be utilizing, such as System.Drawing. We then specify that our class will be placed in the "BarCodeInterop" namespace. The namespace we use has significance in determining the common name we will use to refer to the component. In keeping with the binary interface concepts of COM, it is required that we define a public interface for the method that we will be implementing for our functionality.

COM components implement the IDispatch interface. The IDispatch interface exposes the contents of an object to all programs that support Microsoft Automation. The COM callable wrapper that is responsible for implementing IDispatch for our component will use the interface we have specified to return a COM signature for our method "CreateBarCodeImage". When we use OLEView to inspect the interface our COM object exposes, we get the method signature detailed in Figure 6.

In Figure 7 the first notable item is an "attribute" that provides direction to the compiler for the type of COM interface we want to implement. Using a class interface type of none, our class can provide access only through a late bound interface exposed by IDispatch. Note that our class implements the interface "IBarCodeGenerator" that we defined earlier.

Figure 8 contains the implementation of the required interface method "CreateBarCodeImage". The method creates an image file through the file path specified, with a width, height, and font size specified.

The steps that follow the writing of our code include signing the assembly, adding the assembly to the global assembly cache, and registering the assembly for COM interop. In order to sign our assembly we must first generate a strong name key. We use Microsoft's sn.exe to generate the key (see Figure 9).

Once we have a strong name key, we place the file in the root of our project and associate it with the assembly by editing the "AssemblyInfo.cs" source file. AssemblyInfo.cs contains attributes that allow you to specify component information such as company, version, etc. There are also three attributes that are involved in signing an assembly. We specify our strong name key file by editing the AssemblyKeyFile attribute as:

[assembly: AssemblyKeyFile("..\\..\\BarCodeInterop.snk")]

After signing the assembly and compiling it, the assembly is ready to be added to the global assembly cache. The .NET framework installs the .NET Configuration wizard located under Control Panel -> Administrative Tools, which allows the addition and configuration of assemblies to the global assembly cache, among other things (see Figure 10).

Simply click "Add an Assembly to the Assembly Cache" task link to browse to the assembly location and complete the step of adding the assembly to the global assembly cache.

The final step needed to expose our component to COM is registering the component as a COM component in the system registry. This task is accomplished using the command line utility regasm.exe (see Figure 11).

A typical registration would look like this: "regasm C:\BarCodeInterop.dll".

With the .NET component wrapped and registered, CFMX is able to see the objects' methods and their input parameters.

There you have it! An example that proves COM interop to a .NET assembly can be successfully implemented with CFMX. Why do it? This question has been answered.... It works, and it works well. Organizational leadership must assess costs respective to redesign with the ever-tightening budgets associated with IT. An environment that has been structured around COM and ColdFusion can now easily be converted to .NET and ColdFusion.

With all that goes into the base concepts of integrating CFMX and .NET solutions, we look forward to the next article on the subject of using a native .NET interface for CFMX known as Black Knight. We will also be discussing Web services solutions and their performance parameters. Until then...

More Stories By Jeffrey Bouley

Jeffrey Bouley is the founder of Strikefish, Inc., in Orlando, Florida. He is a certified ColdFusion developer and a former Macromedia Consultant. He currently provides software architecture and development solutions for ColdFusion, Java, .NET, XML, SQL Server, and Oracle Integration (www.strikefish.com).

More Stories By John Parrish

John Parrish has spent his career developing component-oriented systems for the Web. He also serves as director for Jikapa Interactive Inc, an interactive solutions firm providing software and corporate design solutions (www.jikapa.com).

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Shane Sauer 07/12/05 01:25:13 PM EDT

Intrinsyc Software has just released a new J-Integra product for J2EE/.NET interop... J-Integra Espresso! J-Integra Espresso is a true CORBA solution for the Microsoft .NET framework. This Object Request Broker (ORB) has been written in C# and connects Java and CORBA with the .NET world. J-Integra Espresso has been developed entirely as managed code and can therefore be accessed by all .NET languages (C#, ASP.NET, etc...).

J-Integra Espresso features:
* Pure .NET implementation, 100% managed code
* Bi-directional: .NET to Java/CORBA and Java/CORBA to .NET
* Enables interoperability with any J2EE or CORBA infrastructure that is IIOP-compliant such as VisiBroker, Orbix, JacORB, JBoss, WebLogic, and WebSphere
* Support for IIOP transport protocols including SSL and TLS over IIOP (SSLIOP)
* Marshalling objects by reference or by value
* One-sided deployment (no touch on J2EE AppServer)

A free evaluation version can be downloaded at http://j-integra.intrinsyc.com/

Regards,

Shane Sauer
Intrinsyc Software International, Inc.
J-Integra Interoperability Solutions
http://j-integra.intrinsyc.com/
When Web Services are not enough

IoT & Smart Cities Stories
CloudEXPO | DevOpsSUMMIT | DXWorldEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
DXWorldEXPO LLC announced today that Big Data Federation to Exhibit at the 22nd International CloudEXPO, colocated with DevOpsSUMMIT and DXWorldEXPO, November 12-13, 2018 in New York City. Big Data Federation, Inc. develops and applies artificial intelligence to predict financial and economic events that matter. The company uncovers patterns and precise drivers of performance and outcomes with the aid of machine-learning algorithms, big data, and fundamental analysis. Their products are deployed...
All in Mobile is a place where we continually maximize their impact by fostering understanding, empathy, insights, creativity and joy. They believe that a truly useful and desirable mobile app doesn't need the brightest idea or the most advanced technology. A great product begins with understanding people. It's easy to think that customers will love your app, but can you justify it? They make sure your final app is something that users truly want and need. The only way to do this is by ...
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
The challenges of aggregating data from consumer-oriented devices, such as wearable technologies and smart thermostats, are fairly well-understood. However, there are a new set of challenges for IoT devices that generate megabytes or gigabytes of data per second. Certainly, the infrastructure will have to change, as those volumes of data will likely overwhelm the available bandwidth for aggregating the data into a central repository. Ochandarena discusses a whole new way to think about your next...
Cell networks have the advantage of long-range communications, reaching an estimated 90% of the world. But cell networks such as 2G, 3G and LTE consume lots of power and were designed for connecting people. They are not optimized for low- or battery-powered devices or for IoT applications with infrequently transmitted data. Cell IoT modules that support narrow-band IoT and 4G cell networks will enable cell connectivity, device management, and app enablement for low-power wide-area network IoT. B...
The hierarchical architecture that distributes "compute" within the network specially at the edge can enable new services by harnessing emerging technologies. But Edge-Compute comes at increased cost that needs to be managed and potentially augmented by creative architecture solutions as there will always a catching-up with the capacity demands. Processing power in smartphones has enhanced YoY and there is increasingly spare compute capacity that can be potentially pooled. Uber has successfully ...
SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...