[ http://issues.apache.org/jira/browse/BEEHIVE-1032?page=all ]
Jin Kudo updated BEEHIVE-1032:
------------------------------
Attachment: all_patch.txt
Adding complete patch.
But it is temporary workaround solution. The final change is just add the
charset entry in Content-Type header in testrecorder client side instead of
recorded file.
Because the general browser don't add the charset entry in request header, so
it is added in playback phase in client side.
Note. The request encoding is only supported UTF-8 encoding, but you can use
any encoding of JVM.
In record phase, the application server must configure handle the browser
request as UTF-8 encoding and all recorded xml file is stored as UTF-8 encoding
in any time.
> 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: all_patch.txt, 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
