Automated Portable Object Adapter

Component implementations depend upon the standard CORBA Portable Object Adapter (POA) to dispatch incoming client requests to their corresponding servants. However, unlike previous versions of CORBA, the application developer is no longer responsible for creating the POA, the CCM component model implementation uses the component description to create and configure the POA hierarchy automatically and to locate the common services defined by CCM.

Often The Container and the ORB must interact

• Activate or deactivate component implementations to preserve limited system resources, such as main memory.

• Forward client requests to the four commonly used CORBA Object Services (COS): Transaction, Security, Persistent State, and Notification services, thereby freeing clients from having to locate these services.

• Provide adaptation layers for callbacks used by the container and ORB to inform the component about interesting events, such as messages from the Transaction or the Notification Service.

• Manage POA policies to determine how to create component references.