CORBA Interface Definition Language (IDL) files are required in order to use another vendor’s ORB implementation class. EAServer Manager generates IDL files for components when you create or import them using EAServer Manager. Use the IDL-to-C++ compiler that comes with your ORB software to generate compatible stubs.
For information about which component IDL files and EAServer IDL files you need to use to generate stubs for other ORBs, see “Generating compatible Java stubs” (although this section refers to Java clients, it also applies to C++ clients).
Use the ORB vendor’s IDL-to-C++ compiler to generate stubs for the files in the table, “EAServer IDL files”. All IDL files are installed in the EAServer include subdirectory. “Writing CORBA C++ clients” describes how these interfaces are used to instantiate EAServer components and call component methods. For additional information, see the comments in each IDL file.
File name |
Description |
|---|---|
SessionManager.idl |
Defines interfaces for session-based creation of EAServer component instances. |
BCD.idl |
Defines the CORBA datatypes for EAServer’s binary and fixed-point numeric datatypes. |
MJD.idl |
Defines the CORBA datatypes for EAServer’s date and time datatypes. |
TabularResults.idl |
Defines the CORBA datatypes that represent result sets returned by a method invocation. |
EAServer provides C++ header files to convert from the EAServer CORBA datatypes to those commonly used in C++. “Supported datatypes” lists the datatypes displayed in EAServer Manager, the equivalent CORBA IDL types, and the C++ datatypes used in stub methods. If you are using another vendor’s ORB, use the EAServer header files in your application. For languages other than C++, see the comments in the IDL files for details on how the data is interpreted.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
