Remote Systems
v6.4.1

com.ibm.etools.systems.launch.impl
Class RemoteProcessIORedirector

java.lang.Object
  extended bycom.ibm.etools.systems.launch.impl.RemoteProcessIORedirector
All Implemented Interfaces:
IRemoteIORedirector

public class RemoteProcessIORedirector
extends Object
implements IRemoteIORedirector


Field Summary
protected  RemoteCommandShellOperation remoteCommandShellOperation
           
protected  RemoteProcess remoteProcess
           
 
Constructor Summary
RemoteProcessIORedirector(RemoteProcess remoteProcess, RemoteCommandShellOperation remoteCommandShellOperation)
           
 
Method Summary
 boolean init()
           
 boolean isEnabled()
           
 void writeError(String error)
           
 void writeInput(String input)
           
 void writeOutput(String output)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

remoteProcess

protected RemoteProcess remoteProcess

remoteCommandShellOperation

protected RemoteCommandShellOperation remoteCommandShellOperation
Constructor Detail

RemoteProcessIORedirector

public RemoteProcessIORedirector(RemoteProcess remoteProcess,
                                 RemoteCommandShellOperation remoteCommandShellOperation)
Method Detail

init

public boolean init()
Specified by:
init in interface IRemoteIORedirector

writeOutput

public void writeOutput(String output)
Specified by:
writeOutput in interface IRemoteIORedirector

writeError

public void writeError(String error)
Specified by:
writeError in interface IRemoteIORedirector

writeInput

public void writeInput(String input)
Specified by:
writeInput in interface IRemoteIORedirector

isEnabled

public boolean isEnabled()
Specified by:
isEnabled in interface IRemoteIORedirector

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.