All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
JsonPointer.add()
now can replace the value at root location with given array/object, regardless of the original type. This is a requirement from the TCK.
JsonObject.getBoolean()
andJsonObject.isNull()
now correctly throws NPE if there exists no property for the specified key. (PR #12, #13 both are authored by @Thihup)JsonParserFactory.createParser(InputStream)
now correctly throwsJsonException
if character encoding cannot be determined automatically. (Issue #10 reported by @Thihup)- Fixed a bug that was causing JSON Patch move operation on nonexistent value not to throw
JsonException
, if the source path is the same as the target path. (Issue #11 reported by @Thihup)
- Updated the Jakarta API to 2.0.0.
- Added a new JSON-P provider
joy-yaml
which can parse YAML documents with the help of snakeyaml-engine. This artifact can be used as a substitute for the basic providerjoy-classic
.JsonParser
andJsonReader
provided by the new provider can process YAML documents.
- The artifact ID of the original Joy is now changed to
joy-classic
. - Improved
JsonNumber.numberValue()
which now may return an instance ofInteger
orLong
if applicable.
- Fixed the error message emitted when an array in the JSON document is not closed correctly.
- The API package was renamed from
javax.json
tojakarta.json
. - Update the version of Jakarta JSON Processing API to 2.0.0-RC2.
- Collections and maps passed to
JsonBuilderFactory
now can contain instances ofJsonArrayBuilder
orJsonObjectBuilder
as their values. (PR #3 contributed by @toddobryan)
- Update the JSON Processing API to version 1.1.6.
- A bug which was causing
JsonParser.skipArray()
andJsonParser.skipObject()
to throw anIllegalStateException
wrongly when the current state is not the start of the array/object.
- New configuration properties
INDENTATION_SIZE
andTAB_INDENTATION
were added to the extended interfaceJsonGenerator
. (Issue #1 originally proposed by @hohwille)
getConfigInUse()
methods now return only properties recognized by the factory.
- First release to the Maven Central Repository.