Generating Stub for the Notificator Object
Since the UtilCallback bean calls methods of the remote callback object (that is, it behaves like a client to this object), the server-side application must contain the corresponding stub that will carry out the actual communication with the remote object. The callback object's implementation resides on the remote system but it is defined by the remote Notificator interface. Therefore, you must generate the stub against the Notificator class from the UtilCallback project in your Developer Studio.
We use the standard rmic tool that is distributed with the Java Development Kit (JDK) software that you have installed.
You must execute the rmic.exe file that is located in the <jdk_install_dir>\bin directory in a command prompt with the following options:
- Use the -classpath option to add the path to the Notificator class. In this case, it is located in <Developer_Studio_dir>\workspace\UtilCallback\ejbModule.
- Use the -iiop option to instruct the tool to generate IIOP-based communication support.
- Use the -nolocalstubs option to generate stubs that are not optimized for local communication.
- Use the -keep option to keep the java source file of the stub (otherwise you will get only the compiled class file.) You will later use the generated .java file to import the stub to the UtilCallback project in your Developer Studio.
- This option is not mandatory. You can use the -d option to specify the directory where you want the generated stub to be saved.
- At the end of the command line, enter the fully-qualified name of the class you run the rmic tool against. In this case, it is examples.iiop.Notificator .
If you have correctly performed all of the above steps, the rmic tool has generated the _Notificator_Stub.java file in the directory that you entered with the -d option.