You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2014/09/02 11:44:21 UTC

[jira] [Resolved] (DIRMINA-983) Problems with TextLineDecoder and special characters

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

Emmanuel Lecharny resolved DIRMINA-983.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.8

Fixed with Commit: 2030bf02a96f109fd1454c835fcf69e83a16d466

> Problems with TextLineDecoder and special characters
> ----------------------------------------------------
>
>                 Key: DIRMINA-983
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-983
>             Project: MINA
>          Issue Type: Bug
>         Environment: Apache Mina 2.0.7
>            Reporter: Natascha
>            Priority: Minor
>             Fix For: 2.0.8
>
>
> Hey guys,
> we have special characters in our messages like "ü" or "$" and it seems there is a problem in the TextLineDecoder.
> I debugged the "decodeAuto" method and my question is: Why do you use "buffer.array()" instead of "buffer.toString()"?
> Problem is the array is 1 element too long so "buffer.array()" gives out a blank char at the end. "buffer.toString()" pays attention to "buffer.limit" so the string has perfect size.
> We made a workaround to trim it afterwards but maybe you wanted to know this?
> Greetings,
> Natascha



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)