Overview  Package   Class  Tree  Serialized  Deprecated  Index  Help 
Rational Developer for Power Systems Software
V7.6
 PREV CLASS   NEXT CLASS FRAMES    NO FRAMES    
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD

com.ibm.etools.iseries.services.qsys.api
Interface IQSYSFileFieldFactory

All Superinterfaces:
IISeriesHostListBaseFactory, IISeriesHostListFieldFactory
All Known Implementing Classes:
QSYSHostFileFieldFactory, QSYSRemoteFileFieldFactory
public interface IQSYSFileFieldFactory
extends IISeriesHostListFieldFactory

Factory for creating field objects.

Field Summary
static String copyright
           
 
Fields inherited from interface com.ibm.etools.iseries.comm.interfaces.IISeriesHostListFieldFactory
Copyright
 
Method Summary
 IQSYSFileField createFieldObject()
          Return an instance of a class that implements the interface IISeriesHostFieldBasic
 IQSYSFileField createNameOnlyObject()
          Return an instance of a class that implements the interface IISeriesHostFieldNameOnly
 

Field Detail

copyright

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

createNameOnlyObject

IQSYSFileField createNameOnlyObject()
Return an instance of a class that implements the interface IISeriesHostFieldNameOnly

Specified by:
createNameOnlyObject in interface IISeriesHostListFieldFactory

createFieldObject

IQSYSFileField createFieldObject()
Return an instance of a class that implements the interface IISeriesHostFieldBasic

Specified by:
createFieldObject in interface IISeriesHostListFieldFactory
Overview  Package   Class  Tree  Serialized  Deprecated  Index  Help 
Rational Developer for Power Systems Software
V7.6
 PREV CLASS   NEXT CLASS FRAMES    NO FRAMES    
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD
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.