When you are given a system, either to implement or to access, it is very important to have well-defined interfaces between system elements.
Well-defined interfaces allow for solid encapsulation of implementation and modular development practices.
All you need in order to write part of a system are the interfaces to that part of the system and the interfaces to the other parts of the system that your part uses.
The language, patterns, and vendors you use from there on should be up to you, the implementer.
It is important to be able to see the interface in a common form and to know how to use it with respect to the language and vendor choices you have made.
In practical terms, to use an Interface Definition Language (IDL) interface, you must map the IDL interface to an interface, class, or whatever is appropriate in the chosen implementation language.
Some of these language mappings have been standardized by the Object Management Group (OMG). In this course, we will cover the OMG IDL mapping to Java.
In this module, we will cover the most basic elements of the mapping, mainly from the viewpoint of an application client implementer.
By the end of this module you will know how to:
Describe the mapping of an IDL module in Java
Describe the mapping of an IDL constant in Java
Describe the mapping of an IDL typedef in Java
Describe the mapping of interface operations with
inout parameters in Java
Describe the mapping of interface attributes in Java
In the next lesson, you will learn how to describe the mapping of an IDL module in Java.