You can import interfaces defined in CORBA IDL into the EAServer interface repository. There are two ways to import a module:
Organize the modules so that one module is declared per file, and each file has the same name as the module it declares.
For example, module MyModule should be declared in the file MyModule.idl. Copy the files to the EAServer Repository subdirectory and restart the server. If the file contains no syntax errors, its declarations will be added to the EAServer Manager IDL folder. If the file does contain syntax errors, the server will log the errors during start-up and the module’s declarations will not be added to the IDL repository.
Create a new module in EAServer Manager, as described in “Creating and editing IDL modules, interfaces, and types”.
While the new module declaration is displayed in EAServer’s IDL editor, open the module to be imported in another text editor. Copy and paste the text of the module to be imported into the EAServer IDL editor.
To deploy IDL types and interfaces that are not declared within a module, place the IDL file that defines them in the EAServer Repository subdirectory and restart EAServer if it is running.
You can repeat the procedures above to redefine existing IDL definitions.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
