alma.lifecycleTest.TestLifeCycleCompImpl

Class TestLifeCycleCompImpl

java.lang.Object

alma.lifecycleTest.TestLifeCycleCompImpl.TestLifeCycleCompImpl

All Implemented Interfaces:

ComponentLifecycle

public class TestLifeCycleCompImpl
extends java.lang.Object
implements ComponentLifecycle

Constructor Summary

Constructors

Constructor and Description
TestLifeCycleCompImpl()

Method Summary

Modifier and Type	Method and Description
void	aboutToAbort() 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...).
void	cleanUp() Called after the last functional call to the component has finished.
ComponentStates	componentState()
void	dummyInterface()
void	execute() Called after ComponentLifecycle.initialize(ContainerServices) to tell the component that it has to be ready to accept incoming functional calls any time.
void	initialize(ContainerServices containerServices) Called to give the component time to initialize itself.
java.lang.String	name()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

TestLifeCycleCompImpl

public TestLifeCycleCompImpl()

Method Detail

initialize

public void initialize(ContainerServices containerServices)

Description copied from interface: ComponentLifecycle

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 ComponentLifecycle.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.

Specified by:

initialize in interface ComponentLifecycle

Parameters:

containerServices - callback object for services provided by the container

execute

public void execute()

Description copied from interface: ComponentLifecycle

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).

Specified by:

execute in interface ComponentLifecycle

cleanUp

public void cleanUp()

Description copied from interface: ComponentLifecycle

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

Specified by:

cleanUp in interface ComponentLifecycle

aboutToAbort

public void aboutToAbort()

Description copied from interface: ComponentLifecycle

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.

Specified by:

aboutToAbort in interface ComponentLifecycle

componentState

public ComponentStates componentState()

name

public java.lang.String name()

dummyInterface

public void dummyInterface()