Tapestry 5
  1. Tapestry 5
  2. TAP5-268

UTF8 characters are not supported in the autocomplete mixin

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.16
    • Component/s: None
    • Labels:
      None
    • Environment:
      Firefox 2.x

      Description

      The array of String provided by the method called by the mixin is not transfered properly : the non-7 bits characters are lost.

      1. mixin.gif
        1 kB
        José Paumard

        Issue Links

          Activity

          Hide
          Marcelo Lotif added a comment -

          There's a quick fox for this, but i'm not sure if it's the best one:

          class org.apache.tapestry5.util.TextStreamResponse, line 46:

          • return new ByteArrayInputStream(text.getBytes());
            + return new ByteArrayInputStream(text.getBytes("UTF-8"));

          a workaround is to create the package inside your app(org.apache.tapestry5.util) copy this class and switch these lines.

          Show
          Marcelo Lotif added a comment - There's a quick fox for this, but i'm not sure if it's the best one: class org.apache.tapestry5.util.TextStreamResponse, line 46: return new ByteArrayInputStream(text.getBytes()); + return new ByteArrayInputStream(text.getBytes("UTF-8")); a workaround is to create the package inside your app(org.apache.tapestry5.util) copy this class and switch these lines.
          Hide
          José Paumard added a comment - - edited

          I just tested it with FF 2.0 and Chrome, and the bug is still there : if I send non ASCII characters in the List<String> provided by the completion provider, they are not properly sent to the client (see attachment).
          Edit : bug seen in 5.0.15 and 5.016-SNAPSHOT (as of today).

          Show
          José Paumard added a comment - - edited I just tested it with FF 2.0 and Chrome, and the bug is still there : if I send non ASCII characters in the List<String> provided by the completion provider, they are not properly sent to the client (see attachment). Edit : bug seen in 5.0.15 and 5.016-SNAPSHOT (as of today).

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              José Paumard
            • Votes:
              8 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development