Tell me the advantages of POA and disadvantages of BOA
Who is Participating?
cherch0rConnect With a Mentor Commented:
The intent of the POA is to provide an object adapter
that can be used with multiple ORB implementations with a minimum of rewriting needed to deal with different
vendors' implementations. However, most CORBA products do not yet support the POA.
The POA is also intended to allow persistent objects -- at least, from the client's perspective. That is, as far as the client is concerned, these objects are always alive, and maintain data values stored in them, even though physically, the server may have been restarted many times, or the implementation may be provided by many different object implementations.
The POA allows the object implementor a lot more control. Previously, the implementation of the object was                responsible only for the code that is executed in response to method requests. Now, additionally, the implementor has more control over the object's identity, state, storage, and lifecycle.

The POA has support for many other features, including the following:
Transparent object activation
Multiple simultaneous object identities
Transient objects
Object ID namespaces
Policies including multithreading, security, and object management
Multiple distinct POAs in a single server with different policies and namespaces
If you want to go into more details about the POA, look it up int he specifications at
As far as I know, the BOA (Basic Object Adaptor)  and the POA (Portable " " ) are both responsible for the management of CORBA objects. However the POA is newer and has much better control over all the settings of the objects behaviour. The API is the same for all the orbs and thus portable. With BOA the API was different for every orb and porting from one orb to another was tricky for complex CORBA applications.
All Courses

From novice to tech pro — start learning today.