Jackson ObjectMapper with UTF-8 encoding? - 【StackMirror】|json|jackson

Is there a way to tell Jackson to use UTF-8 encoding when using ObjectMapper to serialize and deserialize Objects?

json
jackson

2012-04-04 02:37
by Patricio

Jackson automatically detects encoding used in source: as per JSON specification, only valid encodings are UTF-8, UTF-16 and UTF-32. No other encodings (like Latin-1) can be used. Because of this, auto-detection is easy and done by parser -- no encoding detection is accepted for this reason. So, if input is UTF-8, it will be detected as such.

For output, UTF-8 is the default; but if you explicitly want to use another encoding, you can create JsonGenerator explicitly (with a method that takes JsonEncoding), and pass this to ObjectMapper.

Alternatively in both cases you can of course manually construct java.io.Reader / java.io.Writer, and make it use whatever encoding you want.

2012-04-04 17:14
by StaxMan

I'm not sure how UTF-8 can be the default, when I've spent hours trying to get JSON to be encoded in UTF-8 instead of UTF-16 - cbmanica 2014-03-14 22:31

@cbmanica Trust me, UTF-8 is the absolute default for Jackson when you give java.io.OutputStream. But there are other defaults: JDK has its default encoding if you choose to construct Writer instance yourself, or some other lib/framework does it. These are outside of Jackson - StaxMan 2014-03-17 19:56

@cbmanica Could you, please, share your code that helped you? Seems like I have the very same issue - Tregoreg 2015-05-01 03:05

@StaxMan How is jackson autodetcting the encoding?How can it knows, that an encoded Latin1 is not and UTF8? Because invalid charcaters - alacambra 2016-10-31 13:34

@alacambra Because Latin1 is not valid JSON encoding, as per JSON specification - StaxMan 2016-10-31 22:06

Some example code would be an improvement. I tried

JsonGenerator jsonGeneratorWithUtf16 = new JsonFactory().createGenerator(new File("C:/outputJson.json"), JsonEncoding.UTF16_BE);
      new ObjectMapper().writeValue(jsonGeneratorWithUtf16, objectToBeSerialized);

but when I run file -i C:/outputJson.json it shows charset=binary - Max 2017-05-19 19:38

@Max As long as result is UTF-16 Big-endian Unicode, interpretation by file is something Jackson can do nothing about; perhaps it only detects ASCII/UTF-7/Latin-1, and not UTF-16 encodings. Your usage looks fine. So I am not quite sure what your ask here is - StaxMan 2017-05-20 00:12