BulkDataReceiverEx2Impl< TCallback > Class Template Reference
#include <bulkDataReceiverEx2Impl.h>
Inheritance diagram for BulkDataReceiverEx2Impl< TCallback >:
Collaboration diagram for BulkDataReceiverEx2Impl< TCallback >:
Public Member Functions | |
| BulkDataReceiverEx2Impl (const ACE_CString &name, maci::ContainerServices *containerServices) | |
| virtual | ~BulkDataReceiverEx2Impl () |
| void | cleanUp () |
| virtual void | setParam (const CORBA::Any ¶m) |
| virtual void | myMethod () |
template<class TCallback>
class BulkDataReceiverEx2Impl< TCallback >
Constructor & Destructor Documentation
template<class TCallback>
| BulkDataReceiverEx2Impl< TCallback >::BulkDataReceiverEx2Impl | ( | const ACE_CString & | name, | |
| maci::ContainerServices * | containerServices | |||
| ) |
Constructor
- Parameters:
-
poa Poa which will activate this and also all other Components. name component name.
template<class TCallback>
| virtual BulkDataReceiverEx2Impl< TCallback >::~BulkDataReceiverEx2Impl | ( | ) | [virtual] |
Destructor
Member Function Documentation
template<class TCallback>
| void BulkDataReceiverEx2Impl< TCallback >::cleanUp | ( | ) | [virtual] |
Called after the last functional call to the component has finished. The component should then orderly release resources etc. If this method is overwritten in a subclass, the developer has to make sure that all cleanup performed by the implementation of the base class take place. The best way to do this is to call the implementation of the base itself explicitly, as would be done implicitly in a destructor chain.
- Returns:
- void
Reimplemented from BulkDataReceiverImpl< TCallback >.
template<class TCallback>
| virtual void BulkDataReceiverEx2Impl< TCallback >::myMethod | ( | ) | [virtual] |
template<class TCallback>
| virtual void BulkDataReceiverEx2Impl< TCallback >::setParam | ( | const CORBA::Any & | param | ) | [virtual] |
The documentation for this class was generated from the following file:
