This is a feature of JBuilder Enterprise.
To open the Properties dialog box for OrbixWeb IDL files, right-click an IDL file in the project pane, and select Properties. In order for this dialog box to display, select OrbixWeb as the IDL Compiler on the Build page of the Project|Project Properties dialog box.
In order to compile the generated files, you must create and add a project class library to your project that references the OrbixWeb class files. Use the CORBA page of Tools|Enterprise Setup to do this.
To learn more about developing distributed object applications using JBuilder, see the Distributed Application Developer's Guide. For information on creating a CORBA application with interfaces defined in IDL, see "Exploring CORBA-based distributed applications in JBuilder".
For more information about OrbixWeb, see its documentation.
The Build Properties dialog box for OrbixWeb IDL enables you to specify options for compiling remote interfaces defined in the Interface Definition Language (IDL). When an IDL file is compiled, it generates Java interface definitions and Java client stubs and server skeletons. This allows a Java client to transparently invoke an IDL object that resides on a remote server or allows a Java server to define objects that can be transparently invoked from IDL clients.
When the IDL compiler is invoked by right-clicking an IDL file and selecting Make or Rebuild, the IDL source file is compiled, and a directory structure containing the Java mappings for the IDL declarations is created. Typically, one IDL file will be mapped to many Java files that marshall/unmarshall Java data types to CORBA types and provide IIOP messaging. IDL file names must end with the .idl
extension.
When this option is selected, you can set compiler options, add the compiled files and/or packages to the current project, and view compiler output.
When the option is on, selecting OK sets the options to be used by the OrbixWeb tool when the IDL file is compiled. Set the correct options so that when compiled, Java interface definitions and Java client and server stubs and skeletons are generated.
When the Process This IDL File option is not checked, selecting OK saves the selected options, but does not call the OrbixWeb compiler when the IDL file is compiled. This means that the client stubs and server skeletons are not generated when the IDL file is compiled.
The first step to creating an application of this type to specify all of your objects and their interfaces using the OMG's Interface Definition Language (IDL). The IDL can be mapped to a variety of programming languages.
The interface specification you created is used to generate stub routines for the client program and skeleton code for the object implementation. The stub routines are used by the client program for the method invocations. You use the skeleton code, along with code you write, to create the server that implements the object. The code for the client and object, once completed, is used as input to your Java compiler to produce a Java applet or application and an object server.
This page provides options for modifying the Java source code generated when an IDL source file is compiled. By default, an IDL source file is compiled, and a directory structure containing the Java mappings for the IDL declarations is created. Typically, one IDL file will be mapped to many Java files because Java allows only one public interface or class per file.
Generates code in the specified package. The package name for definitions is prepended with the specified package name. If a directory with the specified package name does not exist, it will be created. If the package directory exists, its contents will be updated. (Equivalent to the -jP IDL.EXE
flag)
Select this option to allow comments. Unselect this option to filter out comments. (Equivalent to the -c IDL.EXE
flag)
Select this option to specify that per-object filtering code will be generated. (Equivalent to the -F IDL.EXE
flag)
Select this option to specify that only code that is compliant with the Object Management Group (OMG) CORBA specifications will be generated. When selected, code that includes OrbixWeb functionality is not generated. (Equivalent to the -jOMG IDL.EXE
flag)
When selected, runs the IDL pre-processor only. (Equivalent to the -E IDL.EXE
flag)
When selected, provides support for the equals()
method in generated code. (Equivalent to the -jQ IDL.EXE
flag)
When selected, and the files are compiled, generates only the client-side (stubs) code. When unselected, both client and server-side code is generated. (Equivalent to the -jc IDL.EXE
flag)
Click the ellipsis button to open a dialog box that allows you to select a directory to be searched for the list of files to include in the build. You must select a directory that contains an .idl file. (Equivalent to the -I IDL.EXE
flag)
This field allows you to specify options that are not available in this dialog box. For a list of possible options, see the OrbixWeb documentation.
Specifies whether to generate marshalling code for InterORB Object Protocol (IIOP). Default is to generate code that support both IIOP and OrbixWeb protocol. (Equivalent to the -m IDL.EXE
flag)
This page displays a list of symbols defined for conditional IDL compilation. Click New to add a new symbol, click Delete to delete the highlighted symbol.
Opens a dialog box that enables you to define a symbol name for conditional IDL compilation, for example #define name def
.
This button enables you to delete the selected symbol from the list of symbols defined for conditional compilation.
When the Process This IDL File option is checked, selecting OK sets the options to be used by the OrbixWeb tool when the IDL file is compiled. Set the correct options so that when compiled, Java interface definitions and Java client and server stubs and skeletons are generated in a subdirectory of the project with the same name as the project.
When the Process This IDL File option is not checked, selecting OK saves the selected options, but does not call the OrbixWeb compiler when the IDL file is compiled. This means that the client stubs and server skeletons are not generated when the IDL file is compiled.