Extensions section

Use the Extensions section of the Administrator to configure ColdFusion to work with other technologies, such as Java and CORBA.

    Java Applets page

    The Java Applets page of the Administrator lets you register applets and edit and delete applet registrations. Before you can use Java applets in your ColdFusion applications, register them in the Java Applets page.

    When your applet is registered with ColdFusion, using the cfapplet tag in your CFML code is simple, because all parameters are predefined: Enter the applet source and the form variable name to use.

    Note: Parameters set with the cfapplet tag override parameters defined on the Java Applets page.
    This page has the following areas:

    • Register New Applet: Registers a Java applet to include in your ColdFusion applications.

    • Actions: Click the Edit icon to edit registration fields of a Java applet. Click the Delete icon to remove the registration of a Java applet.

    • Applet: Click the name of a Java applet to view or edit the registration fields for that applet.

    • Code:Identifies the name of the file that contains the applet subclass.

    • Method: If applicable, this column identifies the method name used in the name attribute of the cfapplet tag.

    • Code Base: This area identifies the directory that contains the applet components.

    Add/Edit Applet page

    To register or modify a Java applet in ColdFusion, use the Add/Edit Registered Java Applet page. Registering an applet lets you use the cfapplet tag.

    Register a Java applet or modify the registration

    1. If you are registering a new Java applet, install the Java class files and any other files required for the class. Make a note of the installation path, because you must specify the code base arguments when you register the applet.

    2. To access the Add/Edit Registered Java Applet page:

      • For new registration, select Extensions > Java Applets, and click Register New Applet. The Add/Edit Registered Java Appletpage appears.

      • For existing registration, in the Registered Java Applets table, click the name of the Java applet registration that you want to view or modify.

    3. On the Add/Edit Registered Java Applet page, specify or modify the following information:

      Option

      Description

      Applet Name

      Provide a name for the Java applet.

      Code

      Identify the name of the file that contains the applet subclass. This filename is relative to the code base URL. The *.class file extension is not required.

      Code Base

      Provide the URL of the code base; the directory that contains the applet components. The applet class files must be located within the web browser root directory; for example, http://<servername>/classes.Note that this field is not required if the Java applet components are contained in a JAR file. For more information, see the Archive option.

      Archive

      (Optional) If the Java applet components are stored in a jar file, enter the jar filename in the Archive text box.

      Method

      (Optional) Specify the method name in the applet that returns a string value. This method name is used in the name attribute of the cfapplet tag to populate a form variable with the method's value. If the applet has no method, leave this field blank.

      Height

      Enter a measurement in pixels for the vertical space for the applet.

      Width

      Enter a measurement in pixels for the horizontal space for the applet.

      Vspace

      Enter a measurement in pixels for the space above and below the applet.

      Hspace

      Enter a measurement in pixels on each side of the applet.

      Align

      Select an alignment option.

      Not supported message

      Specify a message that will be displayed by browsers that do not support Java applets. You can override this message with a different message notsupported attribute in the cfapplet tag.

      Parameter name

      Enter a name for each required applet parameter. Your Java applet typically provides the parameter name needed to use the applet. Enter each parameter in a separate parameter field.

      Value

      Enter a default value for every parameter name specified. Click Add to add the values for the parameters. Your applet documentation provides guidelines on valid entries.

    4. To save and apply the registration information, click Submit.

    CFX Tags page

    Before you can use a CFX tag in ColdFusion applications, register it. Use the CFX Tags page to register and manage ColdFusion custom tags built with C++ and Java.

    You can build CFX tags in the following two ways:

    • Using C++ as a dynamic link library (DLL) on Windows or as shared objects (.so or .sl extension) on Solaris and Linux

    • Using Java interfaces defined in the cfx.jar file

    The page has the following areas:

    Area

    Description

    Register Java CFX

    Click this button to register a CFX Java tag that you want to include in your ColdFusion applications.

    Register C++ CFX

    Click this button to register a CFX C++ tag that you want to include in your ColdFusion applications.

    Actions

    Click the Edit icon to edit the registration fields of a CFX tag. Click the Delete icon to remove the registration of a CFX tag.

    Tag Name

    Click the name of a CFX tag to view or edit the tag's registration fields.

    Type

    Identifies the type of language used to build the CFX tag (C++ or Java).

    Description

    Identifies the use of the CFX tag.

    Add/Edit CFX Java Tag page

    Option

    Description

    Tag Name

    Enter the tag name (after the cfx_prefix). Provide a name for the CFX tag that you are registering.

    Class Name

    Enter the class name (without the .class extension) that implements the interface. The class file should be accessible from the Class Path setting on the Java and JVM page. You typically package the .class file in a .jar file and save it in the cf_root/lib (server configuration) or cf_webapp_root/WEB-INF/cfusion/lib (J2EE configuration) directory.

    Description

    Provide a message that identifies the use of this CFX tag.

    Add/Edit CFX C++ Tag page

    Option

    Description

    Tag Name

    Provide a name for the CFX tag that you are registering. Tag names must be prefixed with cfx_.

    Server Library (.dll)

    Enter the path to the library, or click Browse Server to locate the library that you want to use.

    Procedure

    Enter the procedure that implements the CFX tag. The procedure name must correspond with the procedure associated with the DLL or shared object you have specified. Notice that procedure names are case sensitive.

    Keep Library Loaded

    Select this option to retain the library in RAM.

    Description

    In this text box, provide a message that identifies the use of this CFX tag.

    Custom Tag Paths page

    Use the Custom Tag Paths page of the Administrator to add, edit, and delete custom tag directory paths.

    By default, all custom tags are stored under the cf_root/ CustomTags (server configuration) or cf_webapp_root/WEBINF/cfusion/CustomTags (J2EE configuration) directory. However, you can specify additional paths to your custom tag locations by using this page.The following table describes the areas on the page:

    Area

    Description

    New Path

    Specify the path of your custom tags.

    Browse Server

    Click to browse your system fro the location of your custom tags.

    Add Path

    Click to add the path specified in the path text box.

    Actions

    Click Exit to edit or Delete to remove a selected path.

    Path

    Identifies the custom tag paths registered in ColdFusion.

    CORBA Connectors page

    Use the CORBA Connectors page to register, edit, and delete CORBA connectors. Register CORBA connectors before you use them in ColdFusion applications and restart the server when you finish configuring the CORBA connector.

    ColdFusion loads object request broker (ORB) libraries dynamically by using a connector, which does not restrict ColdFusion developers to a specific ORB vendor. The connectors depend on the ORB runtime libraries provided by the vendor. A connector for Borland Visibroker is embedded within ColdFusion. Make sure that the ORB runtime libraries are in cf_root/runtime/lib (server configuration) or cf_webapp_root/WEB-INF/cfusion/lib (multiserver and J2EE configurations).

    The following table contains information about the libraries and connectors:

    Operating System

    Vendor

    ORB

    ColdFusion connector

    ORB library

    Windows NT and later

    Borland

    VisiBroker 4.5

    coldfusion.runtime.corba.VisibrokerConnector (embedded)

    vbjorb.jar

    Solaris

    Borland

    VisiBroker 4.5

    coldfusion.runtime.corba.VisibrokerConnector (embedded)

    vbjorb.jar

    Example of a CORBA connector configuration for VisiBroker:

    ORB Name                            visibroker 
ORB Class Name                            coldfusion.runtime.corba.VisibrokerConnector 
ORB Property File                            c:\ColdFusion9\runtime\cfusion\lib\vbjorb.properties 
Classpath                            [blank]

    ColdFusion includes the vbjorb.properties file, which contains the following properties that configure the ORB:

    org.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB 
org.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB 
SVCnameroot=namingroot