Remote Systems
v6.4.1

com.ibm.etools.systems.universalfilesubsys
Interface UniversalfilesubsysFactory

All Known Implementing Classes:
UniversalfilesubsysFactoryImpl

public interface UniversalfilesubsysFactory

The Factory for the model. It provides a create method for each non-abstract class of the model.

See Also:
UniversalfilesubsysPackage

Field Summary
static String copyright
           
static UniversalfilesubsysFactory eINSTANCE
          The singleton instance of the factory
 
Method Summary
 UniversalFileSubSystem createUniversalFileSubSystem()
          Returns a new object of class 'Universal File Sub System'
 UniversalFileSubSystemFactory createUniversalFileSubSystemFactory()
          Returns a new object of class 'Universal File Sub System Factory'
 UniversalfilesubsysPackage getUniversalfilesubsysPackage()
          Returns the package supported by this factory
 

Field Detail

copyright

public static final String copyright

See Also:
Constant Field Values

eINSTANCE

public static final UniversalfilesubsysFactory eINSTANCE
The singleton instance of the factory.

Method Detail

createUniversalFileSubSystemFactory

public UniversalFileSubSystemFactory createUniversalFileSubSystemFactory()
Returns a new object of class 'Universal File Sub System Factory'.

Returns:
a new object of class 'Universal File Sub System Factory'.

createUniversalFileSubSystem

public UniversalFileSubSystem createUniversalFileSubSystem()
Returns a new object of class 'Universal File Sub System'.

Returns:
a new object of class 'Universal File Sub System'.

getUniversalfilesubsysPackage

public UniversalfilesubsysPackage getUniversalfilesubsysPackage()
Returns the package supported by this factory.

Returns:
the package supported by this factory.

Remote Systems
v6.4.1

Copyright © 2005 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.