jackson-core
jackson-core copied to clipboard
Core part of Jackson that defines Streaming API as well as basic shared abstractions
Bundles need to include extra metadata to support `java.util.ServiceLoader` inside an OSGi framework. Jackson's bundles are all missing this metadata. In theory, it _should_ just be a matter of applying...
Currently `createParser()` and `createGenerator()` methods require caller to take care of closing of parser/generator, allowing possible loss of things like file handles and URL connections (see #803 f.ex) But it...
(note: replaces https://github.com/FasterXML/jackson-databind/issues/3520) It looks like JDK's `HttpURLConnection` has unfortunate handling of some error cases, leading to leakage of not-fully-closed HTTP connections under some error conditions. See https://github.com/FasterXML/jackson-databind/issues/3455 for details....
Using jackson version 2.9.6, ```java System.out.println("'\\u2028' is whitespace: " + Character.isWhitespace('\u2028')); System.out.println("'\\u2028' is space char: " + Character.isSpaceChar('\u2028')); System.out.println("'\\u2028' is line separator: " + (Character.getType('\u2028') == Character.LINE_SEPARATOR)); new JsonFactory().createParser("\u2028{\"some\": \"json\"}").nextToken();...
Looks like content such as: ``` [ 100.300.30 ] ``` does pass and report number token `100.300`, only failing when trying to access to the following token. This should be...
Adding https://github.com/nst/JSONTestSuite in https://github.com/rallyhealth/weePickle/pull/106 uncovered that `JsonPointer` memory usage is quadratic over depth. `-Xmx8g` is insufficient to create a `JsonPointer` for [100k opening arrays](https://github.com/nst/JSONTestSuite/blob/d64aefb55228d9584d3e5b2433f720ea8fd00c82/test_parsing/n_structure_100000_opening_arrays.json) without an `OutOfMemoryError`. `JsonPointer` seems to...
When deserializing using the streaming API, the properties of the parsed JSON string are lost when the length () of the JSON string is equal to 156220; when the length...
The optional features in the JSON parser allow it be configured to _almost_ be a fully-compatible parser for JSON5. There's just a few missing features, documented here: https://stackoverflow.com/questions/68312227/can-the-jackson-parser-be-used-to-parse-json5 Summarised as:...
Implementation of #774 is mostly complete, but there is one minor inconsistency: whereas leading plus sign -- if (and only if) enabled as non-standard feature -- is retained for some...
We're seeing inconsistencies between JS's and Jackson's representation of non-printable characters embedded in JSON strings. Where JS sends `\u001b`, once it goes through Jackson the field holds the string `\u001B`,...