Eric Douglas wrote:
Surely this is a longer explanation than you're asking for.
Certainly was ;-)
The short
answer is I'm well aware of how the output streams work, but I thought
if the transform was writing to it which should be a complete process
that it would close it when it's done.
It was your expressed surprise that an open BufferedOutputStream
isn't flushed that I was commenting on.
As in:
Eric Douglas wrote:
I resolved this. After the transform I didn't close the output stream.
Apparently that left some bytes hanging.
It appears that the (real) surprise is that the execution
doesn't close its destination OutputStream.
I would be surprised if it *did*.
Consider, for example, that for reasons all-my-own I want to create an old
style quickdraw version from fop input. If I had a quickdraw
writing library, I could generate a quickdraw image header (*),
let FOP write a (rendered) jpeg to the still-open OutputStream
of the quickdraw, and then generate any required quickdraw trailer.
It would be most inconvenient if the FOP staged closed my outputstream.
BugBear
(* this isn't how the quickdraw really works, but it's near enough for this
example)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
