Remote Systems
v6.4.1

com.ibm.etools.systems.dstore.miners.command
Class QueryPathThread

java.lang.Object
  extended byjava.lang.Thread
      extended bycom.ibm.etools.systems.dstore.miners.command.QueryPathThread
All Implemented Interfaces:
Runnable

public class QueryPathThread
extends Thread

QueryPathThread is used to determine available command completions


Field Summary
static String Copyright
           
 
Fields inherited from class java.lang.Thread
MAX_PRIORITY, MIN_PRIORITY, NORM_PRIORITY
 
Constructor Summary
QueryPathThread(DataElement status)
           
 
Method Summary
 List getPathEnvironment()
           
 void getPossibleCommands(DataElement status)
           
protected  List parsePathEnvironmentVariable(String path)
           
 void run()
           
 
Methods inherited from class java.lang.Thread
activeCount, checkAccess, countStackFrames, currentThread, destroy, dumpStack, enumerate, getContextClassLoader, getName, getPriority, getThreadGroup, holdsLock, interrupt, interrupted, isAlive, isDaemon, isInterrupted, join, join, join, resume, setContextClassLoader, setDaemon, setName, setPriority, sleep, sleep, start, stop, stop, suspend, toString, yield
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Constructor Detail

QueryPathThread

public QueryPathThread(DataElement status)
Method Detail

run

public void run()

getPathEnvironment

public List getPathEnvironment()

parsePathEnvironmentVariable

protected List parsePathEnvironmentVariable(String path)

getPossibleCommands

public void getPossibleCommands(DataElement status)

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.