Babel supports calls to SIDL classes implemented in Java. These
classes obey the same rules described in Subsection 10.3.1
for client-side Java classes, except
that in this case the file, class, and method names all end in _Impl.
Implementation of a set of SIDL classes in Java first requires the
generation of the necessary bindings. This is accomplished by invoking
Babel as follows
% babel -exclude-external -server=Java file.sidlor simply
% babel -E -sJava file.sidl
The directory structure that results from this command is the same as that produced on the client-side except there are many more files. Given the SIDL file is named ``file.sidl'', as above, a file subdirectory is created and ``Impl'' files (i.e., those ending in _Impl.java) are automatically generated in that subdirectory. These Java ``Impl'' files are supposed to contain implementation details. Refer to Subsection 10.4.2 for details.
In the current directory there are also new files that end in _jniSkel.c. These files are equivalent to the client-side _jniStub.c. In fact, all client-side files are generated from this call as well to allow for calling methods on the current object in the Java ``Impl'' file. Consequently, they can safely be ignored.