jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vincent Partington <>
Subject Re: always uses default encoding, ResultCollector always uses UTF-*
Date Mon, 05 Jan 2004 15:43:00 GMT
Jordi Salvat i Alabart wrote:
> I've fixed the issue (in current CVS code) by enabling TextFile to use 
> an encoding of choice and having ResultCollector use UTF-8. It's 
> suboptimal, but it will do until someone has the time and energy to 
> write a ResultCollector that dumps content into files or uses base64 
> encoding or whatever.

Hi Jordi,

Thank you for implementing that fix. That will at least solve some of my 
problems. There is still the issue of the &1#; characters appearing.

The problem will be solved even better when result data is not written 
to the results XML file. Currently this only happens when a response 
assertion sets error="true":
            new String((byte[]) response.getResponseData()));

A more logical approach would be to set the failure message to something 
like "Cannot assert response when sample was not succesful", or just not 
checking where the sample was succesful at all.

Regards, Vincent.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message