| Previous | Table of Contents | Next |
The Common ORB Architecture is designed to allow interoperation with a wide range
of object systems (see Figure 2-9 on page 2-18). Because there are many existing
object systems, a common desire will be to allow the objects in those systems to be accessible via the ORB. For those object
systems that are ORBs themselves, they may be connected to other ORBs through the mechanisms described throughout this manual.
Figure 2-9 Different Ways to Integrate Foreign Object Systems
For object systems that simply want to map their objects into ORB objects and receive invocations through the ORB, one approach
is to have those object systems appear to be implementations of the corresponding ORB objects. The object system would register
its objects with the ORB and handle incoming requests, and could act like a client and perform outgoing requests.
In some cases, it will be impractical for another object system to act like a POA object implementation. An object adapter
could be designed for objects that are created in conjunction with the ORB and that are primarily invoked through the ORB.
Another object system may wish to create objects without consulting the ORB, and might expect most invocations to occur within
itself rather than through the ORB. In such a case, a more appropriate object adapter might allow objects to be implicitly
registered when they are passed through the ORB.