Java Source Properties

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

IMPORTANT: Be sure to use the scroll bar to the right of the dialog to access all options.

Distributed objects are objects that can be accessed remotely. This means that a distributed object can be used like a regular object, but from any machine on the network. The physical location of the object is not critical to the user of the object. To distribute Java objects in JBuilder, see Developing distributed applications for a detailed explanation.

The interface file is used to generate Java interface definitions and Java client and server stubs. To support the distribution of objects implemented in a variety of programming languages, this interface file is used to define the services offered by a particular distributed object. You can define the interface for the CORBA object in either IDL or Java, as follows:

The Generate RMI stub/skeleton option generates Java Remote Method Invocation (RMI) stubs and skeletons from a Java file. Java RMI is an alternative to CORBA for creating distributed applications in an all-Java environment. See Developing distributed applications for more information.

VisiBroker 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 Interface. For more information on distributed objects in JBuilder, see Developing distributed applications.

Generate IIOP Interface

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 interoperability between client applications and server-based objects in a Common Object Request Broker Architecture (CORBA) architecture.

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.

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:

For more information on developing distributed applications in Java RMI, see Creating distributed applications using Java RMI.

Generate JNI Header File

Generates JNI header files when the project is compiled.

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.