Class MoverServer.ECproxyCallback
java.lang.Object
ecmwf.common.ectrans.DefaultCallback
ecmwf.ecpds.mover.MoverServer.ECproxyCallback
- All Implemented Interfaces:
ECtransCallback
- Enclosing class:
MoverServer
The Class ECproxyCallback.
-
Method Summary
Modifier and TypeMethodDescriptionvoidcheck()Check if the transmission was successful?.voidcompleted(TransferModule module) Completed.voidconnected(TransferModule module) Notifies that the module has connected and is now processing the requested action.voidexecutionFinished(TransferModule module, boolean successful) Optional evidence hook, also invoked when action cleanup prevents the ordinary terminal callback.voidfailed(TransferModule module, String comment) Failed.Methods inherited from class DefaultCallback
getECtransSetup, getUniqueName, isByteAccountingEnabled, retry, setByteCounter, setMSUser, transferredBytes
-
Method Details
-
connected
Description copied from interface:ECtransCallbackNotifies that the module has connected and is now processing the requested action. Called once, right beforeECtransAction.exec(TransferModule, boolean)starts, so implementations that need the liveTransferModuleinstance while a transfer is still in progress (e.g. to queryTransferModule.getConnectedRemoteAddress()for "Live ECPDS Earth") can capture it here. Default no-op for implementations that do not need it.- Parameters:
module- the module
-
executionFinished
Description copied from interface:ECtransCallbackOptional evidence hook, also invoked when action cleanup prevents the ordinary terminal callback. -
completed
Completed.- Specified by:
completedin interfaceECtransCallback- Overrides:
completedin classDefaultCallback- Parameters:
module- the module
-
failed
Failed.- Specified by:
failedin interfaceECtransCallback- Overrides:
failedin classDefaultCallback- Parameters:
module- the modulecomment- the comment
-
check
Check if the transmission was successful?.- Throws:
IOException- Signals that an I/O exception has occurred.
-