Process API Updates (JEP 102)
Roger.Riggs at Oracle.com
Tue Mar 25 13:28:28 UTC 2014
Good idea, I'll put something together in the next couple of weeks.
On 3/25/14 1:54 AM, Martijn Verburg wrote:
> Hi Roger,
> Is there a short survey we could send out to the wider dev community
> on this one? I think just about every day to day Java developer has
> had to use Process at some stage in their career.
> On 24 March 2014 21:11, roger riggs <roger.riggs at oracle.com
> <mailto:roger.riggs at oracle.com>> wrote:
> I'm starting to work on JEP 102, Process API Updates for JDK 9.
> The use cases identified include test execution and build systems such
> as Jtreg and Hudson/Jenkins. And there is a use-case for using Java
> to monitor the health of a more complex system where the processes
> are not spawned by the same manager.
> The current API of Process itself is pretty complete with the
> addition of a getPid
> method to enable identification of subprocesses spawned by the
> and allow external identification. It will not be possible to
> intercept the input,
> output and error streams of an arbitrary process.
> From the scope of the JEP, a fairly simple API seems sufficient.
> - Enumerate the direct children
> - The rest of the functions are similar to Process
> - to terminate a process, forcibly and normally
> - to destroy a process and all of its children recursively
> - to check if one is alive
> - to waitFor for termination and retrieve the exit status
> Are there use cases for which this is insufficient? Please comment.
> Thanks, Roger
More information about the core-libs-dev