Chapter 15 Creating CORBA C++ Clients

Generating stubs

The EAServer ORB implementation class requires stub header files in order to invoke component methods. You generate the stub header files with Jaguar Manager and include them in your client source files. The stub header files contain as inline all the component functions, which make calls to the C functions in libjcc.dll. Inline functions allow EAServer to support multiple C++ compilers without having to include separate link libraries for each compiler.

If you are using another ORB implementation class to connect to EAServer, you must export IDL and use the vendor's IDL compiler to generate stubs that are compatible with that ORB implementation. "Using CORBA ORB implementations other than EAServer" describes how to export IDL files for EAServer components.

Procedure for generating stubs

You can generate stub header files from Jaguar Manager as follows:

Highlight a component, package, or module as follows:
- Highlight a component to generate stubs for all interfaces and types required by a component,
- Highlight a package to generate all stubs needed by components in the package, or
- Highlight a module to generate stubs for IDL interfaces and types defined within that module.
Select File | Generate Stub/Skeleton. The Generate Stubs & Skeletons dialog is displayed.
Select the Generate Stubs check box. Unselect Generate Skeletons unless you want to generate stubs at the same time. Enter the C/C++ and Java code base values in the Stubs Generation Options area.
- Code Base - enter the top-level directory path where generated files should be created. When the window displays, the default is the EAServer include subdirectory.
  
  You can type a different path or use the Browse button to select a directory. The path must be a valid UNIX or Windows path. It can include a drive and as many directories as you want. The only shell aliases allowed in this field are %JAGUAR% (for Windows) and $JAGUAR (for UNIX).
  
  If you clear the field, the default is your home directory (specified by $HOME for UNIX and %home% for Windows).
  
  If you specify a relative path, the path is interpreted relative to the EAServer html/classes directory.
Click the Generate button.