alma::test::corbareftest::component::HelloWorldImpl Class Reference

Inheritance diagram for alma::test::corbareftest::component::HelloWorldImpl:

Collaboration diagram for alma::test::corbareftest::component::HelloWorldImpl:

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

Detailed Description

A component for testing the persistence of CORBA references

Author:: acaproni

Member Function Documentation

void alma::test::corbareftest::component::HelloWorldImpl::aboutToAbort ( ) [inline]

Calls cleanUp). Override this method if the emergency situation of a container/component abort with unknown remaining lifetime requires a different strategy than the regular clean-up.

See also:: alma.acs.component.ComponentLifecycle::aboutToAbort()

Reimplemented from alma::acs::component::ComponentImplBase.

References cleanUp(), and m_logger.

void alma::test::corbareftest::component::HelloWorldImpl::cleanUp ( ) [inline]

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

Reimplemented from alma::acs::component::ComponentImplBase.

References m_logger.

Referenced by aboutToAbort().

ComponentStates alma::test::corbareftest::component::HelloWorldImpl::componentState ( ) [inline]

See also:: alma.ACS.ACSComponentOperations::componentState()

Reimplemented from alma::acs::component::ComponentImplBase.

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

void alma::test::corbareftest::component::HelloWorldImpl::displayMessage ( ) [inline]

void alma::test::corbareftest::component::HelloWorldImpl::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).

Reimplemented from alma::acs::component::ComponentImplBase.

References m_logger.

void alma::test::corbareftest::component::HelloWorldImpl::initialize ( ContainerServices containerServices ) [inline]

Subclass must call super.initialize(containerServices) unless it overrides as well all other methods which access the member vars of this class.