com.ibm.etools.systems.launch
Class RemoteCommandShellOperationHelper
java.lang.Object
com.ibm.etools.systems.commands.RemoteCommandShellOperation
com.ibm.etools.systems.launch.RemoteCommandShellOperationHelper
- All Implemented Interfaces:
- EventListener, ISystemResourceChangeListener
- public class RemoteCommandShellOperationHelper
- extends RemoteCommandShellOperation
Methods inherited from class com.ibm.etools.systems.commands.RemoteCommandShellOperation |
associateProject, commandMatches, finish, getCurrentCommand, getRemoteCommandShell, getShell, handleShellFinished, isActive, outputUpdated, run, sendCommand, sendInput, setWorkingDirectory, systemResourceChanged |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
validIOReceived
protected boolean validIOReceived
needToCheckDuplicate
protected boolean needToCheckDuplicate
RemoteCommandShellOperationHelper
public RemoteCommandShellOperationHelper(Shell shell,
RemoteCmdSubSystem cmdSubSystem,
IRemoteFile pwd,
IRemoteIORedirector remoteIORedirector)
handleCommandFinished
public void handleCommandFinished(String cmd)
- Specified by:
handleCommandFinished
in class RemoteCommandShellOperation
handleOutputChanged
public void handleOutputChanged(String command,
Object output)
- Specified by:
handleOutputChanged
in class RemoteCommandShellOperation
addListener
public void addListener(IRemoteOutputProxyEventListener listener)
removeListener
public void removeListener(IRemoteOutputProxyEventListener listener)
fireEvent
protected void fireEvent(RemoteOutputProxyEvent event)
setRemoteIORedirector
public void setRemoteIORedirector(IRemoteIORedirector remoteIORedirector)
getRemoteIORedirector
public IRemoteIORedirector getRemoteIORedirector()
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.