Remote Systems
v6.4.1

com.ibm.etools.systems.universal.util
Class UniversalLanguageUtilityFactory

java.lang.Object
  extended bycom.ibm.etools.systems.subsystems.util.AbstractLanguageUtilityFactory
      extended bycom.ibm.etools.systems.universal.util.UniversalLanguageUtilityFactory
All Implemented Interfaces:
ILanguageUtilityFactory

public class UniversalLanguageUtilityFactory
extends AbstractLanguageUtilityFactory

This is a singleton factory class associated each universal subsystem.


Field Summary
 
Fields inherited from class com.ibm.etools.systems.subsystems.util.AbstractLanguageUtilityFactory
subsystem
 
Method Summary
static ILanguageUtilityFactory getInstance(RemoteFileSubSystem subsystem)
          Returns an instance for each subsystem.
 ILanguageUtility getUtility(String language)
          For Java, subclasses should return an instance of IJavaLanguageUtility
 
Methods inherited from class com.ibm.etools.systems.subsystems.util.AbstractLanguageUtilityFactory
getSubSystem
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Method Detail

getInstance

public static ILanguageUtilityFactory getInstance(RemoteFileSubSystem subsystem)
Returns an instance for each subsystem. Note that there is just a singleton instance for each universal subsystem.

Parameters:
subsystem - the universal subsystem.
Returns:
the singleton instance associated with the subsystem.

getUtility

public ILanguageUtility getUtility(String language)
Description copied from class: AbstractLanguageUtilityFactory
For Java, subclasses should return an instance of IJavaLanguageUtility

Specified by:
getUtility in interface ILanguageUtilityFactory
Specified by:
getUtility in class AbstractLanguageUtilityFactory
See Also:
ILanguageUtilityFactory.getUtility(java.lang.String)

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.