superclass, ACSComponent. More...

#include <CounterConsumerImpl.h>

Inheritance diagram for CounterConsumerImpl:

Collaboration diagram for CounterConsumerImpl:

Public Member Functions
	CounterConsumerImpl (const ACE_CString &name, maci::ContainerServices *containerServices)
virtual	~CounterConsumerImpl ()
virtual void	getBlocks ()
virtual CORBA::Long	waitTillDone ()
Static Private Member Functions
static void	counterDataHandler (COUNTER::statusBlockEvent s, void *p)
Private Attributes
int	m_eventCount
bool	contFlag
nc::SimpleConsumer < COUNTER::statusBlockEvent > *	m_CounterConsumer_p

Detailed Description

superclass, ACSComponent.

This is the CORBA stub client header for ACSErrTypeCommon.idl where the definition of the CORBA exception is found. The empty CORBA servant interface, POA_COUNTER::CounterConsumer, is obtained from this header file and is automatically generated from COUNTER's Interface Definition File (i.e., contNcTest_IF.idl) by CORBA. All components should inherit from CharacteristicComponentImpl or it's superclass, ACSComponentImpl, to remain compatiable with ACS tools such as objexp (i.e., a GUI used to manipulate components). This class also derives from POA_COUNTER::CounterConsumer which is a class automatically generated by CORBA from COUNTER's IDL file.

Version:: "@(#) $Id: CounterConsumerImpl.h,v 1.3 2008/10/07 09:41:42 cparedes Exp $"

Constructor & Destructor Documentation

CounterConsumerImpl::CounterConsumerImpl	(	const ACE_CString &	name,
		maci::ContainerServices *	containerServices
	)

Constructor

Parameters:

	poa	Poa which will activate this and also all other components. Developers need not be concerned with what a PortableServer does...just pass it to the superclass's constructor.
	name	component's name. All components have a name associated with them so other components and clients can access them.

virtual CounterConsumerImpl::~CounterConsumerImpl ( ) [virtual]

Destructor