beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jin Kudo (JIRA)" <...@beehive.apache.org>
Subject [jira] Updated: (BEEHIVE-1032) TestRecorder handle request encoding
Date Mon, 13 Feb 2006 09:09:46 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-1032?page=all ]

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

    Attachment: step1and2_patch.txt

Adding patch for step1 and 2. Change the recording encoding to UTF-8 instead of VM encoding.
But it is still requried to modify for step 3. It seems that it is not just use VM encoding
by client side.
The client side is require to both reading file from recorded file and send the request to
server.


> 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, step1and2_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


Mime
View raw message