Components::CCMObject Interface Reference

import "CCM_Object.idl";

Inheritance diagram for Components::CCMObject:

Inheritance graph
[legend]
Collaboration diagram for Components::CCMObject:

Collaboration graph
[legend]
List of all members.

Public Member Functions

CORBA::IRObject get_component_def ()
CCMHome get_ccm_home ()
PrimaryKeyBase get_primary_key () raises (NoKeyAvailable)
void configuration_complete () raises (InvalidConfiguration)
void remove () raises (RemoveFailure)
ComponentPortDescription get_all_ports ()
StandardConfigurator get_standard_configurator ()
void ciao_preactivate () raises (InvalidConfiguration)
void ciao_activate () raises (InvalidConfiguration)
 CIAO specific.
void ciao_postactivate () raises (InvalidConfiguration)
 CIAO specific.
void ciao_passivate () raises (InvalidConfiguration)
 CIAO specific.

Member Function Documentation

void Components::CCMObject::ciao_activate (  )  raises (InvalidConfiguration)

CIAO specific.

void Components::CCMObject::ciao_passivate (  )  raises (InvalidConfiguration)

CIAO specific.

void Components::CCMObject::ciao_postactivate (  )  raises (InvalidConfiguration)

CIAO specific.

void Components::CCMObject::ciao_preactivate (  )  raises (InvalidConfiguration)

This is all from our work on ARMS where we needed to know whether every component has been configured, say for example to use logging in the assembly which could in turn be provided by a component. To get around all this we are adding some methods on this till we think of some standard way to do this. The problem is that the deployer should be able to call this as opposed to the home calling it as soon as the component is created.

All these operations are called in the order mentioned, ie. the deployer calls ciao_preactivate () on all components, then ciao_activate and then ciao_postactivate (). The speciality is that these operations would be invoked on every target object before the next call is made. It is similar to the way portable interceptors work, trying to get everything onto the flow stack, but differ in the intention.

void Components::CCMObject::configuration_complete (  )  raises (InvalidConfiguration)

ComponentPortDescription Components::CCMObject::get_all_ports (  ) 

CCMHome Components::CCMObject::get_ccm_home (  ) 

CORBA::IRObject Components::CCMObject::get_component_def (  ) 

PrimaryKeyBase Components::CCMObject::get_primary_key (  )  raises (NoKeyAvailable)

StandardConfigurator Components::CCMObject::get_standard_configurator (  ) 

Factory method to return a StandardConfigurator interface. CIAO specific

void Components::CCMObject::remove (  )  raises (RemoveFailure)


The documentation for this interface was generated from the following file:
Generated on Mon Apr 30 23:49:34 2007 for CIAO by  doxygen 1.4.7-1