On 04/10/2014 19:12, Bernd Eckenfels wrote:
:
This creates the interesting situation, that the JVM verifies stricter
if you not use the (Microsoft recommended) "cmd /C". (In fact the
implementation even documents this as a workaround if you want to
avoid the validation.)
Would it make sense to o
Am Sat, 04 Oct 2014 18:21:58 -0700
schrieb Alan Bateman :
> It's for compatibility reasons. There is a lot of code that calls
> Runtime.exec to run .cmd and .bat scripts. Early versions of the JDK
> didn't do much validation in this area and just passed the input to
> the win32 call. The checking
On 04/10/2014 16:54, Bernd Eckenfels wrote:
Hello,
I noticed that MSDN CreateProcess(W) talks about using "cmd /c" for
executing .bat and .cmd files:
"To run a batch file, you must start the command interpreter;
set lpApplicationName to cmd.exe and set lpCommandLine to the
following arguments:
Hello,
I noticed that MSDN CreateProcess(W) talks about using "cmd /c" for
executing .bat and .cmd files:
"To run a batch file, you must start the command interpreter;
set lpApplicationName to cmd.exe and set lpCommandLine to the
following arguments: /c plus the name of the batch file."
However
