A «CORBAInterface» class that has both children and relations leads to the generation, compilation, and linkage of both server-side and client-side code.
IBM® Rational® Rhapsody® generates both server and client IDL code for the CORBA interface IServer and, in this case, keeps both. The Client class, which has an association relation to IServer, links to IServer's client-side (stub) code. The Server class, which inherits from IServer, links to IServer's server-side (skeleton) code. Therefore, if you allocate the classes to components (as described in the Hello World example), you end up with two applications (Client.exe and Server.exe) that share the CORBA interface.
Rational Rhapsody cannot interpret a CORBA interface that does not have children or relations. Therefore, nothing (stub or skeleton code) is generated for it. You can force stub or skeleton generation using the ExposeCorbaInterfaces and UseCorbaInterfaces properties (under CORBA::Configuration). See Interpreting CORBA interfaces for details.