Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
7.14.x, 7.15.x, 7.16.x, 7.17.0
-
None
Description
Environment:
- Any non-docker Camunda distro (all supported versions)
- Any database
- Operating system with non-UTF-8 standard encoding
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
Task comments with Persian characters are not saved correctly.
Steps to reproduce (Required on creation):
- Create a comment on task with following rest API call: POST /task/<id>/comment/create
- message in Unicode (Persian), for example این نمونه است
- Retrieve the comment using this API: GET /task/<id>/comment/<commentId>
*The message in response is ?? ???
Observed Behavior (Required on creation):
After saving a comment with message این نمونه است, the persisted message is ??? ??
Expected behavior (Required on creation):
The correct characters are persisted in the database.
Root Cause (Required on prioritization):
The message is saved in a BLOB database column. When converting the String to Bytes, the character encoding is not set.
Without a specified encoding, the default encoding is used (which is probably UTF-8 in the docker container) but differs from system to system (mine was ISO_8859_1).
Solution Ideas (Optional):
Set the character encoding to UTF-8 when converting the message to bytes.
