Forum Discussion
While waiting for 1.5 to come out, here is something to try, which I found in a SmartBear Community post late last year, when I experienced a similar problem.
Try adding -Dfile.encoding=UTF8 in the file ReadyAPI-1.4.0.vmoptions in the ReadyAPI bin directory under c:\Program Files\SmartBear - assuming UTF-8 is your choice of encoding. I found I had to add this every time I upgraded since 1.3.0, for my tests to work.
For the developer on this thread - if this is a valid work-around while waiting for 1.5 (hey, I'm trying to stay on topic :smileyhappy:) - in the forum I found both -Dfile.encoding=UTF8 (no hyphen) and -Dfile.encoding=UTF-8 (with the hyphen). Which is correct?
- TanyaYatskovska10 years agoSmartBear Alumni (Retired)
Hi Kieron_horide-h,
The issue reported in this thread was fixed in the Ready! API 1.4 maintenance build. Please check if the issue disappears in your case:
- kieron_horide-h10 years agoNew Contributor
Understood. I was thinking this might be a work-around to try, allowing users to stay on the normal upgrade path.
However, the maintenance build doesn't fix my problem - in SoapUI NG, the Raw view of the request shows M?ori ???? in a value, where in the Form view it has Māori ĀĀāā (the header has Content-Type: application/xml; charset=utf-8 ). the request fails server-side validation because of the '?' characters. This problem is resolved by adding -Dfile.encoding=UTF8 to the vmoptions file.
Related Content
- 2 years ago
- 3 years ago
- 3 years ago
- 6 years ago
Recent Discussions
- 5 days ago