The refiner interface, that determines the functions that need to be
implemented to add various types of transfer nodes to the workflow.
The single in the name indicates that the refiner works with the
implementation that handles one file transfer per transfer job.
author: Karan Vahi author: Gaurang Mehta version: $Revision: 50 $
The overloaded constructor.
Parameters: dag - the workflow to which transfer nodes need to be added. Parameters: properties - the PegasusProperties object containing allthe properties required by Pegasus. Parameters: options - the options passed to the planner.
Loads the appropriate implementations that is required by this refinement
strategy for different types of transfer jobs. It calls to the factory
method to load the appropriate Implementor.
Loads the implementing class corresponding to the mode specified by the user
at runtime in the properties file. The properties object passed should not
be null.
Parameters: properties - the PegasusProperties object containing allthe properties required by Pegasus. Parameters: options - the options with which the planner was invoked. exception: TransferImplementationFactoryException - that nests any error thatmight occur during the instantiation.
Fields inherited from org.griphyn.cPlanner.transfer.AbstractRefiner