There are two ways of generating the stub, skeleton, and protocol code for a CORBA application. We can either run the IDL compiler on the command-line, or we can run it within the Functional Developer development environment. The second option is more convenient given that we are already using the environment.
Simply building the project in the normal way is enough to invoke the IDL compiler. This convenience is thanks to the spec file in the project Sources list: when the build gets to the spec file, the build system looks in it to see what to do with it. The spec file in My-Hello-World-Client states with the
Idl-File: keywords that there is a OMG IDL file to compile, and with the
Stubs: keyword that a project containing client stub code should be generated.
If we build My-Hello-World-Client now, the IDL compiler will read the IDL file and create the stubs code. Meanwhile the rest of the Dylan code in the project is also compiled.
The spec file in My-Hello-World-Server is similar, but asks for skeletons instead of stubs.
After the build, each project's Sources page is updated to include new subprojects. The subprojects are as follows.
In the client project:
In the server project:
In addition, a protocol subproject appears in both the stubs and the skeletons projects: