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
- A
const
in IDL maps to either a class or a static final variable depending on where the const
is declared in the IDL
- A
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
- An operation
in
parameter maps simply to a method
parameter
- An operation
out
or inout
parameter maps to a special holder class
- An attribute maps to two methods, a
get
method and a set
method
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.