exec

Processes may behave differently on different operating systems - for instance stop doesn't always kill the process. Please see http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4109888 for additional information.

Property Summary

Example Summary

Property Detail

A string list of arguments.

The command to execute. The command is interpreted as space delimited text which may be specified over several lines. Arguments that need to include spaces must be quoted. Within quoted arguments quotes may be escaped using a backslash.

The working directory.

An environment variable to be set before the program is executed. This is a map like property.

The exit value of the process.

A name, can be any text.

Create a fresh/clean environment.

Redirect the standard error stream in standard output.

An output to where stderr of the proces will be written.

An input stream which will act as stdin for the process.

An output to where stdout for the process will be written.

This flag is set by the stop method and should be examined by any Stoppable jobs in their processing loops.

Forcibly stop the process on stop.

Examples

A simple example.

<exec name="Batch Example">
cmd /C "${oddjob.dir}\bin\greeting.bat" Hello
</exec>

<exec name="Batch Example">
    <args>
        <list>
            <values>
                <value value="cmd"/>
                <value value="/C"/>
                <value value="${oddjob.dir}\bin\greeting.bat"/>
                <value value="Hello"/>
            </values>
        </list>
    </args>
</exec>

Using the existing environment with an additional environment variable.

<oddjob>
    <job>
        <exec name="Example With Environment" id="exec">
            <environment>
                <value key="ODDJOB_FILE" value="myfile.txt"/>
            </environment>
${platform.set.command}
        </exec>
    </job>
</oddjob>

Capturing console output to a file. The output is Oddjob's command line help.

<oddjob id="this">
    <job>
        <exec id="exec" redirectStderr="true">
            <stdout>
                <file file="${work.dir}/ExecOutput.log"/>
            </stdout>
            java -jar "${oddjob.test.run.jar}" -h
        </exec>
    </job>
</oddjob>

Capturing console output to the logger. Note how the logger output can be defined with different log levels for stdout and sterr.

<oddjob id="this">
    <job>
        <exec>
            <stdout>
                <logout level="INFO"/>
            </stdout>
            <stderr>
                <logout level="WARN"/>
            </stderr>
            java -jar ${oddjob.test.run.jar} -f Missing.xml ${logConfigArgs}/
        </exec>
    </job>
</oddjob>

Using the output of one process as the input of another. Standard input for the first process is provided by a buffer. A second buffer captures the output of that process and passess it to the second process. The output of the second process is captured and sent to the console of the parent process.

<oddjob id="this">
    <job>
        <sequential>
            <jobs>
                <variables id="vars">
                    <ourBuffer>
                        <buffer/>
                    </ourBuffer>
                </variables>
                <exec>
                    <stdin>
                        <buffer>apples
oranges
pears
</buffer>
                    </stdin>
                    <stdout>
                        <value value="${vars.ourBuffer}"/>
                    </stdout>
java -jar "${oddjob.test.run.jar}" -f "${this.dir}/OddjobCat.xml" ${logConfigArgs}
        </exec>
                <exec id="exec">
                    <stdin>
                        <value value="${vars.ourBuffer}"/>
                    </stdin>
                    <stdout>
                        <stdout/>
                    </stdout>
java -jar "${oddjob.test.run.jar}" -f "${this.dir}/OddjobCat.xml" ${logConfigArgs}
        </exec>
            </jobs>
        </sequential>
    </job>
</oddjob>