CORBA26 — Inter-component type semantics unclear

The semantics of components of a particular type (session, entity)
residing in a compatible container type that access components of a
different type residing in a corresponding but different compatible
container type are unclear. Are there any expected or preferred
combinations? Are any disallowed or discouraged? See, for example, the
discussion under issue 4025 on automated recovery. In his replies, Mr.
Dubois seems to assume that entity components create transient (service
or session) components but not the reverse. In the telecommunications
domain, however, a session object may share access to an entity, and
then create additional entities based on external events, even though
the session itself is not persistent. Could someone please articulate
the possibilities and their utility (or lack thereof)?

rejected