harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "deven you (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-6590) [classlib][luni]A issue about CharsetEncoder.flush() in the OutputStreamWrtier.close()
Date Fri, 16 Jul 2010 06:19:49 GMT
[classlib][luni]A issue about CharsetEncoder.flush() in the OutputStreamWrtier.close()

                 Key: HARMONY-6590
                 URL: https://issues.apache.org/jira/browse/HARMONY-6590
             Project: Harmony
          Issue Type: Bug
          Components: Classlib
    Affects Versions: 5.0M14
            Reporter: deven you
             Fix For: 5.0M14

Today I read through the OutputStreamWrtier.close() code below:
    public void close() throws IOException {
        synchronized (lock) {
            if (encoder != null) {
                encoder = null;
                bytes = null;
I remember the java spec says for the CharsetEncoder.flush(): IllegalStateException - If the
previous step of the current encoding operation was an invocation neither of the reset method
nor of the three-argument encode method with a value of true for the endOfInput parameter.
Obviously OutputStreamWrtier.close() does not check this prerequisite before invoking the
encoder.flush(bytes). So I write a test case[1] to check this issue but it passed, I think
it is because our CharsetEncoder.flush() does not follow the spec.
Though I think our OutputStreamWrtier.close() should modify to follow the spec. I have put
the patch[1] on this jira.
And I will also look into the CharsetEncoder.flush() to investigate this problem.
[1] see the attached patch

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message