Adobe 38043740 - ColdFusion Standard - Mac Development Manual page 1159

DEVELOPING COLDFUSION 9 APPLICATIONS
Using Web Elements and External Objects
• For each method in the class:
• The method's return value's class (if any) and all of its supporting classes.
• For each of the method's parameters, the parameter's class and all of its supporting classes.
• For each constructor in the class, for each of the constructor's parameters, the parameter's class and all of its
supporting classes.
Unlike Java, where supporting classes include exceptions that methods throw, .NET supporting classes don't include
thrown exceptions, because they are not declared in advance.
The number of supporting classes depends on the classes explicitly listed, but it often can be 200-250 classes. Usually
you generate all supporting classes. However, to save time or space, you can generate only those classes explicitly
specified, without supporting classes.
If a proxy for a supporting class has not been generated, and a proxy for such a class is later needed when the proxies
are used, the proxy for the nearest superclass to the required class is used instead. If that proxy hasn't been generated,
the proxy for the superclass of that superclass is used if it has been generated, and so forth, until the proxy for
System.Object (which is always generated) is encountered. Thus, even with an incomplete set of proxies, code executes,
although functionality and other information could be lost.
In the jnbproxyGui tool, when you click the Add button, the list includes only the explicitly listed classes. When you
click the Add+ button, the list also includes the supporting classes. In the jnbproxy command line program, the default
command generates proxies for the supporting classes; use the
Configuring the .NET-side system
To configure the .NET-side system, you edit the jnbridge\JNBDotNetSide.exe.config configuration file in the
following ways:
• For local assemblies, edit this file only if you do not use the default port, or if you use SSL security.
• For a .NET assembly on a remote machine, register the assemblies in this file to make it accessible to ColdFusion.
Edit the configuration file
Ensure that the following lines are in the <configSections> subsection of the <configuration> section:
1
<jnbridge>
<javaToDotNetConfig scheme="Protocol" port="local port number"
useSSL="true|false" certificateLocation="server certificate path"/>
</jnbridge>
• The
attribute specifies the communications protocol, and must be
scheme
• The port number is the port of the .NET-side agent, normally 6086.
• The attribute specifies whether to use SSL for secure communications. The attribute is optional; the
useSSL
default is to not use SSL.
• The
certificateLocation
attribute is
useSSL true
These settings must be the same as the corresponding attributes in your
If the .NET assemblies are on a remote system, specify the assemblies that ColdFusion accesses by adding the
2
following elements inside the <jnbridge> section.
attribute specifies the location of the server SSL certificate. It is required only if the
.
Last updated 1/20/2012
option to override this default.
/ns
or
jtcp http
tag.
cfobject
1154
.