
Since C++ is a different language to Java, it knows nothing about J2EE technologies such as EJB, or the Java types. Since you use these Java classes in your server-side application, you have to "translate" them into C++ for the client-side application. You do this using the language-neutral IDL representation of the CallbackApplication.
To generate the IDL files, use the command-line rmic tool that is distributed with you JDK installation. You run this command against the Notificator.java, UtilCallback.java and UtilCallbackHome.java interfaces from the server-side application.
| Source File Name | Classpath to Set |
|---|---|
|
Notificator |
<IDE_install_dir>\workspace\UtilCallback\UtilCallback.jar |
|
UtilCallbackHome |
<IDE_install_dir>\workspace\UtilCallback\UtilCallback.jar <IDE_install_dir>\plugins\com.tssap.ext.libs.j2ee_1.3\lib\ejb20.jar |
|
UtilCallback |
<IDE_install_dir>\workspace\UtilCallback\UtilCallback.jar <IDE_install_dir>\plugins\com.tssap.ext.libs.j2ee_1.3\lib\ejb20.jar |
If you are not confident about using the rmic command syntax, execute rmic -h to read the help provided with the command.
After you execute the command against each of the interfaces mentioned above, you will have the necessary IDL files that represent the CallbackApplication's classes. Regardless of the fact that you have run the command against only three classes, many more IDL files are generated. This is because the rmic tool searches through the inheritance chain that occurs in the source classes and generates an IDL representation of each match.