The next step is to run the IDL compiler to generate language-specific source files that will implement the object, stubs and skeletons. Each ORB vendor supplies an IDL compiler; and each compiler works a little bit differently. Don't let that worry you, though: as long as there is IDL and IIOP, the objects created by different ORB development environments will be compatible with each other.
Anyway, this page shows running the IDL compiler that's part of JDK 1.2. It generates the following files: _MeetingStub.java, which implements the stub, Meeting.java which defines the remote interface as a Java interface, MeetingHolder.java and MeetingHelper.java, which implement some extra classes that help clients use the remote object and _MeetingImplBase.java. This last file has two jobs: first, it implements the skeleton for the remote object, and second, it provides a superclass which we can extend to write the remote object's implementation.
You don't really need to understand the code inmost of these source files; the only one that's really worth reading is Meeting.java, shown on this page, which defines a Java interface. Note that this Java interface extends a CORBA-defined interface, and includes three methods:a "getter" and a "setter" for the "date" attribute, and the "scheduleIt" method. Our next job will be to implement these methods.
One other note: as of this writing, the idltojava compiler is not included with the JDK. Instead, you must download it separately from the www.javasoft.com web site. See the JDK documentation for more details.