These properties appear when you select a CORBA Settings subnode in the Projects Setting window.
Specifies what kind of code is generated for binding the client to a server.
When you are developing both the client and the server, use the same binding type for both the client and server sides. If you are developing a client that uses an existing server, you have to choose the type of binding that works with the server.
Sets up parameters (such as -I to specify a path to include files) to pass to the preprocessor in the IDL parser.
Specifies the object type whose definition is used at runtime.
Specifies whether the skeleton code generated from your IDL file is inheritance-based or tie-based.
class HelloImpl extends _HelloImplBase
class HelloImplTIE implements _HelloOperationsIn this case, a tie class, such as _HelloTie, establishes the relationship between the implementation class and the skeleton class.
Specifies what kind of implementation code is generated for operations (methods) declared in your IDL file:
Specifies whether the stubs and skeleton files generated by the IDL compiler are visible in the IDE.
Sets up any parameters you want to pass to the IDL compiler. Anything you type in this property is passed to the IDL compiler when it is executed.
Specifies what kind of code is generated on the server side for preparing a reference to the implementation instance or servant object:
The client side must use the same binding method. For example, if the server-side code registers the implementation instance or servant object with the naming service, the client must obtain its reference to the servant from the naming service.
Specifes how the IDE behaves when you modify an IDL definition. Depending on the setting, the IDE displays a dialog box that enables you to synchronize IDL and implementation.
After modifying an IDL interface definition you also need to recompile it to regenerate the stub and skeleton classes.
Enables you to protect portions of code that the CORBA module outputs with guarded (highlighted) blocks.
Specifies the number of the group returned by the Error Expression property that contains the column number of the offending code. If your IDL compiler does not return this information, or your Error Expression does not parse it, set this parameter to -1. A valid default value is supplied for each supported ORB product; you probably will not need to change the default.
Provides the switch passed on the command line to the IDL compiler. The switch indicates that the following entry is the directory in which the generated files should be stored. A valid default is supplied for each supported ORB product and its IDL compiler; you probably will not need to change the default.
Specifies a POSIX syntax regular expression that is used to parse the IDL compiler's error output. The expression sorts the compiler's output into groups for error message, column number, file name, and line number. A valid error expression is supplied for each supported ORB product; you probably will not need to change the default.
Specifies a string used to build a name for the generated class that serves as the base class for the implementation class. (In other words, the IDL compiler generates a class that the implementation class must extend.) Each ORB product has a naming convention for this base class. A valid default value is supplied for each supported ORB product; you probably will not need to change the default.
For example, most ORB products use a prefix of "_" and a postfix of ImplBase for the base classes they generate. If you compile an IDL interface named Hello with one of these ORB products, it generates a base class named _HelloImplBase. The actual implementation class is declared as extends_HelloImplBase.
See Extended Class Postfix. A valid default value is supplied for each supported ORB product; you probably will not need to change the default.
Identifies the IDL compiler for a specific ORB product. Type in the full path to the IDL compiler or, if the IDL compiler's directory is included in the operating system's PATH environment variable, just type in the executable's name.
Provides an integer value indicating which group in the Error Expression contains the file name of the IDL source file that produced errors. See Error Expression.
Specifies a string used to build a name for a generated implementation class to be used with inheritance-based skeletons. Each ORB product has a naming convention for this class. The IDE supplies a valid default value for each supported ORB product; you probably will not need to change the default.
For example, most ORB products use no prefix and a postfix of Impl for the implementation classes they generate. If you generate an implementation class for an IDL interface named Hello with one of these ORB products, it generates an implementation class named HelloImpl.
See Implementation Postfix. A valid default value is supplied for each supported ORB product; it is unlikely you will need to change it.
Specifies a string used to build a name for a generated tie interface to be used with tie-based skeletons. Each ORB product has a naming convention for this interface. A valid default value is supplied for each supported ORB product; you probably will not need to change the default.
For example, most ORB products use no prefix and a postfix of Operations for the implementation classes they generate. If you generate a tie interface for an IDL interface named Hello with one of these ORB products it generates an interface named HelloOperations.
See Implemented Interface Postfix. A valid default value is supplied for each supported ORB product; you probably will not need to change the default.
Provides an integer value indicating which group in the Error Expression contains the line number of the source code that the IDL compiler could not process. See Error Expression.
Provides an integer value indicating which group in the Error Expression contains the error message. See Error Expression.
Specifies the character used to separate package names in commands passed to the IDL compiler. This is the "." character (as in java.awt) for all currently supported ORB products.
Specifies the string that the IDL compiler recognizes as the command line switch. This switch is followed by the package name for files generated by the compiler.
Specifies a value for a template text tag. The templates contain text tags that are replaced when code is generated. These tags are delimited by two underscore characters on each side of them. The template table consists of entries such as USER=JOEUSER. Whenever __USER__ is encountered when the user creates a new class from the template, it is replaced by JOEUSER.
Specifies a string used to build a name for a generated implementation class for use with tie-based skeletons. Each ORB product has a naming convention for this class, and therefore a valid default value is supplied for each supported ORB product; you probably will not need to change the default.
For example, most ORB products use no prefix and a postfix of ImplTIE for the tie-based implementation classes they generate; if you generate a tie-based implementation class for an IDL interface named Hello with one of these ORB products it generates an implementation class name HelloImplTIE.
See Tie Implementation Postfix. A valid default value is supplied for each supported ORB product; you probably will not need to change the default.
Provides the line switch included on the command line to the IDE's Implementation Generator and tells the Implementation Generator to generate classes for use with a tie-based skeleton instead of an inheritance-based skeleton.
Specifies a string used to build a name for a generated implementation class for use with inheritance-based skeletons. Each ORB product has a naming convention for this class. A valid default factory value is supplied for each supported ORB product; you probably will not need to change the default.
For example, most ORB products use no prefix and a postfix of ValueFactoryImpl for the value factory implementation classes they generate. If you generate a value factory implementation class for an IDL interface named Hello with one of these ORB products, it generates an implementation class named HelloValueFactoryImpl. You can supply a postfix designator (for example, _M_) by entering the designation in the Value Factory Implementation Postfix property.
![]() |
If the postfix you designate does not appear, make sure that the ORB for Compilation property for your IDL corresponds to the same ORB for which you have set the postfix. Right-click the IDL file in the Explorer, click Properties in the contextual menu, and click the Compilation tab in the Properties window to verify the ORB. |
See Value Factory Implementation Postfix. A valid default value is supplied for each supported ORB product; you probably will not need to change the default. You can supply a prefix designator (for example, _M_) by entering the designation in the Value Factory Implementation Prefix property.
Specifies a string used to build a name for a generated implementation class for use with inheritance-based skeletons. Each ORB product has a naming convention for this class. A valid default value is supplied for each supported ORB product; you probably will not need to change the default.
For example, most ORB products use no prefix and a postfix of ValueImpl for the value implementation classes they generate. If you generate a value implementation class for an IDL interface named Hello with one of these ORB products, it generates an implementation class named HelloValueImpl. You can supply a postfix designator (for example, _M_) by entering the designation in the Value Implementation Postifx property.
![]() |
If the postfix you designate does not appear, make sure that the ORB for Compilation property for your IDL corresponds to the same ORB for which you have set the postfix. Right-click the IDL file in the Explorer, click Properties in the contextual menu, and click the Compilation tab in the Properties window to verify the ORB. |
See Value Implementation Postfix. A valid default value is supplied for each supported ORB product; you probably will not need to change the default. You can supply a postfix designator (for example, _M_) by entering the designation in the Value Implementation Prefix property.