? If
not, could you please close this bug?
ByteBuffer getString() confused after CharacterCodingException
--
Key: DIRMINA-460
URL: https://issues.apache.org/jira/browse/DIRMINA-460
Project
. I
will mark this bug as invalid and close it.
ByteBuffer getString() confused after CharacterCodingException
--
Key: DIRMINA-460
URL: https://issues.apache.org/jira/browse/DIRMINA-460
.
--
Resolution: Invalid
ByteBuffer getString() confused after CharacterCodingException
--
Key: DIRMINA-460
URL: https://issues.apache.org/jira/browse/DIRMINA-460
Project: MINA
On 10/16/07, Yigal Rachman [EMAIL PROTECTED] wrote:
Hi, Folks:
When ByteBuffer.getString() breaks midway because of a
CharacterCodingException, it fails to restore the position and limit;
thus getString() is destructive when this happens. One can, of course,
work around this, but it should
Hi, Trustin:
The call I am using is buf.getString( decoder ). The limit does not
change, but the position does; it remains at the "broken" byte. I
thought it would simply read the buffer between position() and limit()
without changing anything - did I misunderstand this?
Yigal
Trustin Lee
Hi, Trustin:
I ran your test case on my system and had the following error (which is
actually different from what I am seeing!)
Exception in thread "main" java.lang.AssertionError:
expected:12 but was:3
at org.junit.Assert.fail(Assert.java:71)
at
Hi, Trustin:
Yep - I just installed mina 1.1.2, and ByteBuffer now passes the test.
Thanks again for the swift help.
Yigal
Yigal Rachman wrote:
Hi, Trustin:
I ran your test case on my system and had the following error (which is
actually different from what I am seeing!)
Hi, Folks:
When ByteBuffer.getString() breaks midway because of a
CharacterCodingException, it fails to restore the position and limit;
thus getString() is destructive when this happens. One can, of course,
work around this, but it should not be necessary.
Yigal Rachman
On 10/16/07, Yigal Rachman [EMAIL PROTECTED] wrote:
Hi, Folks:
When ByteBuffer.getString() breaks midway because of a
CharacterCodingException, it fails to restore the position and limit;
thus getString() is destructive when this happens. One can, of course,
work around this, but it should
ByteBuffer getString() confused after CharacterCodingException
--
Key: DIRMINA-460
URL: https://issues.apache.org/jira/browse/DIRMINA-460
Project: MINA
Issue Type: Bug
10 matches
Mail list logo