harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Ellison (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HARMONY-6594) [classlib][nio_char] CharsetEncoder.flush(Bytebuffer) doesn't follow the spec and RI's behavior
Date Tue, 27 Jul 2010 11:36:15 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tim Ellison closed HARMONY-6594.

    Resolution: Fixed

The patch was re-applied at r979647 in conjunction with the fix for HARMONY-6590 (which was
causing the test failures).

> [classlib][nio_char] CharsetEncoder.flush(Bytebuffer) doesn't  follow the spec and RI's
> ------------------------------------------------------------------------------------------------
>                 Key: HARMONY-6594
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6594
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>    Affects Versions: 5.0M14
>            Reporter: deven you
>            Assignee: Tim Ellison
>             Fix For: 5.0M15
>         Attachments: HARMONY-6594.diff, HARMONY-6594_v2.diff
>   Original Estimate: 96h
>  Remaining Estimate: 96h
> Java 5 spec says the fulsh() will throw 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.
> Our harmony one doesn't follow this behavior and won't throw Exception.

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

View raw message