Jason,
I might be misunderstanding your suggestion, but the current
implementation of
OutputStreamWriter.flushBuffer()/StreamWriter.implFlushBuffer() does not
flush
the encoder, so even the caller can choose when to invoke flushBuffer(),
it does
not solve the problem (flush() invokes flushBuff
CCed Bill Shannon.
On 02/09/2012 11:10 AM, Xueming Shen wrote:
CharsetEncoder has the "flush()" method as the last step (of a series
of "encoding" steps) to
flush out any internal state to the output buffer. The issue here is
the the upper level wrapper
class, OutputStreamWriter in our case,
CharsetEncoder has the "flush()" method as the last step (of a series of
"encoding" steps) to
flush out any internal state to the output buffer. The issue here is the
the upper level wrapper
class, OutputStreamWriter in our case, doesn't provide a "explicit"
mechanism to let the
user to reques
First of all, is this really a Java SE bug? The usage of
OutputSteamWriter in JavaMail seems to be wrong to me. The writeTo
method in the bug report doesn't seem to be able to deal with any
stateful encodings.
Masayoshi
On 2/9/2012 3:26 PM, Xueming Shen wrote:
Hi
This is a long standing "re
