Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.comm.interfaces
Interface IISeriesHostListSpoolFileFactory

All Superinterfaces:
IISeriesHostListBaseFactory
All Known Implementing Classes:
ISeriesHostListSpoolFileFactory

public interface IISeriesHostListSpoolFileFactory
extends IISeriesHostListBaseFactory

This interface defines a factory for creating new instances of classes which implement one of the spool list interfaces:

  • IISeriesHostSpoolFileNameOnly for just name requests
  • IISeriesHostSpoolFlieBasic for basic spool file information This is a special factory interface required for ISeriesListSpoolFiles. It allows you to have the list processor return your own objects directly versus getting an intermediate list and then mapping it.

    See Also:
    ISeriesHostSpoolFileNameOnly, ISeriesHostSpoolFileBasic

    Field Summary
    static String Copyright
               
     
    Method Summary
     IISeriesHostSpoolFileBasic createSpoolFileBasic()
              Return an instance of a class that implements the interface IISeriesHostSpoolFileBasic
     IISeriesHostSpoolFileNameOnly createSpoolFileNameOnly()
              Return an instance of a class that implements the interface IISeriesHostSpoolFileNameOnly
     

    Field Detail

    Copyright

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

    createSpoolFileNameOnly

    IISeriesHostSpoolFileNameOnly createSpoolFileNameOnly()
    Return an instance of a class that implements the interface IISeriesHostSpoolFileNameOnly


    createSpoolFileBasic

    IISeriesHostSpoolFileBasic createSpoolFileBasic()
    Return an instance of a class that implements the interface IISeriesHostSpoolFileBasic

    THIS IS THE SAME AS createObject()


    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.