alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl Class Reference

Inheritance diagram for alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl:

Collaboration diagram for alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl:

Public Member Functions
void	initialize (ContainerServices containerServices)
void	execute ()
void	cleanUp ()
void	aboutToAbort ()
ComponentStates	componentState ()
String	name ()
void	dummyInterface ()
Private Attributes
ContainerServices	m_containerServices
Logger	m_logger

Member Function Documentation

void alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl::aboutToAbort ( ) [inline]

Called when due to some error condition the component is about to be forcefully removed some unknown amount of time later (usually not very much...).

The component should make an effort to die as neatly as possible.

Because of its urgency, this method will be called asynchronously to the execution of any other method of the component.

Implements alma::acs::component::ComponentLifecycle.

References cleanUp().

void alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl::cleanUp ( ) [inline]

Called after the last functional call to the component has finished. The component should then orderly release resources etc.

Implements alma::acs::component::ComponentLifecycle.

Referenced by aboutToAbort().

ComponentStates alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl::componentState ( ) [inline]

References alma::acs::container::ContainerServices::getComponentStateManager(), and m_containerServices.

void alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl::dummyInterface ( ) [inline]

References m_logger.

void alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl::execute ( ) [inline]

Called after ComponentLifecycle#initialize(ContainerServices) to tell the component that it has to be ready to accept incoming functional calls any time.

Examples:

last-minute initializations for which initialize seemed too early
component could start actions which aren't triggered by any functional call, e.g. the Scheduler could start to rank SBs in a separate thread.

Must be implemented as a synchronous (blocking) call (can spawn threads though).

Implements alma::acs::component::ComponentLifecycle.

void alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl::initialize ( ContainerServices containerServices ) [inline]

Called to give the component time to initialize itself. For instance, the component could retrieve connections, read in configuration files/parameters, build up in-memory tables, ...

Called before execute(). In fact, this method might be called quite some time before functional requests can be sent to the component.

Must be implemented as a synchronous (blocking) call.

Parameters:

containerServices

callback object for services provided by the container

Implements alma::acs::component::ComponentLifecycle.

References alma::acs::container::ContainerServicesBase::getLogger(), m_containerServices, and m_logger.

String alma::lifecycleTest::TestLifeCycleCompImpl::TestLifeCycleCompImpl::name ( ) [inline]

References alma::acs::container::ContainerServicesBase::getName(), and m_containerServices.