This is a feature of JBuilder Enterprise.
To open the Properties dialog for OrbixWeb IDL files, right-click on an IDL file in the project pane, and select Properties. In order for this dialog to display, first select OrbixWeb as the IDL Compiler from the Build page of the Project|Project Properties dialog box. The other IDL Compiler option is VisiBroker.
In order to compile the generated files, you must create and add a project class library that references the OrbixWeb class files to your project using the CORBA page of Tools|Enterprise Setup.
The OrbixWeb IDL Properties dialog 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 on an IDL file and selecting Run, 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.
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.
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.
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.
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)
#define name def
.
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.