You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "deven you (JIRA)" <ji...@apache.org> on 2010/07/21 04:46:50 UTC
[jira] Updated: (HARMONY-6594) [classlib][luni]
CharsetEncoder.flush(Bytebuffer) doesn't follow the spec and RI's behavior
[ https://issues.apache.org/jira/browse/HARMONY-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
deven you updated HARMONY-6594:
-------------------------------
Attachment: HARMONY-6594.diff
> [classlib][luni] CharsetEncoder.flush(Bytebuffer) doesn't follow the spec and RI's behavior
> --------------------------------------------------------------------------------------------
>
> 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
> Attachments: HARMONY-6594.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.