You're right. The command line wrapper can and probably should delete
the target file in case of an error. Could you check if the
return code
is set on the command line? If not, we should fix that.
Jeremias Märki
Don't know about UNIX but on Windows it seems that the return
code is always
You're right. The command line wrapper can and probably should delete
the target file in case of an error. Could you check if the return code
is set on the command line? If not, we should fix that.
It is. The problem is that FOP can't delete the output file
in case of a
problem if it only
Don't know about UNIX but on Windows it seems that the return code is always 0.
Regards
Con
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Sent: Monday, June 17, 2002 08:23
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: error handling
You're right
Roland Neilands wrote:
All very well for embeddding, but the command prompt version still leaves
the corrupt file there no file at all would be preferable to a useless
one.
Well, I believe it's feasible, but anyway this behaviour should be
parametrizable.
--
Oleg Tkachenko
Multiconn
It is. The problem is that FOP can't delete the output file in case of a
problem if it only gets an OutputStream. And for optimization reasons
FOP can't wait until the end to write the output to the target stream.
On 14.06.2002 21:21:48 Oleg Tkachenko wrote:
Ruane, Conleth wrote:
I'm using the
Jeremias Maerki wrote:
It is. The problem is that FOP can't delete the output file in case of a
problem if it only gets an OutputStream. And for optimization reasons
FOP can't wait until the end to write the output to the target stream.
But does fop should delete output file? I don't think so,
It is. The problem is that FOP can't delete the output file
in case of a
problem if it only gets an OutputStream. And for
optimization reasons
FOP can't wait until the end to write the output to the
target stream.
But does fop should delete output file? I don't think so, that's
I'm using the latest version of FOP to automatically generate pdf files from
xml (what else) and I've noticed that when fop stops due to errors in the input
file(s) a corrupt pdf file is generated.
Is there any way I can prevent this or is there any way I can access a FOP exit
code so that I
Ruane, Conleth wrote:
I'm using the latest version of FOP to automatically generate pdf files from
xml (what else) and I've noticed that when fop stops due to errors in the input
file(s) a corrupt pdf file is generated.
Is there any way I can prevent this or is there any way I can access a FOP
