java.lang.ProcessBuilderEach ProcessBuilder instance manages a collection
of process attributes. The start() method creates a new
Process instance with those attributes. The start() method can be invoked repeatedly from the same instance
to create new subprocesses with identical or related attributes.
Each process builder manages these process attributes:
user.dir.
false, meaning that the standard output and error
output of a subprocess are sent to two separate streams, which can
be accessed using the Process.getInputStream() and Process.getErrorStream() methods. If the value is set to
true, the standard error is merged with the standard
output. This makes it easier to correlate error messages with the
corresponding output. In this case, the merged data can be read
from the stream returned by Process.getInputStream(), while
reading from the stream returned by Process.getErrorStream() will get an immediate end of file.
Modifying a process builder's attributes will affect processes subsequently started by that object's start() method, but will never affect previously started processes or the Java process itself.
Most error checking is performed by the start() method. It is possible to modify the state of an object so that start() will fail. For example, setting the command attribute to an empty list will not throw an exception unless start() is invoked.
Note that this class is not synchronized.
If multiple threads access a ProcessBuilder instance
concurrently, and at least one of the threads modifies one of the
attributes structurally, it must be synchronized externally.
Starting a new process which uses the default working directory and environment is easy:
Process p = new ProcessBuilder("myCommand", "myArg").start();
Here is an example that starts a process with a modified working directory and environment:
ProcessBuilder pb = new ProcessBuilder("myCommand", "myArg1", "myArg2");
Map<String, String> env = pb.environment();
env.put("VAR1", "myValue");
env.remove("OTHERVAR");
env.put("VAR2", env.get("VAR1") + "suffix");
pb.directory(new File("myDir"));
Process p = pb.start();
To start a process with an explicit set of environment variables, first call Map.clear() before adding environment variables.
| Constructor Summary | ||
| ProcessBuilder(String... command) Constructs a process builder with the specified operating
system program and arguments. |
||
| ProcessBuilder(List<String> command) Constructs a process builder with the specified operating
system program and arguments. |
| Method Summary | ||
| command() Returns this process builder's operating system program and
arguments. |
||
| command(String... command) Sets this process builder's operating system program and
arguments. |
||
| command(List<String> command) Sets this process builder's operating system program and
arguments. |
||
| directory() Returns this process builder's working directory. |
||
| directory(java.io.File directory) Sets this process builder's working directory. |
||
| environment() Returns a string map view of this process builder's environment. |
||
boolean |
redirectErrorStream() Tells whether this process builder merges standard error and
standard output. |
|
| redirectErrorStream(boolean redirectErrorStream) Sets this process builder's redirectErrorStream property. |
||
| start() Starts a new process using the attributes of this process builder. |
||
| Methods inherited from class java.lang.Object |
| clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
command list. Subsequent
updates to the list will be reflected in the state of the
process builder. It is not checked whether
command corresponds to a valid operating system
command.nullcommand
array, in the same order. It is not checked whether
command corresponds to a valid operating system
command.command list. Subsequent updates to the list will
be reflected in the state of the process builder. It is not
checked whether command corresponds to a valid
operating system command.nullcommand array, in the same order. It is not
checked whether command corresponds to a valid
operating system command.The returned object may be modified using ordinary Map operations. These modifications will be
visible to subprocesses started via the start()
method. Two ProcessBuilder instances always
contain independent process environments, so changes to the
returned map will never be reflected in any other
ProcessBuilder instance or the values returned by
System.getenv.
If the system does not support environment variables, an empty map is returned.
The returned map does not permit null keys or values. Attempting to insert or query the presence of a null key or value will throw a NullPointerException. Attempting to query the presence of a key or value which is not of type String will throw a ClassCastException.
The behavior of the returned map is system-dependent. A system may not allow modifications to environment variables or may forbid certain variable names or values. For this reason, attempts to modify the map may fail with UnsupportedOperationException or IllegalArgumentException if the modification is not permitted by the operating system.
Since the external format of environment variable names and values is system-dependent, there may not be a one-to-one mapping between them and Java's Unicode strings. Nevertheless, the map is implemented in such a way that environment variables which are not modified by Java code will have an unmodified native representation in the subprocess.
The returned map and its collection views may not obey the general contract of the Object.equals() and Object.hashCode() methods.
The returned map is typically case-sensitive on all platforms.
If a security manager exists, its
checkPermission
method is called with a
RuntimePermission("getenv.*")
permission. This may result in a SecurityException being
thrown.
When passing information to a Java subprocess, system properties are generally preferred over environment variables.
null -- this means to use
the working directory of the current Java process, usually the
directory named by the system property user.dir,
as the working directory of the child process.null -- this means to use the
working directory of the current Java process, usually the
directory named by the system property user.dir,
as the working directory of the child process.If this property is true, then any error output
generated by subprocesses subsequently started by this object's
start() method will be merged with the standard
output, so that both can be read using the
Process.getInputStream() method. This makes it easier
to correlate error messages with the corresponding output.
The initial value is false.
redirectErrorStream propertyredirectErrorStream property.
If this property is true, then any error output
generated by subprocesses subsequently started by this object's
start() method will be merged with the standard
output, so that both can be read using the
Process.getInputStream() method. This makes it easier
to correlate error messages with the corresponding output.
The initial value is false.
The new process will invoke the command and arguments given by command(), in a working directory as given by directory(), with a process environment as given by environment().
This method checks that the command is a valid operating system command. Which commands are valid is system-dependent, but at the very least the command must be a non-empty list of non-null strings.
If there is a security manager, its
checkExec
method is called with the first component of this object's
command array as its argument. This may result in
a SecurityException being thrown.
Starting an operating system process is highly system-dependent. Among the many things that can go wrong are:
In such cases an exception will be thrown. The exact nature of the exception is system-dependent, but it will always be a subclass of java.io.IOException.
Subsequent modifications to this process builder will not affect the returned Process.
0)