Mailing-List: contact dev-help@beehive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <dev@beehive.apache.org>
Message-ID: <2034590940.1135790221986.JavaMail.jira@ajax.apache.org>
Date: Wed, 28 Dec 2005 18:17:01 +0100 (CET)
From: "Jin Kudo (JIRA)" <dev@beehive.apache.org>
To: dev@beehive.apache.org
Subject: [jira] Updated: (BEEHIVE-1032) TestRecorder handle request encoding
In-Reply-To: <69236364.1135655791941.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/BEEHIVE-1032?page=all ]

Jin Kudo updated BEEHIVE-1032:
------------------------------

    Attachment: step1_patch.txt

That is patch only for step1 in the comment.


> TestRecorder handle request encoding
> ------------------------------------
>
>          Key: BEEHIVE-1032
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-1032
>      Project: Beehive
>         Type: Test
>   Components: NetUI
>     Versions: V1
>     Reporter: Jin Kudo
>  Attachments: step1_patch.txt
>
> Currently the test recorder always handle the request encoding as ISO-8859-1. That is cause to none ASCII characters can't be stored in the recording data file correctly. Request encoding determination is not so easy, but I suggest as the reasonable solution testrecorder use the platform encoding as request encoding rather than fixed ISO-8859-1 value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira