CORBA26 — Component home interface inheritance

The definition of homes does not permit interface inheritance. It
appears this is an oversight as the omission seems unreasonable and
counter-intuitive, especially since homes must follow a parallel
derivation hierarchy with their component types. I have found cases in
which a home would expose the same interface as its component in which
the home subsequently delegates to a specific component instance (even a
persistent instance) however selected. (The component instance may or
may not be hidden from the client.) Interfaces are a perfect mechanism
whereby the operational signatures could be standardized, thus
eliminating potential errors caused by changing one but not the other.
This could be accomplished using a supports clause in the inheritance
specification similar to that of valuetypes.

see below