Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.subsystems.qsys.jobs
Interface IJobTicketSourceFactory

All Known Implementing Classes:
RBJobTicketSourceFactory

public interface IJobTicketSourceFactory

Interface for JobTicketSource factories. JobTicketSource factories are used by the JobTicketManager for persisting and restoring job tickets in a memento between workbench invocations. If a JobTicketSource wishes to be persisted and restored then a JobTicketSourceFactory needs to be registered via the com.ibm.etools.iseries.


Field Summary
static String Copyright
           
 
Method Summary
 IJobTicketSource createJobTicketSource(IMemento memento)
          Create an IJobTicketSource from this memento.
 String getFactoryID()
          Return the ID for this factory.
 void saveJobTicketSourceAttributes(IMemento memento, IJobTicketSource ticketSource)
          Save job ticket attributes that are unique to this job ticket source so the job ticket source can be restored at a latter time.
 

Field Detail

Copyright

static final String Copyright
See Also:
Constant Field Values
Method Detail

saveJobTicketSourceAttributes

void saveJobTicketSourceAttributes(IMemento memento,
                                   IJobTicketSource ticketSource)
Save job ticket attributes that are unique to this job ticket source so the job ticket source can be restored at a latter time.


createJobTicketSource

IJobTicketSource createJobTicketSource(IMemento memento)
Create an IJobTicketSource from this memento. This method will only be called for factory


getFactoryID

String getFactoryID()
Return the ID for this factory. This is used to lookup the factory via the jobticketsource extension point when the job ticket source needs to be restored.


Rational Developer for Power Systems Software
V7.6

Copyright 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.