Table of Contents
Advertisement
DEVELOPING COLDFUSION 9 APPLICATIONS
Using Web Elements and External Objects
How .NET access works
For ColdFusion to access .NET assemblies, ColdFusion .NET extension software must run on the system that hosts the
assemblies. A ColdFusion system that accesses only remote assemblies does not require the .NET extension. The .NET
extension software provides the .NET-side connectivity features that enable access to .NET assemblies, including a
.NET-side agent (which normally runs as the ColdFusion .NET service) that listens for and handles requests from the
ColdFusion system.
On the ColdFusion system, the ColdFusion objects use Java proxies that act as local representatives of the .NET classes.
These proxies use binary TCP or SOAP-based HTTP communication to access a .NET-side agent. The agent then uses
a DLL to invoke the .NET assembly classes. This communication is required in all cases, even if ColdFusion and the
.NET assemblies are on the same system.
The following image shows how CFML-to-.NET access works:
CFML Page
Invokes
Java Proxy
Uses
JNBCore.jar
(installed on all
ColdFuson
systems)
ColdFusion Side
If your .NET assemblies are on the local system, ColdFusion automatically creates and manages all required proxies
and configuration information. Ensure only that the .NET extension is installed on your system and that the
ColdFusion .NET Service is running. You can use the
assemblies without any additional steps.
Application view
TCP/Binary or
HTTP/SOAP
communications
both sides can be
on a single system
tag or
cfobject
Last updated 8/5/2010
.NET Assembly
Invokes
JNBShare.dll
JNBDotNetSide.
exe.config
Specifies
assembly classes
JNBDotNetSide.exe
(runs as a Windows
service)
.NET Side
function to access the
CreateObject
1150
Uses
Advertisement
Table of Contents
