BulkDataReceiverEx3Impl< TCallback > Class Template Reference
#include <bulkDataReceiverEx3Impl.h>
Inheritance diagram for BulkDataReceiverEx3Impl< TCallback >:
Collaboration diagram for BulkDataReceiverEx3Impl< TCallback >:
Public Member Functions | |
| BulkDataReceiverEx3Impl (const ACE_CString &name, maci::ContainerServices *containerServices) | |
| virtual | ~BulkDataReceiverEx3Impl () |
| void | cleanUp () |
template<class TCallback>
class BulkDataReceiverEx3Impl< TCallback >
Constructor & Destructor Documentation
template<class TCallback >
| BulkDataReceiverEx3Impl< TCallback >::BulkDataReceiverEx3Impl | ( | const ACE_CString & | name, | |
| maci::ContainerServices * | containerServices | |||
| ) |
template<class TCallback >
| virtual BulkDataReceiverEx3Impl< TCallback >::~BulkDataReceiverEx3Impl | ( | ) | [virtual] |
Member Function Documentation
template<class TCallback >
| void BulkDataReceiverEx3Impl< 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 >.
The documentation for this class was generated from the following file:
