Re: exec problem is JDK 1.7.0_21
On 4/28/2013 2:23 AM, Sven K?hler wrote:
Am 28.04.2013 05:35, schrieb Arne Vajh?j:
On 4/24/2013 3:39 AM, Sven K?hler wrote:
On 04/23/2013 11:32 PM, Arved Sandstrom wrote:
That's the point a number of us have been making, Sven. In the case of
ProcessBuilder and Process you jump to no conclusions, and test your
specific case.
The specific case is broken. Now what?
ProcessBuilder provides some functionality.
Hmm. I find that argument dangerous, as it given the a free pass to
implement whatever they want - however badly they want ...
I don't think they have intended to do it badly.
They decided to do things a certain way.
And that decision is causing some problem for you.
But that does not necesarrily make it a bad decision.
If you need more or different functionality, then use JNI
to write your own stuff.
... and then claim
Running external processes is not really platform independent,
so you do not loose that.
Are you saying, that they should have never attempted to convert an
array of arguments into a command line string on Windows? Because that
would exactly be one of my points. Recall the fact, that documentation
already mentions the possibility of proper platform dependent behaviour.
Or are you somehow trying to defend the faulty escaping they implemented
to make it seem like a cross-platform API?
Because at the moment, we're stuck with something broken which is
neither platform dependent nor independent. We neither have a platform
dependent API (e.g. taking arrays of arguments on UNIX and a single
argument on Windows) and neither a platform independent API (which
properly converts an argument array to an argument string).
I am saying that executing external commands is not platform
independent and that if you don't like the standard functionality,
then you should just create your own native code and call it
via JNI. Problem solved.
Arne