In this module, we looked at mapping from the most basic elements in IDL to their Java equivalents. You have seen how
- Modules map to packages
- Each primitive type in IDL has an equivalent in Java
const in IDL maps to either a class or a static final variable depending on where the
const is declared in the IDL
typedef is ignored in the mapping, and the underlying type is used
An operation in an IDL interface maps to a method in a Java interface
in parameter maps simply to a
inout parameter maps to a special holder class
An attribute maps to two methods, a
get method and a
We looked at how the client application uses these facts to invoke methods on existing servers. In the following modules, we will look at creating
servers, the mapping for more complicated types, and locating existing servers through a Naming Service.
The next module covers the mapping for IDL interfaces in detail. You will learn more about the Java interface and other classes that are
generated for each IDL interface, as well as how to implement a server object for an IDL interface.