This is a feature of JBuilder Professional and Enterprise.
To open the Properties dialog box for a file, right-click a file in the project pane, and select Properties.
The Build page of this dialog box allows you to define what files are copied to the output path when JBuilder compiles. It also enables you to determine what type of stubs and skeletons are 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.
Use this page to set options for the RMI and JNI compilers.
Sets RMI and JNI compiler options.
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:
*Stub.java
file. The stub file contains the stub code that will perform the marshalling.*Skeleton.java
file. The skeleton file contains the dispatch for the RemoteObject
.*Marshaller.java
files. These files are marshaller classes for all the non-Remote
objects that need to be marshalled.See "Exploring RMI-based distributed applications" in the Distributed Application Developer's Guide for more information.
Enter any command line options here. See the sun.java.com Web site for more information on RMI command line options.
Sets options for the JNI compiler.
Generates Java Native Interface (JNI) header files when the project is compiled.
Enter any command line options here. See the sun.java.com Web site for more information on JNI command line options.
The VisiBroker page is displayed when VisiBroker is selected as the IDL compiler on the Build page of the Project|Project Properties dialog box.
Sets options for the java2idl
compiler.
Select this option to generate 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 "Working with the java2idl compiler" for more information on generating IDL interfaces from a Java interface.
Enter any command line options here. See the VisiBroker for Java Reference Guide for command line options.
Sets options for the java2iiop
compiler.
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.
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.
This option is available when Generate IIOP Interface is selected. When selected, this option enables generation of example implementation code.
This option is available when Generate IIOP Interface is selected. When selected, this option enables generation of -tie classes.
This option is available when Generate IIOP Interface is selected. When selected, this option enables generation of comments in the source code.
Enter any command line options here. See the VisiBroker for Java Reference Guide for command line options.
JBuilder copies all known resource types from the source path to the output path during the compile process. By default, JBuilder recognizes all images, sound, and properties files as resources and copies them to the output path. You can override these default resource definitions on individual files or by file extension project wide. See "Setting the output path" for more information on the output path.
On the Build page of the Properties dialog box you can set individual files as resources, as well as set project-wide resources by file extension.
You can access the Resource tab on the Build page two ways:
There are two groups of radio buttons that have different results:
Copies selected file(s) to the output path. The Copy option selects an absolute behavior: always copy to the output path when the project is built, regardless of whether or not the file type is considered a resource.
If you changed the defaults for individual files and you want to return them to the project defaults as specified in the Project-wide Defaults By Extension list, select the files again and choose Use File Extension Defaults.
If the selected files or extensions do not all share the same setting, none of the radio buttons in the corresponding group are selected. Selecting one of the radio buttons changes everything to the same value, while leaving none selected allows the differing values to be left alone.
Does not copy the selected file(s) to the output path. The Do Not Copy option selects an absolute behavior: never copy to the output path when the project is built, regardless of whether or not the file type is considered a resource.
If you changed the defaults for individual files and you want to return them to the project defaults as specified in the Project-wide Defaults By Extension list, select the files again and choose Use File Extension Defaults.
If the selected files or extensions do not all share the same setting, none of the radio buttons in the corresponding group are selected. Selecting one of the radio buttons changes everything to the same value, while leaving none selected allows the differing values to be left alone.
Copies all files based on their file extension to the output path that are labeled Copy
in the Project-wide Defaults By Extension list.
File types that are labeled Do Not Copy
are never copied to the output path on compilation.
This is the default behavior for all newly created files and files in the current project. The correct extensions for the files currently selected in the project pane are automatically
selected in the list to highlight the default behavior. The default settings for the project can be changed in the Project-wide Defaults By Extension section.
These options are project wide and control what is copied to the output path by file extension. Select a file type in the Project-wide Defaults By Extension list and choose Copy or Do Not Copy. For example, if html
is changed from Do Not Copy
to Copy
in the Project-wide Defaults By Extension list, then all HTML files in the project are copied to the output path during compilation.
Copies all files of the selected type to the output path.
Does not copy any files of the selected type to the output path.
Use the Reset button to return all files in the file extension list to the state they were in when the dialog box was displayed. Remember, this does not change your individual file settings to the default.