Maybe I’m late to the party, but UTF-8 should be quite comprehensive covering most languages.
Regarding
Another alternative is to take the input JSON string , pass that to stringToBytes , pass the output to bytesToString again, check if you see a difference.
Not only related to this question, but having a cloud environment (with a set of products installed) where flows can be created and demonstrated should reduce the to and fro in such issues. If someone doesn’t want to share with public , sanitization /appropriate ACLs can be applied as well.
It will be much easier to share flow snippets that way and will allow others to look at the flow and respond.
Regards,
Nagendra
#webMethods#Integration-Server-and-ESB#Flow-and-Java-services