To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=94027
User fs changed the following:
What |Old value |New value
================================================================================
Status|NEW |RESOLVED
--------------------------------------------------------------------------------
Resolution| |INVALID
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Sep 18 11:13:36 +0000
2008 -------
Uhm .... Actually, this is INVALID.
What the macro does is
1. create a pipe
2. write some bytes into it
3. pass the pipe to setBinaryStream, together with a length of 65535, i.e.
saying that 65535 bytes should be read from the input stream side of the
pipe.
Since less that 65535 bytes have been written into the pipe, the implementation
of setBinaryStream blocks - it is waiting for more bytes, which will never
arrive.
This is the correct behavior of setBinaryStream, since the stream passed to it
*is not closed yet*. That is, adding a call "oPipe.closeOutput" *after* writing
the bytes into the pipe, but *before* passing the pipe to setBinaryStream, fixes
the problem. In this case, setBinaryStream is able to detect that there aren't
any more bytes. Even though it couldn't read all requested 65535 bytes, it is
still allowed to break since EOF was reached.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
