Java Source Properties

This is a feature of JBuilder Professional and Enterprise.

To open the Properties dialog for Java file, right-click on a Java file in the project pane, and select Properties.

Build tab

This page of the dialog enables you to determine what type of stubs and skeletons will be generated when this file is compiled. Stubs and skeletons are used in distributed object computing. For more information on distributed object computing, see the Distributed Application Developer's Guide.

The type of Java file that will generate Java interface definitions and Java client stubs and server skeletons are interface files. The interface file defines the services offered by a particular distributed object. The interfaces can be defined in the Java programming language or in Interface Definition Language (IDL).

See "Exploring RMI-based distributed applications" in the Distributed Application Developer's Guide for more information.

RMI/JNI page

RMI Compiler Settings

Generate RMI Stub/Skeleton

The Generate RMI Stub/Skeleton option generates remote method invocation (RMI) for communicating between two machines running Java code. This allows code on the client computer to invoke a method on an object on the server. In this environment, the computer that is running the Java code that calls the remote method is the client for only that call - the computer hosting the object that processes the call could be the server for another call at another time. Java RMI provides a way to transparently connect Java clients to network servers.

When this option is selected and the project is compiled, the following files are generated:

See "Exploring RMI-based distributed applications" in the Distributed Application Developer's Guide for more information.

Options

Enter any command line options here. See the sun.java.com Web site for more information on RMI command line options.

JNI Compiler settings

Generate JNI Header File

Generates Java Native Interface (JNI) header files when the project is compiled.

Options

Enter any command line options here. See the sun.java.com Web site for more information on JNI command line options.

VisiBroker page

The VisiBroker page displays when VisiBroker is selected in the Project|Project Properties dialog as the IDL Compiler on the Build page.

Java2IDL Settings

Generate IDL

Selecting this option, and clicking OK, generates an Interface Definition Language (IDL) file from a Java file or a class file. To support the distribution of objects implemented in a variety of programming languages, an IDL file is used to define the services offered by a particular distributed object.

You could use a Java interface or class file instead of an IDL file to create an interface that is Internet InterORB (Object Request Broker) Protocol (IIOP) compliant using by selecting Generate IIOP. For more information on developing distributed objects using JBuilder, see the Distributed Application Developer's Guide. See "Generating IDL interfaces from Java" for more information on generating IDL interfaces from a Java interface.

Options

Enter any command line options here. See the VisiBroker for Java Reference Guide for command line options.

Java2IIOP Settings

Generate IIOP

The Generate IIOP Interface option generates an Internet InterORB (Object Request Broker) Protocol (IIOP) compatible Java interface file from a Java interface or class file. This is done by creating a new Java interface that extends org.omg.Corba.object. This Java interface can be used to describe CORBA interfaces in place of using an Interface Definition Language (IDL) file to describe the interfaces. The IIOP protocol maintains a basic set of functionality to ensure inter-operability between client applications and server-based objects in a Common Object Request Broker Architecture (CORBA) architecture.

See "Generating IIOP interfaces" for more information on generating IIOP interfaces from a Java interface.

Strict Portable Code Generation

This option is available when Generate IIOP Interface is selected. When selected, this option enables generation of portable stubs, meaning stubs that contain code that is not specific to VisiBroker.

Generate Example Implementation

This option is available when Generate IIOP Interface is selected. When selected, this option enables generation of example implementation code.

Generate Tie Bindings

This option is available when Generate IIOP Interface is selected. When selected, this option enables generation of -tie classes.

Generate Comments

This option is available when Generate IIOP Interface is selected. When selected, this option enables generation of comments in the source code.

Options

Enter any command line options here. See the VisiBroker for Java Reference Guide for command line options.

OK button

Saves these properties so that they can be used when the project is compiled.

Cancel button

Exits the dialog and does not save the properties.