From 50f7838f3765609dd01d3c6ff5dfc2eb08444475 Mon Sep 17 00:00:00 2001 From: gurunrao Date: Thu, 10 Feb 2022 09:13:20 +0530 Subject: [PATCH] remove jsonb tck. Signed-off-by: gurunrao --- Jenkinsfile | 7 +- bin/coverage-build.xml | 14 +- docker/build_standalone-tcks.sh | 7 +- docker/jsonbtck.sh | 88 - docker/scripts/tcks/docker-entrypoint.sh | 5 - docker/scripts/tcks/jsonbtck.sh | 41 - install/jakartaee/bin/ts.jtx | 43 - install/jsonb/LICENSE.md | 637 ----- install/jsonb/bin/build.xml | 331 --- install/jsonb/bin/harness.policy | 4 - install/jsonb/bin/java.policy | 5 - install/jsonb/bin/sig-test-pkg-list.txt | 34 - install/jsonb/bin/sig-test.map | 41 - install/jsonb/bin/smoke.xml | 62 - install/jsonb/bin/ts.jte | 255 -- install/jsonb/bin/ts.jtx | 33 - .../bin/xml/impl/glassfish/config.vi.xml | 144 -- install/jsonb/docs/JSONB2.0-ReleaseNotes.html | 99 - .../assertions/JSONB20JavadocAssertions.html | 846 ------- .../assertions/Jsonb20SpecAssertions.html | 910 -------- install/jsonb/docs/index.html | 77 - install/jsonb/other/testsuite.jtt | 23 - install/jsonb/other/vehicle.properties | 70 - internal/docs/jsonb/JSONB1.0.TCD.txt | 73 - .../docs/jsonb/JSONB10JavadocAssertions.html | 846 ------- .../docs/jsonb/JSONB10JavadocAssertions.xml | 891 ------- .../docs/jsonb/Jsonb10SpecAssertions.html | 910 -------- internal/docs/jsonb/Jsonb10SpecAssertions.xml | 2046 ----------------- internal/docs/jsonb/JsonbSpecAssertions.html | 895 ------- internal/docs/jsonb/JsonbSpecAssertions.xml | 2011 ---------------- internal/docs/jsonb/README.txt | 80 - internal/docs/jsonb/extracted-ids.xml | 1617 ------------- internal/docs/jsonb/generateSpecAssertions | 29 - internal/docs/jsonb/jsonbRegrouping.xsl | 371 --- release/tools/jsonb.xml | 172 -- user_guides/build_tckugs.sh | 4 +- user_guides/jsonb/README.md | 77 - user_guides/jsonb/pom.xml | 258 --- .../jsonb/src/main/jbake/assets/README.md | 4 - .../jsonb/src/main/jbake/assets/_config.yml | 14 - .../jsonb/src/main/jbake/assets/css/style.css | 313 --- .../img/eclipse_foundation_logo_tiny.png | Bin 3612 -> 0 bytes .../jsonb/src/main/jbake/content/README | 77 - .../src/main/jbake/content/attributes.conf | 37 - .../jsonb/src/main/jbake/content/config.adoc | 353 --- .../jsonb/src/main/jbake/content/config.inc | 107 - .../src/main/jbake/content/debug-tips.inc | 0 .../jsonb/src/main/jbake/content/debug.adoc | 174 -- .../jsonb/src/main/jbake/content/defns.inc | 46 - .../jsonb/src/main/jbake/content/faq.adoc | 62 - .../main/jbake/content/install-server-vi.inc | 0 .../src/main/jbake/content/install-server.inc | 0 .../jsonb/src/main/jbake/content/install.adoc | 86 - .../jsonb/src/main/jbake/content/intro.adoc | 349 --- .../jsonb/src/main/jbake/content/intro.inc | 0 .../jsonb/src/main/jbake/content/packages.inc | 11 - .../src/main/jbake/content/platforms.inc | 1 - .../jsonb/src/main/jbake/content/preface.adoc | 147 -- .../jsonb/src/main/jbake/content/rebuild.adoc | 20 - .../jsonb/src/main/jbake/content/rebuild.inc | 8 - .../src/main/jbake/content/req-software.inc | 10 - .../jsonb/src/main/jbake/content/rules.adoc | 403 ---- .../jsonb/src/main/jbake/content/rules.inc | 78 - .../src/main/jbake/content/tck-packages.inc | 7 - .../jsonb/src/main/jbake/content/title.adoc | 42 - .../jsonb/src/main/jbake/content/title.inc | 11 - .../src/main/jbake/content/using-examples.inc | 53 - .../jsonb/src/main/jbake/content/using.adoc | 323 --- .../jsonb/src/main/jbake/content/using.inc | 0 .../jsonb/src/main/jbake/jbake.properties | 24 - .../jsonb/src/main/jbake/templates/footer.ftl | 44 - .../jsonb/src/main/jbake/templates/header.ftl | 54 - .../jsonb/src/main/jbake/templates/menu.ftl | 1 - .../jsonb/src/main/jbake/templates/page.ftl | 8 - .../jsonb/src/theme/jakartaee-theme.yml | 299 --- 75 files changed, 8 insertions(+), 17214 deletions(-) delete mode 100644 docker/jsonbtck.sh delete mode 100644 docker/scripts/tcks/jsonbtck.sh delete mode 100644 install/jsonb/LICENSE.md delete mode 100644 install/jsonb/bin/build.xml delete mode 100644 install/jsonb/bin/harness.policy delete mode 100644 install/jsonb/bin/java.policy delete mode 100644 install/jsonb/bin/sig-test-pkg-list.txt delete mode 100644 install/jsonb/bin/sig-test.map delete mode 100644 install/jsonb/bin/smoke.xml delete mode 100644 install/jsonb/bin/ts.jte delete mode 100644 install/jsonb/bin/ts.jtx delete mode 100644 install/jsonb/bin/xml/impl/glassfish/config.vi.xml delete mode 100644 install/jsonb/docs/JSONB2.0-ReleaseNotes.html delete mode 100644 install/jsonb/docs/assertions/JSONB20JavadocAssertions.html delete mode 100644 install/jsonb/docs/assertions/Jsonb20SpecAssertions.html delete mode 100644 install/jsonb/docs/index.html delete mode 100644 install/jsonb/other/testsuite.jtt delete mode 100644 install/jsonb/other/vehicle.properties delete mode 100644 internal/docs/jsonb/JSONB1.0.TCD.txt delete mode 100644 internal/docs/jsonb/JSONB10JavadocAssertions.html delete mode 100644 internal/docs/jsonb/JSONB10JavadocAssertions.xml delete mode 100644 internal/docs/jsonb/Jsonb10SpecAssertions.html delete mode 100644 internal/docs/jsonb/Jsonb10SpecAssertions.xml delete mode 100644 internal/docs/jsonb/JsonbSpecAssertions.html delete mode 100644 internal/docs/jsonb/JsonbSpecAssertions.xml delete mode 100644 internal/docs/jsonb/README.txt delete mode 100644 internal/docs/jsonb/extracted-ids.xml delete mode 100644 internal/docs/jsonb/generateSpecAssertions delete mode 100644 internal/docs/jsonb/jsonbRegrouping.xsl delete mode 100644 release/tools/jsonb.xml delete mode 100644 user_guides/jsonb/README.md delete mode 100644 user_guides/jsonb/pom.xml delete mode 100644 user_guides/jsonb/src/main/jbake/assets/README.md delete mode 100644 user_guides/jsonb/src/main/jbake/assets/_config.yml delete mode 100644 user_guides/jsonb/src/main/jbake/assets/css/style.css delete mode 100644 user_guides/jsonb/src/main/jbake/assets/img/eclipse_foundation_logo_tiny.png delete mode 100644 user_guides/jsonb/src/main/jbake/content/README delete mode 100644 user_guides/jsonb/src/main/jbake/content/attributes.conf delete mode 100644 user_guides/jsonb/src/main/jbake/content/config.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/config.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/debug-tips.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/debug.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/defns.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/faq.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/install-server-vi.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/install-server.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/install.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/intro.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/intro.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/packages.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/platforms.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/preface.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/rebuild.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/rebuild.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/req-software.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/rules.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/rules.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/tck-packages.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/title.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/title.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/using-examples.inc delete mode 100644 user_guides/jsonb/src/main/jbake/content/using.adoc delete mode 100644 user_guides/jsonb/src/main/jbake/content/using.inc delete mode 100644 user_guides/jsonb/src/main/jbake/jbake.properties delete mode 100644 user_guides/jsonb/src/main/jbake/templates/footer.ftl delete mode 100644 user_guides/jsonb/src/main/jbake/templates/header.ftl delete mode 100644 user_guides/jsonb/src/main/jbake/templates/menu.ftl delete mode 100644 user_guides/jsonb/src/main/jbake/templates/page.ftl delete mode 100644 user_guides/jsonb/src/theme/jakartaee-theme.yml diff --git a/Jenkinsfile b/Jenkinsfile index 08db235528..5f182d5ca8 100644 --- a/Jenkinsfile +++ b/Jenkinsfile @@ -17,8 +17,7 @@ env.label = "jakartaee-tck-pod-${UUID.randomUUID().toString()}" default_suites=[ "samples", "signaturetest/javaee" ] -default_tcks=["caj", "concurrency", "connector", "el", "jacc", "jaspic", "jaxws", "jms", "jpa", "jsf", "jsp", "jsonb", "jstl", "jta", "saaj", "securityapi", "servlet", "websocket"] - +default_tcks=["caj", "concurrency", "connector", "el", "jacc", "jaspic", "jaxws", "jms", "jpa", "jsf", "jsp", "jstl", "jta", "saaj", "securityapi", "servlet", "websocket"] def cts_suites = params.test_suites != null ? params.test_suites.split() : default_suites def tcks = params.standalone_tcks != null ? params.standalone_tcks.split() : default_tcks @@ -169,7 +168,7 @@ spec: string(name: 'GF_VERSION_URL', defaultValue: '', description: 'URL required for downloading GlassFish version details' ) - string(name: 'OLD_GF_BUNDLE_URL', + string(name: 'OLD_GF_BUNDLE_URL', defaultValue: '', description: 'URL required for downloading Old GlassFish Full/Web profile bundle' ) string(name: 'TCK_BUNDLE_BASE_URL', @@ -193,7 +192,7 @@ spec: description: 'Run the full EE compliance testsuite or a standalone tck' ) string(name: 'test_suites', defaultValue: 'concurrency connector ejb ejb30/bb ejb30/lite/appexception ejb30/lite/async ejb30/lite/basic ejb30/lite/ejbcontext ejb30/lite/enventry ejb30/lite/interceptor ejb30/lite/lookup ejb30/lite/naming ejb30/lite/nointerface ejb30/lite/packaging ejb30/lite/singleton ejb30/lite/stateful ejb30/lite/tx ejb30/lite/view ejb30/lite/xmloverride ejb30/assembly ejb30/timer ejb30/webservice ejb30/zombie ejb30/misc ejb30/sec ejb32 el integration jacc jaspic javaee javamail jaxrs jdbc_appclient jdbc_ejb jdbc_jsp jdbc_servlet jms_appclient jms_ejb jms_jsp jms_servlet jpa_appmanaged jpa_appmanagedNoTx jpa_pmservlet jpa_puservlet jpa_stateful3 jpa_stateless3 jsf jsonb jsonp jsp jstl jta jws samples securityapi servlet signaturetest/javaee webservices12 webservices13 websocket xa', description: 'Space separated list of Test suites to run') - string(name: 'standalone_tcks', defaultValue: 'caj concurrency connector el jacc jaspic jaxws jms jpa jsf jsp jsonb jstl jta saaj securityapi servlet websocket', + string(name: 'standalone_tcks', defaultValue: 'caj concurrency connector el jacc jaspic jaxws jms jpa jsf jsp jstl jta saaj securityapi servlet websocket', description: 'Space separated list of standalone TCKs to build and run') string(name: 'USER_KEYWORDS', defaultValue: '', diff --git a/bin/coverage-build.xml b/bin/coverage-build.xml index 3797911228..889974fc6a 100644 --- a/bin/coverage-build.xml +++ b/bin/coverage-build.xml @@ -1,7 +1,7 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/install/jsonb/bin/harness.policy b/install/jsonb/bin/harness.policy deleted file mode 100644 index 16a8bfabdd..0000000000 --- a/install/jsonb/bin/harness.policy +++ /dev/null @@ -1,4 +0,0 @@ -grant { - // "standard" properies that can be read by anyone - permission java.security.AllPermission ; -}; diff --git a/install/jsonb/bin/java.policy b/install/jsonb/bin/java.policy deleted file mode 100644 index 35733e010f..0000000000 --- a/install/jsonb/bin/java.policy +++ /dev/null @@ -1,5 +0,0 @@ -grant { - // "standard" properies that can be read by anyone - permission java.security.AllPermission ; -}; - diff --git a/install/jsonb/bin/sig-test-pkg-list.txt b/install/jsonb/bin/sig-test-pkg-list.txt deleted file mode 100644 index 44dc51176a..0000000000 --- a/install/jsonb/bin/sig-test-pkg-list.txt +++ /dev/null @@ -1,34 +0,0 @@ -# -# Copyright (c) 2017, 2020 Oracle and/or its affiliates. All rights reserved. -# -# This program and the accompanying materials are made available under the -# terms of the Eclipse Public License v. 2.0, which is available at -# http://www.eclipse.org/legal/epl-2.0. -# -# This Source Code may also be made available under the following Secondary -# Licenses when the conditions for such availability set forth in the -# Eclipse Public License v. 2.0 are satisfied: GNU General Public License, -# version 2 with the GNU Classpath Exception, which is available at -# https://www.gnu.org/software/classpath/license.html. -# -# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 -# - -# -# $Id$ -# - -## -# This file contains a list of all the packages -# contained in the signature files for this -# deliverable. This file is used to exclude valid -# sub-packages from being verified when their -# parent package's signature is checked. -## - -jakarta.json.bind -jakarta.json.bind.adapter -jakarta.json.bind.annotation -jakarta.json.bind.config -jakarta.json.bind.serializer -jakarta.json.bind.spi diff --git a/install/jsonb/bin/sig-test.map b/install/jsonb/bin/sig-test.map deleted file mode 100644 index 171b2c4649..0000000000 --- a/install/jsonb/bin/sig-test.map +++ /dev/null @@ -1,41 +0,0 @@ -# -# Copyright (c) 2017, 2021 Oracle and/or its affiliates. All rights reserved. -# -# This program and the accompanying materials are made available under the -# terms of the Eclipse Public License v. 2.0, which is available at -# http://www.eclipse.org/legal/epl-2.0. -# -# This Source Code may also be made available under the following Secondary -# Licenses when the conditions for such availability set forth in the -# Eclipse Public License v. 2.0 are satisfied: GNU General Public License, -# version 2 with the GNU Classpath Exception, which is available at -# https://www.gnu.org/software/classpath/license.html. -# -# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 -# - -# -# $Id$ -# - -############################################################### -# -# IMPORTANT: this sig-test.map file for use with JDK 11+ only! -# Using this file with older version of JDK will yield errors. -# -# The signature test mapping file for the JSON-B TCK. This file -# should be formatted as a standard java properties file. The -# name is the package name and the value is the version of the -# package that should be tested by the signature tests. -# -# The resultant signature file name has a name that complies -# with the following format: -# .sig -# Given this format, the following example breaks down as follows: -# jakarta.json.bind.sig: -# = jakarta.json.bind -# = 1.1 (for JSON-B) -# -# -############################################################### -jakarta.json.bind=3.0 diff --git a/install/jsonb/bin/smoke.xml b/install/jsonb/bin/smoke.xml deleted file mode 100644 index 40a46b8bec..0000000000 --- a/install/jsonb/bin/smoke.xml +++ /dev/null @@ -1,62 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/install/jsonb/bin/ts.jte b/install/jsonb/bin/ts.jte deleted file mode 100644 index cc1167b20f..0000000000 --- a/install/jsonb/bin/ts.jte +++ /dev/null @@ -1,255 +0,0 @@ -# -# Copyright (c) 2017, 2021 Oracle and/or its affiliates. All rights reserved. -# -# This program and the accompanying materials are made available under the -# terms of the Eclipse Public License v. 2.0, which is available at -# http://www.eclipse.org/legal/epl-2.0. -# -# This Source Code may also be made available under the following Secondary -# Licenses when the conditions for such availability set forth in the -# Eclipse Public License v. 2.0 are satisfied: GNU General Public License, -# version 2 with the GNU Classpath Exception, which is available at -# https://www.gnu.org/software/classpath/license.html. -# -# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 -# - -######################################################################### -# # -# JavaTest Environment file for JSON-B Compatibility Test Suite # -# # -# Environment specific properties in this file will likely # -# have to be modified prior to running the JSON-B TCK. Instructions # -# for modifying these properties are contained in this file. # -# # -######################################################################### - -############################################################################ -# Properties to set prior to running the JSON-B TCK tests -# -# @jsonb.classes -- Classes of the JSON-B RI Implementation needed to -# build and run the JSON-B TCK -# -# Added to ts.classpath, ts.run.classpath and -# sigTestClasspath below. -############################################################################ -jsonb.classes= - -############################################################################### -# DO NOT MODIFY -# -# @jsonb.resources -- Location of resources used by JSON-B TCK tests -# @jsonb.alt.provider.classes -- Specify location of alternate JsonProvider. -# This is done automatically by run.pluggability -# target in ${ts.home}/bin/build.xml. This target -# in turn calls enable.alternate.jsonb.provider and -# disable.alternate.jsonb.provider targets to enable -# the alternate Json test provider when running the -# pluggability tests for SPI testing and to disable -# it after testing is complete. -# -# Added to ts.run.classpath below. -############################################################################### -jsonb.resources=${ts.home}/src/com/sun/ts/tests/jsonb/resources -jsonb.alt.provider.classes=jsonb.alt.provider.classes - -#################################################################### -# The jars/classes for the TS harness/javatest and the test classes -# @ts.harness.classpath -- Classes required by javatest -# @ts.classpath -- Classes used to build the JSON-B tests -# @ts.run.classpath -- Classes needed by test run -#################################################################### -ts.harness.classpath=${ts.home}/lib/javatest.jar${pathsep}${ts.home}/lib/tsharness.jar${pathsep}${ts.home}/lib/jsonbtck.jar${pathsep}${ant.home}/lib/ant.jar - -ts.classpath=${jsonb.classes}${pathsep}${ts.home}/lib/tsharness.jar${pathsep}${ts.home}/lib/jsonbtck.jar - -ts.run.classpath=${ts.home}/lib/tsharness.jar${pathsep}${ts.home}/lib/sigtest.jar${pathsep}${ts.home}/lib/jsonbtck.jar${pathsep}${ts.home}/classes${pathsep}${ts.home}/bin${pathsep}${jsonb.alt.provider.classes}${pathsep}${jsonb.classes} - -########################################################################### -# @tools.jar should be set to the location of the tools.jar from the -# installed jdk -########################################################################### -tools.jar=${jdk.home}/lib/tools.jar - -######################################################################## -## Javatest batch mode work directory and report directory, and policy for -## handling existing work and report directories. These properties affects -## runclient and report targets, but not gui target. -## To disable generating test report, unset report.dir, or set it to "none" -## either here or from command line, as in the following command: -## ant runclient -Dreport.dir="none" -## -# @work.dir The directory used to store Javatest test results and test -# information. -# @report.dir The directory used to store Javatest summary reports of -# test results. -# @if.existing.work.report.dirs specifies how existing work.dir and -# report.dir will be handled, and it must be one of the following values: -# overwrite overwrites all content in work.dir and report.dir -# backup moves all content in work.dir and report.dir to -# work.dir_time_day_bak and report.dir_time_day_bak, -# respectively -# append reuses and preserves the existing work.dir and report.dir -# auto lets the build files decide which mode to use -# (overwrite, backup or append). the value is determined -# like this: -# if.existing.work.report.dirs == auto -# if in JSON-B workspace -# if.existing.work.report.dirs = overwrite -# else we are in a distribution bundle -# if.existing.work.report.dirs = append -# end if -# else -# if.existing.work.report.dirs = value in this file -# end if -######################################################################## -work.dir=/tmp/JTworkjsonb -report.dir=/tmp/JTreportjsonb -if.existing.work.report.dirs=append - -############################################################### -## These properties must be set to tell the Test harness the -## class names of your porting class implementations. By default -## the property settings below point to Sun RI specific classes. -## both property sets below point to Sun RI specific classes. -############################################################### -porting.ts.url.class.1=com.sun.ts.lib.implementation.sun.common.SunRIURL - -######################################################################### -# @jimage.dir: This property specifies the directory where Java 11+ -# modules will be expanded by the jimage tool for use -# in sigTestClasspath -# -# @sigTestClasspath: This property must be set when running signature -# tests. This property should be set to a list of -# jar files and/or directories which contain your -# Java EE and Java SE classes. Paths must be -# separated by the appropriate path separator -# (';' windows, ':' Unixes). -######################################################################### -jimage.dir=${ts.home}/tmp/jdk-bundles - -sigTestClasspath=${jsonb.classes}${pathsep}${jimage.dir}/java.base${pathsep}${jimage.dir}/java.rmi${pathsep}${jimage.dir}/java.sql${pathsep}${jimage.dir}/java.naming - -######################################################################## -# These properties are used by the harness. "harness.log.port" -# specifies the port that server components use to send logging -# output back to JavaTest. If the default port # is not available -# on the machine running JavaTest, then you can set it here. -# -# @harness.temp.directory directory location used by the -# harness to store temporary files -# -# @harness.log.port the port the harness listens on for log mesages -# from remote clients -# -# @harness.log.traceflag used to turn on/off verbose debugging output -# for the tests. -# -# @harness.log.delayseconds Number of seconds to delay to allow -# reporting from remote clients to finish. -# -# @harness.executeMode used to run the harness in the following modes -# of execution: 2 - run only -# -# @harness.socket.retry.count - denotes the number of time we should -# attempt to create a server socket when intilizing a test -# client. The socket is used for logging purposes. -######################################################################## -harness.temp.directory=${ts.home}/tmp -harness.log.port=2000 -harness.log.traceflag=false -harness.log.delayseconds=1 -harness.executeMode=2 -harness.socket.retry.count=10 - -############################################################### -# @tz - your local timezone. For valid values, consult your -# Operating System documentation. -############################################################### -tz=US/Eastern - -######################################################################## -# @javatest.timeout.factor This property specifies the scale factor used by -# Javatest to adjust the time JavaTest will wait for a given test to -# complete before returning failure. For instance if the default test timeout -# is 5 minutes, this value will be multiplied by 5 minutes to determine -# the total timeout delay. Note: this value only works with Javatest's -# batch mode (runclient). When using the Javatest GUI users must change -# this timeout factor in the GUI. Configure -> Edit Configuration -> View -# -> choose Standard Values -> select tab Execution -> set Time Factor. -######################################################################## -javatest.timeout.factor=1.0 - -####################################################################### -#build level -####################################################################### -#1: compile only -#2: compile and build component archives (e.g., jar's, war's) -build.level=2 - -############################################################### -# @ts.display -- location to display JSON-B output on Unix -############################################################### -ts.display=:0.0 - -####################################################################### -# default deliverable class -####################################################################### -deliverable.class=com.sun.ts.lib.deliverable.jsonb.JSONBDeliverable - -############################################################### -## This command allows the test clients to be run in -## the same JVM as JavaTest in this case. This mode can be -## enabled by passing "-Dsame.jvm=true" to the runclient or gui -## targets. NOTE: This option is only to be used for sanity -## checking and not when running the TCK for compatibility. -############################################################### -command.testExecuteSameJVM=com.sun.ts.lib.harness.ExecuteTSTestSameJVMCmd \ - $testExecuteClass $testExecuteArgs - -######################################################################## -## Common environment for both ts_unix and ts_win32 -######################################################################## -command.testExecute=com.sun.ts.lib.harness.ExecTSTestCmd \ - CLASSPATH=${ts.run.classpath} \ - DISPLAY="${ts.display}" \ - HOME="${user.home}" \ - windir=${windir} \ - SYSTEMROOT=${SYSTEMROOT} \ - ${JAVA_HOME}/bin/java \ - -Djava.security.policy="${bin.dir}/harness.policy" \ - -Djava.security.manager \ - -Ddeliverable.class=${deliverable.class} \ - $testExecuteClass $testExecuteArgs - -######################################################################### -## Environment for ts_unix -## The test execution commands inherit from common environment -## defined above: testExecute. -## If you need to override it, uncomment it in the following section. -######################################################################### -env.ts_unix.menu=true - -######################################################################## -## Environment for ts_win32 -## The test execution commands inherit from common environment -## defined above: testExecute. -## If you need to override it, uncomment it in the following section. -######################################################################## -env.ts_win32.menu=true - -###################################################################### -## Deliverables must set this property to the name of the deliverable -## specific library jar file (if create.manifest.extension.entries -## is set to true) -###################################################################### -tslib.name=jsonbtck - -############################################################### -# @extension.dir - The extension directory of RI. -# The CTS config.vi target will copy the CTS library -# jars to this location, used only for RI. -############################################################### -extension.dir=${web.home}/domains/domain1/lib - diff --git a/install/jsonb/bin/ts.jtx b/install/jsonb/bin/ts.jtx deleted file mode 100644 index 922aedf8bc..0000000000 --- a/install/jsonb/bin/ts.jtx +++ /dev/null @@ -1,33 +0,0 @@ -# -# Copyright (c) 2017, 2019 Oracle and/or its affiliates. All rights reserved. -# -# This program and the accompanying materials are made available under the -# terms of the Eclipse Public License v. 2.0, which is available at -# http://www.eclipse.org/legal/epl-2.0. -# -# This Source Code may also be made available under the following Secondary -# Licenses when the conditions for such availability set forth in the -# Eclipse Public License v. 2.0 are satisfied: GNU General Public License, -# version 2 with the GNU Classpath Exception, which is available at -# https://www.gnu.org/software/classpath/license.html. -# -# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 -# - -# -# Bug ID: https://github.com/eclipse-ee4j/jsonb-api/issues/180 -# -com/sun/ts/tests/jsonb/defaultmapping/basictypes/BasicJavaTypesMappingTest.java#testLongMapping_from_standalone -com/sun/ts/tests/jsonb/defaultmapping/bignumbers/BigNumbersMappingTest.java#testBigNumberMarshalling_from_standalone - -# -# Bug ID: https://github.com/eclipse-ee4j/jakartaee-tck/issues/102 -# -com/sun/ts/tests/jsonb/defaultmapping/dates/DatesMappingTest.java#testGregorianCalendarWithTimeMapping_from_standalone - -# -# Bug ID: https://github.com/eclipse-ee4j/jakartaee-tck/issues/103 -# -com/sun/ts/tests/jsonb/defaultmapping/collections/CollectionsMappingTest.java#testEnumMap_from_standalone -com/sun/ts/tests/jsonb/defaultmapping/collections/CollectionsMappingTest.java#testEnumSet_from_standalone - diff --git a/install/jsonb/bin/xml/impl/glassfish/config.vi.xml b/install/jsonb/bin/xml/impl/glassfish/config.vi.xml deleted file mode 100644 index 03556f3966..0000000000 --- a/install/jsonb/bin/xml/impl/glassfish/config.vi.xml +++ /dev/null @@ -1,144 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/install/jsonb/docs/JSONB2.0-ReleaseNotes.html b/install/jsonb/docs/JSONB2.0-ReleaseNotes.html deleted file mode 100644 index 0a3afaac67..0000000000 --- a/install/jsonb/docs/JSONB2.0-ReleaseNotes.html +++ /dev/null @@ -1,99 +0,0 @@ - - - - - Jakarta EE JSON Binding TCK, Release Notes - - - -
-

Jakarta EE JSON Binding Technology Compatibility Kit, - Version 2.0

-

- Release Notes, May 2021

-
-

Kit Contents

-

The Jakarta EE JSON Binding (JSON-B), Version 2.0 Technology - Compatibility Kit (TCK) includes the following items:

-
    -
  • -

    Jakarta EE JSON-B TCK tests signature, API, and end-to-end - tests:

    -
      -
    • -

      A signature test that checks that all of the - public APIs are supported in the Jakarta EE JSON-B Version 2.0 - implementation that is being tested

      -
      • -
    • -

      API tests for all of the public APIs under the jakarta.json.bind - package

      -
      • -
    • -

      Specification tests for the testable assertions - required by the Jakarta EE JSON-B 2.0 Specification.

      -
      • -
    -
    • -
-
-

Jakarta EE JSON Binding 2.0 TCK Facts

-

The test suite bundle contains the following:

-
    -
  • 266 total tests
    • -
-
-

Platform Notes

-

The Jakarta EE JSON-B TCK tests have been built with JDK 8 (1.8) and - tested running on the JavaTM - Standard Edition 8 and 11.

-

The Jakarta EE JSON-B TCK tests run on the following platforms:

-
    -
  • CentOS Linux 7
    • -
  • Alpine Linux v3.12
    • -
-
-

Installing, Setting Up, and Running the - Jakarta EE JSON Binding TCK

-

Refer to the Jakarta EE - JSON Binding TCK 2.0 User's Guide (or PDF) for - complete instructions on installing, setting up, and running the Jakarta - EE JSON-B TCK. - The online version of the JT Harness version 5.0 documentation is - available here.

-
-

Attributions

-

The Jakarta EE JSON-B 2.0 TCK includes software developed by the Apache - Software Foundation (http://www.apache.org/). - The Apache Ant Contrib project is located at http://ant-contrib.sourceforge.net/.

-
-

Copyright 2017, 2021 Oracle and/or its affiliates. All - rights reserved.

- - diff --git a/install/jsonb/docs/assertions/JSONB20JavadocAssertions.html b/install/jsonb/docs/assertions/JSONB20JavadocAssertions.html deleted file mode 100644 index 41260de61b..0000000000 --- a/install/jsonb/docs/assertions/JSONB20JavadocAssertions.html +++ /dev/null @@ -1,846 +0,0 @@ - - - - - -JavaDoc Assertion Detail - - -
-
-

Jakarta JSON Binding - 2.0
- JavaDoc Assertion Detail -

-
- - - - - - - - - - - -
TotalsTotalActiveDeprecatedRemoved
- # of Assertions - 808000
- # of Required Assertions - 808000
- # of Optional Assertions - 0000
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IDReturnMethod/FieldDescriptionRequiredDeprecatedTestable
JSONB:JAVADOC:1Objectjakarta.json.bind.Jsonb.fromJson
- - ( - String - ,
Class - ) - 		Reads in a JSON data from the specified string and return the resulting content tree.true -
-		true
JSONB:JAVADOC:2Objectjakarta.json.bind.Jsonb.fromJson
- - ( - String - ,
Class - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:3Objectjakarta.json.bind.Jsonb.fromJson
- - ( - String - ,
Type - ) - 		Reads in a JSON data from the specified string and return the resulting content tree.true -
-		true
JSONB:JAVADOC:4Objectjakarta.json.bind.Jsonb.fromJson
- - ( - String - ,
Type - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:5Objectjakarta.json.bind.Jsonb.fromJson
- - ( - Reader - ,
Class - ) - 		Reads in a JSON data from the specified Reader and return the resulting content tree.true -
-		true
JSONB:JAVADOC:6Objectjakarta.json.bind.Jsonb.fromJson
- - ( - Reader - ,
Class - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:7Objectjakarta.json.bind.Jsonb.fromJson
- - ( - Reader - ,
Type - ) - 		Reads in a JSON data from the specified Reader and return the resulting content tree.true -
-		true
JSONB:JAVADOC:8Objectjakarta.json.bind.Jsonb.fromJson
- - ( - Reader - ,
Type - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:9Objectjakarta.json.bind.Jsonb.fromJson
- - ( - InputStream - ,
Class - ) - 		Reads in a JSON data from the specified InputStream and return the resulting content tree.true -
-		true
JSONB:JAVADOC:10Objectjakarta.json.bind.Jsonb.fromJson
- - ( - InputStream - ,
Class - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:11Objectjakarta.json.bind.Jsonb.fromJson
- - ( - InputStream - ,
Type - ) - 		Reads in a JSON data from the specified InputStream and return the resulting content tree.true -
-		true
JSONB:JAVADOC:12Objectjakarta.json.bind.Jsonb.fromJson
- - ( - InputStream - ,
Type - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:13Stringjakarta.json.bind.Jsonb.toJson
- - ( - Object - ) - 		Writes the Java object tree with root object object to a String instance as JSON.true -
-		true
JSONB:JAVADOC:14Stringjakarta.json.bind.Jsonb.toJson
- - ( - Object - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization, such as I/O error.true -
-		false
JSONB:JAVADOC:15Stringjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ) - 		Writes the Java object tree with root object object to a String instance as JSON.true -
-		true
JSONB:JAVADOC:16Stringjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization, such as I/O error.true -
-		false
JSONB:JAVADOC:17voidjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
Writer - ) - 		Writes the object content tree into a Writer character stream.true -
-		true
JSONB:JAVADOC:18voidjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
Writer - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization.true -
-		false
JSONB:JAVADOC:19voidjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ,
Writer - ) - 		Writes the object content tree into a Writer character stream.true -
-		true
JSONB:JAVADOC:20voidjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ,
Writer - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization.true -
-		false
JSONB:JAVADOC:21voidjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
OutputStream - ) - 		Writes the object content tree into output stream.true -
-		true
JSONB:JAVADOC:22voidjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
OutputStream - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization.true -
-		false
JSONB:JAVADOC:23voidjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ,
OutputStream - ) - 		Writes the object content tree into output stream.true -
-		true
JSONB:JAVADOC:24voidjakarta.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ,
OutputStream - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization.true -
-		false
JSONB:JAVADOC:25Jsonbjakarta.json.bind.JsonbBuilder.build
-		Returns a new instance of jakarta.json.bind.Jsonb Jsonb based on the parameters and configuration specified previously in this builder.true -
-		true
JSONB:JAVADOC:26Jsonbjakarta.json.bind.JsonbBuilder.create
-		Create a new jakarta.json.bind.Jsonb instance using the default JsonbBuilder implementation provided as returned from jakarta.json.bind.spi.JsonbProvider#provider() method.true -
-		true
JSONB:JAVADOC:27Jsonbjakarta.json.bind.JsonbBuilder.create
- - ( - JsonbConfig - ) - 		Create a new jakarta.json.bind.Jsonb instance using the default JsonbBuilder implementation provided as returned from jakarta.json.bind.spi.JsonbProvider#provider() method, configured with provided configuration.true -
-		true
JSONB:JAVADOC:28JsonbBuilderjakarta.json.bind.JsonbBuilder.newBuilder
-		Create a new JsonbBuilder instance as returned by the default jakarta.json.bind.spi.JsonbProvider#provider() method.true -
-		true
JSONB:JAVADOC:29JsonbBuilderjakarta.json.bind.JsonbBuilder.newBuilder
- - ( - String - ) - 		Create a new JsonbBuilder instance as returned by jakarta.json.bind.spi.JsonbProvider#provider(String) method.true -
-		true
JSONB:JAVADOC:30JsonbBuilderjakarta.json.bind.JsonbBuilder.newBuilder
- - ( - JsonbProvider - ) - 		Create a new JsonbBuilder instance as returned by provider#create call.true -
-		true
JSONB:JAVADOC:31JsonbBuilderjakarta.json.bind.JsonbBuilder.withConfig
- - ( - JsonbConfig - ) - 		Set configuration which will be set to the newly created jakarta.json.bind.Jsonb Jsonb instance.true -
-		true
JSONB:JAVADOC:32JsonbBuilderjakarta.json.bind.JsonbBuilder.withProvider
- - ( - JsonProvider - ) - 		Provides a JSON-P provider to be used for all JSON-P related operations.true -
-		true
JSONB:JAVADOC:33Mapjakarta.json.bind.JsonbConfig.getAsMap
-		Return all configuration properties as an unmodifiable map.true -
-		true
JSONB:JAVADOC:34Optionaljakarta.json.bind.JsonbConfig.getProperty
- - ( - String - ) - 		Return value of particular configuration property. The method can only be used to retrieve one of the standard JSON Binding properties defined in this class or a provider specific property. Attempting to get an undefined property will result in an empty Optional value. See Supported Properties.true -
-		true
JSONB:JAVADOC:35JsonbConfigjakarta.json.bind.JsonbConfig.JsonbConfig
-		 -
-		true -
-		true
JSONB:JAVADOC:36JsonbConfigjakarta.json.bind.JsonbConfig.setProperty
- - ( - String - ,
Object - ) - 		Set the particular configuration property to a new value. The method can only be used to set one of the standard JSON Binding properties defined in this class or a provider specific property.true -
-		true
JSONB:JAVADOC:37JsonbConfigjakarta.json.bind.JsonbConfig.withAdapters
- - ( - JsonbAdapter[] - ) - 		Property used to specify custom mapping adapters. Configures value of ADAPTERS property. Calling withAdapters more than once will merge the adapters with previous value.true -
-		true
JSONB:JAVADOC:38JsonbConfigjakarta.json.bind.JsonbConfig.withBinaryDataStrategy
- - ( - String - ) - 		Property used to specify custom binary data strategy. Configures value of BINARY_DATA_STRATEGY property.true -
-		true
JSONB:JAVADOC:39JsonbConfigjakarta.json.bind.JsonbConfig.withDateFormat
- - ( - String - ,
Locale - ) - 		Property used to specify custom date format. This format will be used by default for all date classes serialization and deserialization.true -
-		true
JSONB:JAVADOC:40JsonbConfigjakarta.json.bind.JsonbConfig.withDeserializers
- - ( - JsonbDeserializer[] - ) - 		Property used to specify custom deserializers. Configures value of DESERIALIZERS property. Calling withDeserializers more than once will merge the deserializers with previous value.true -
-		true
JSONB:JAVADOC:41JsonbConfigjakarta.json.bind.JsonbConfig.withEncoding
- - ( - String - ) - 		The binding operations will default to this property for encoding of JSON data. For input data (fromJson), selected encoding is used if the encoding cannot be detected automatically. Default value is 'UTF-8'. Configures value of ENCODING property.true -
-		true
JSONB:JAVADOC:42JsonbConfigjakarta.json.bind.JsonbConfig.withFormatting
- - ( - Boolean - ) - 		Property used to specify whether or not the serialized JSON data is formatted with linefeeds and indentation. Configures value of FORMATTING property.true -
-		true
JSONB:JAVADOC:43JsonbConfigjakarta.json.bind.JsonbConfig.withLocale
- - ( - Locale - ) - 		Property used to specify custom locale.true -
-		true
JSONB:JAVADOC:44JsonbConfigjakarta.json.bind.JsonbConfig.withNullValues
- - ( - Boolean - ) - 		Property used to specify whether null values should be serialized to JSON document or skipped. Configures value of NULL_VALUES property.true -
-		true
JSONB:JAVADOC:45JsonbConfigjakarta.json.bind.JsonbConfig.withPropertyNamingStrategy
- - ( - PropertyNamingStrategy - ) - 		Property used to specify custom naming strategy. Configures value of JSONB_PROPERTY_NAMING_STRATEGY property.true -
-		true
JSONB:JAVADOC:46JsonbConfigjakarta.json.bind.JsonbConfig.withPropertyNamingStrategy
- - ( - String - ) - 		Property used to specify custom naming strategy. Configures value of JSONB_PROPERTY_NAMING_STRATEGY property.true -
-		true
JSONB:JAVADOC:47JsonbConfigjakarta.json.bind.JsonbConfig.withPropertyOrderStrategy
- - ( - String - ) - 		Property used to specify property order strategy. Configures values of JSONB_PROPERTY_ORDER_STRATEGY property.true -
-		true
JSONB:JAVADOC:48JsonbConfigjakarta.json.bind.JsonbConfig.withPropertyVisibilityStrategy
- - ( - PropertyVisibilityStrategy - ) - 		Property used to specify custom property visibility strategy. Configures value of PROPERTY_VISIBILITY_STRATEGY property.true -
-		true
JSONB:JAVADOC:49JsonbConfigjakarta.json.bind.JsonbConfig.withSerializers
- - ( - JsonbSerializer[] - ) - 		Property used to specify custom serializers. Configures value of SERIALIZERS property. Calling withSerializers more than once will merge the serializers with previous value.true -
-		true
JSONB:JAVADOC:50JsonbConfigjakarta.json.bind.JsonbConfig.withStrictIJSON
- - ( - Boolean - ) - 		Property used to specify whether strict I-JSON serialization compliance should be enforced. Configures value of STRICT_IJSON property.true -
-		true
JSONB:JAVADOC:51JsonbExceptionjakarta.json.bind.JsonbException.JsonbException
- - ( - String - ) - 		Constructs a new runtime exception with the specified detail message. The cause is not initialized, and may subsequently be initialized by a call to #initCause.true -
-		true
JSONB:JAVADOC:52JsonbExceptionjakarta.json.bind.JsonbException.JsonbException
- - ( - String - ,
Throwable - ) - 		Constructs a new runtime exception with the specified detail message and cause. Note that the detail message associated with cause is not automatically incorporated in this runtime exception's detail message.true -
-		true
JSONB:JAVADOC:53Objectjakarta.json.bind.adapter.JsonbAdapter.adaptFromJson
- - ( - Object - ) - 		This method is used on deserialization only. It contains a conversion logic from type Adapted to type Original.true -
-		true
JSONB:JAVADOC:54Objectjakarta.json.bind.adapter.JsonbAdapter.adaptFromJson
- - ( - Object - ) -
throws - Exception
-		if there is an error during the conversion.true -
-		false
JSONB:JAVADOC:55Objectjakarta.json.bind.adapter.JsonbAdapter.adaptToJson
- - ( - Object - ) - 		This method is used on serialization only. It contains a conversion logic from type Original to type Adapted. After conversion Adapted type will be mapped to JSON the standard way.true -
-		true
JSONB:JAVADOC:56Objectjakarta.json.bind.adapter.JsonbAdapter.adaptToJson
- - ( - Object - ) -
throws - Exception
-		if there is an error during the conversion.true -
-		false
JSONB:JAVADOC:57Stringjakarta.json.bind.annotation.JsonbDateFormat.locale
-		Custom java.util.Locale to use.true -
-		true
JSONB:JAVADOC:58Stringjakarta.json.bind.annotation.JsonbDateFormat.value
-		Specifies the date pattern to use.true -
-		true
JSONB:JAVADOC:59booleanjakarta.json.bind.annotation.JsonbNillable.value
-		True if field with null value should be serialized as key/value pair into JSON with null value.true -
-		true
JSONB:JAVADOC:60Stringjakarta.json.bind.annotation.JsonbNumberFormat.locale
-		Custom java.util.Locale to use.true -
-		true
JSONB:JAVADOC:61Stringjakarta.json.bind.annotation.JsonbNumberFormat.value
-		Specifies the number pattern to use.true -
-		true
JSONB:JAVADOC:62booleanjakarta.json.bind.annotation.JsonbProperty.nillable
-		True if field with null value should be serialized as key/value pair into JSON with null value.true -
-		true
JSONB:JAVADOC:63Stringjakarta.json.bind.annotation.JsonbProperty.value
-		Customized name of the field (or JavaBean property).true -
-		true
JSONB:JAVADOC:64String[]jakarta.json.bind.annotation.JsonbPropertyOrder.value
-		Order in which properties are serialized. Names must correspond to original names defined in Java class before any customization applied.true -
-		true
JSONB:JAVADOC:65Classjakarta.json.bind.annotation.JsonbTypeAdapter.value
-		Custom JsonbAdapter which provides custom mapping for given field or JavaBean property.true -
-		true
JSONB:JAVADOC:66Classjakarta.json.bind.annotation.JsonbTypeDeserializer.value
-		Custom JsonbDeserializer which provides custom mapping for given field or JavaBean property.true -
-		true
JSONB:JAVADOC:67Classjakarta.json.bind.annotation.JsonbTypeSerializer.value
-		Custom JsonbSerializer which provides custom mapping for given field or JavaBean property.true -
-		true
JSONB:JAVADOC:68Classjakarta.json.bind.annotation.JsonbVisibility.value
-		Custom property visibility strategy used to resolve visibility of the members.true -
-		true
JSONB:JAVADOC:69Stringjakarta.json.bind.config.PropertyNamingStrategy.translateName
- - ( - String - ) - 		Translates the property name into its JSON field name representation.true -
-		true
JSONB:JAVADOC:70booleanjakarta.json.bind.config.PropertyVisibilityStrategy.isVisible
- - ( - Field - ) - 		Responds whether the given field should be considered as the JsonbProperty.true -
-		true
JSONB:JAVADOC:71booleanjakarta.json.bind.config.PropertyVisibilityStrategy.isVisible
- - ( - Method - ) - 		Responds whether the given method should be considered as the JsonbProperty.true -
-		true
JSONB:JAVADOC:72Objectjakarta.json.bind.serializer.DeserializationContext.deserialize
- - ( - Class - ,
JsonParser - ) - 		Deserialize JSON stream into instance of provided class using jakarta.json.stream.JsonParser. JsonParser cursor have to be at KEY_NAME before START_OBJECT / START_ARRAY, or at START_OBJECT / START_ARRAY to call this method. After deserialization is complete JsonParser will be at END_OBJECT / END_ARRAY for deserialized JSON structure. If method is called for the same type, which is deserializer bound to, deserializer recursion is suppressed. Otherwise deserializers are reentrant during deserialization process started by this method. JsonParser instance of JSONB runtime is shared with custom deserializer.true -
-		true
JSONB:JAVADOC:73Objectjakarta.json.bind.serializer.DeserializationContext.deserialize
- - ( - Type - ,
JsonParser - ) - 		Deserialize JSON stream into instance of provided class using jakarta.json.stream.JsonParser. JsonParser cursor have to be at KEY_NAME before START_OBJECT / START_ARRAY, or at START_OBJECT / START_ARRAY to call this method. After deserialization is complete JsonParser will be at END_OBJECT / END_ARRAY for deserialized JSON structure. If method is called for the same type, which is deserializer bound to, deserializer recursion is suppressed. Otherwise deserializers are reentrant during deserialization process started by this method. JsonParser instance of JSONB runtime is shared with custom deserializer.true -
-		true
JSONB:JAVADOC:74Objectjakarta.json.bind.serializer.JsonbDeserializer.deserialize
- - ( - JsonParser - ,
DeserializationContext - ,
Type - ) - 		Deserialize JSON stream into object.true -
-		true
JSONB:JAVADOC:75voidjakarta.json.bind.serializer.JsonbSerializer.serialize
- - ( - Object - ,
JsonGenerator - ,
SerializationContext - ) - 		Serializes object into JSON stream.true -
-		true
JSONB:JAVADOC:76voidjakarta.json.bind.serializer.SerializationContext.serialize
- - ( - String - ,
Object - ,
JsonGenerator - ) - 		Serializes arbitrary object to JSON, using current jakarta.json.stream.JsonGenerator instance. Serialization is ran as serialization of a root type from user JsonbSerializer. JsonGenerator instance is shared with JSONB and user serializer.true -
-		true
JSONB:JAVADOC:77voidjakarta.json.bind.serializer.SerializationContext.serialize
- - ( - Object - ,
JsonGenerator - ) - 		Serializes arbitrary object to JSON, using current jakarta.json.stream.JsonGenerator instance. Serialization is ran as serialization of a root type from user JsonbSerializer. JsonGenerator instance is shared with JSONB and user serializer. Method without key parameter is intended to serialize inside JSON_ARRAYs.true -
-		true
JSONB:JAVADOC:78JsonbBuilderjakarta.json.bind.spi.JsonbProvider.create
-		Returns a new instance of jakarta.json.bind.JsonbBuilder JsonbBuilder class. jakarta.json.bind.JsonbBuilder JsonbBuilder provides necessary getter methods to access required parameters.true -
-		true
JSONB:JAVADOC:80JsonbProviderjakarta.json.bind.spi.JsonbProvider.provider
-		Creates a JSON Binding provider object by using the java.util.ServiceLoader#load(Class) method. The first provider of JsonbProvider class from list of providers returned by ServiceLoader.load call is returned. If there are no available service providers, this method tries to load the default service provider using Class#forName(String) method.true -
-		true
JSONB:JAVADOC:81JsonbProviderjakarta.json.bind.spi.JsonbProvider.provider
- - ( - String - ) - 		Creates a JSON Binding provider object by using the java.util.ServiceLoader#load(Class) method, matching providerName. The first provider of JsonbProvider class from list of providers returned by ServiceLoader.load call, matching providerName is returned. If no such provider is found, JsonbException is thrown.true -
-		true
- - diff --git a/install/jsonb/docs/assertions/Jsonb20SpecAssertions.html b/install/jsonb/docs/assertions/Jsonb20SpecAssertions.html deleted file mode 100644 index 873c6877f7..0000000000 --- a/install/jsonb/docs/assertions/Jsonb20SpecAssertions.html +++ /dev/null @@ -1,910 +0,0 @@ - - - - - -Specification Assertion Detail - - -
-
-

Jakarta JSON Binding - 2.0
- Specification Assertion Detail -

-
- - - - - - - - - - - -
TotalsTotalActiveDeprecatedRemoved
- # of Assertions - 15215101
- # of Required Assertions - 14514401
- # of Optional Assertions - 7700
-
Assertions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IDChapterSectionDescriptionRequiredDependencyImplementation SpecificDefined byStatusTestable
JSONB:SPEC:JSB-3.1-133.1JSON Binding implementations MUST support binding of JSON documents as defined in RFC 7159 JSON Grammar. Serialized JSON output MUST conform to the RFC 7159 JSON Grammar and be encoded in UTF-8 encoding as defined in Section 8.1 (Character Encoding) of RFC 7159 - true -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-233.1Implementations MUST support deserialization of documents conforming to RFC 7159 JSON Grammartrue -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-333.1In addition, implementations SHOULD NOT allow deserialization of RFC 7159 non-conforming text (e.g. unsupported encoding, ...) and report error in such casefalse -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-433.1Detection of UTF encoding of deserialized document is done as defined in the Section 3 (Encoding) of RFC 4627true -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-533.1Implementations SHOULD ignore presence of UTF byte order mark (BOM) and not treat it as an error.false -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.2-133.2Implementations SHOULD NOT allow unmarshalling of RFC 7159 non-conforming text (e.g. unsupported encoding) and report error in such case.false -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.2-233.2Implementation SHOULD also report error also during unmarshalling operation, if it is not possible to represent JSON document value in the expected Java typefalse -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.3-133.3Implementation MUST report binding of the following basic java classes and their corresponding primitive types -java.lang.String -java.lang.Character -java.lang.Byte -java.lang.Short -java.lang.Integer -java.lang.Long -java.lang.Float -java.lang.Double -java.lang.Booleantrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.1-133.3.1Instances of type java.lang.String and java.lang.Character are marshalled to JSON String values as defined within RFC 7159 Section 7 (Strings) in UTF-8 encoding without byte order mark. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.1-233.3.2Implementations SHOULD support deserialization of JSON text in other (than UTF-8) UTF encodings into java.lang.String instancesfalse -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.2-133.3.2Serialization of type java.lang.Byte, Short, Integer, Long, Float, Double and their corresponding primitive types to JSON Number MUST follow the conversion process defined in javadoc specification for the corresponding toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.2-233.3.2Deserialization of a JSON value into java.lang.Byte, Short, Integer, Long, Float, Double instance or corresponding primitive type MUST follow the conversion process as defined in the specification for their corresponding parse$Type method, such as java.lang.Byte.parseByte for Byte.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.3-133.3.3Serialization of type java.lang.Boolean and its corresponding boolean primitive type to JSON value MUST follow conversion process defined in specification for java.lang.Boolean.toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.3-233.3.3Deserialization of a JSON value into java.lang.Boolean instance or boolean primitive type MUST follow the conversion process as defined in specification for java.lang.Boolean.parseBoolean method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.4-133.3.4Serialization of type java.lang.Number (if their more concrete type is not defined elsewhere in this chapter) to JSON string MUST retrieve double value returned from java.lang.Number.doubleValue() method and converting the value to JSON Number as defined in subsection 3.3.2true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.4-233.3.4Deserialization of a JSON value into Java type java.lang.Number should return instance of java.math.BigDecimal by using conversion as defined in the specification for constructor of java.math.BigDecimal with java.lang.String.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4-133.4Implementations MUST support binding of the following standard Java SE classes: -java.math.BigInteger -java.math.BigDecimal -java.net.URL -java.net.URI -java.util.Optional -java.util.OptionalInt -java.util.OptionalLong -java.util.OptionalDouble true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.1-133.4.1Serialization of type java.math.BigInteger, BigDecimal to s JSON Number MUST follow the conversion process defined in specification for their toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.1-233.4.2Deserialization of JSON value into java.math.BigInteger, BigDecimal instance MUST follow the conversion process as defined in the specification for constructor of java.math.BigInteger, BigDecimal with java.lang.String.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.2-133.4.2Serialization of type java.net.URL, URI to a JSON String value MUST follow the conversion process defined in specification for their toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.2-233.4.2Deserialization of a JSON value into java.net.URL, URI instance MUST follow the conversion process as defined in the specification for constructor of java.net.URL, URI with java.lang.String input.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-133.4.3Non-empty instances of type java.util.Optional, OptionalInt, OptionalLong, OptionalDouble are serialized to a JSON value by retrieving their contained instance and converting it to JSON value based on its type and corresponding mapping definitions within this chapter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-233.4.3Class fields containing empty optional instances are treated as having a null value and serialized based on 3.14.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-333.4.3Empty optional instances in array items are serialized as null.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-433.4.3Deserializing into Optional, OptionalInt, OptionalLong, OptionalDouble return empty optional value for properties containing a null value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-533.4.3Otherwise any non-empty Optional, OptionalInt, OptionalLong, OptionalDouble value is constructed of type unmarshalled based on mappings defined in this chapter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-633.4.3Instances of type java.util.Optional T are serialized to a JSON value as JSON objects when T alone would be serialized as JSON object. When T would be serialized as a JSON value (e.g. java.lang.String, java.lang.Integer), an instance of java.util.Optional T is serialized as a JSON value (without curly brackets).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-733.4.3Deserialization of a JSON value into java.util.Optional(T) MUST be supported if deserialization of a JSON value into instance of T is supported.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-133.5Implementations MUST support binding of the following standard Java date/time classes: java.util.Date -java.util.Calendar -java.util.GregorianCalendar -java.util.TimeZone -java.util.SimpleTimeZone -java.time.Instant -java.time.Duration -java.time.Period -java.time.LocalDate -java.time.LocalTime -java.time.LocalDateTime -java.time.ZonedDateTime -java.time.ZoneId -java.time.ZoneOffset -java.time.OffsetDateTime -java.time.OffsetTimetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-233.5If not specified otherwise in this section, GMT standard time zone and offset specified from UTC Greenwich is used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-333.5If not specified otherwise, date time format for marshalling and unmarshalling is ISO 8601 without offset, as specified in java.time.format.DateTimeFormatter.ISO_DATE.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-433.5Implementations MUST report error if the date/time string in JSON document does not correspond to the expected datetime format. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-533.5If in strict I-JSON compliance mode, default date format is changed as it’s described in 4.4.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-133.5.1The serialization format of java.util.Date, Calendar, GregorianCalendar instances with no time information is ISO_DATE.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-233.5.1If time information is present, the format is ISO_DATE_TIMEtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-333.5.1Implementations MUST support deserialization of both ISO_DATE and ISO_DATE_TIME into java.util.Date, Calendar and GregorianCalendar instances.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-133.5.2Implementations MUST support deserialization of any time zone format specified in java.util.TimeZone into a field or property of type java.util.TimeZone and SimpleTimeZone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-233.5.2Implementations MUST report an error for deprecated three-letter time zone IDs as specified in java.util.Timezone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-333.5.2The serialization format of java.util.TimeZone and SimpleTimeZone is NormalizedCustomID as specified in java.util.TimeZone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-133.5.3The serialization output for a java.time.Instant instance MUST be in a ISO_INSTANT format, as specified in java.time.format.DateTimeFormatter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-233.5.3Implementations MUST support the deserialization of an ISO_INSTANT formatted JSON string to a java.time.Instant instance.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-333.5.3Analogically, for other java.time.* classes, following mapping table matches Java types and corresponding formats: -java.time.Instant ISO_INSTANT -java.time.LocalDate ISO_LOCAL_DATE -java.time.LocalTime ISO_LOCAL_TIME -java.time.LocalDateTime ISO_LOCAL_DATE_TIME -java.time.ZonedDateTime ISO_ZONED_DATE_TIME -java.time.OffsetDateTime ISO_OFFSET_DATE_TIME -java.time.OffsetTime ISO_OFFSET_TIMEtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-433.5.3Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneId into a field or property of type java.time.ZoneId.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-533.5.3The serialization format of java.time.ZoneId is the normalized zone ID as specified in java.time.ZoneId.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-633.5.3Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneOffset into a field or property of type java.time.ZoneOffset.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-733.5.3The serialization format of java.time.ZoneOffset is the normalized zone ID as specified in java.time.ZoneOffset.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-833.5.3Implementations MUST support the deserialization of any duration format specified in java.time.Duration into a field or property of type java.time.Duration.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-933.5.3This is super-set of ISO 8601 duration format. The serialization format of java.time.Duration is the ISO 8601 seconds based representation, such as PT8H6M12.345S.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1033.5.3Implementations MUST support the deserialization of any period format specified in java.time.Period into a field or property of type java.time.Period.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1133.5.3This is a super-set of ISO 8601 period format. The serialization format of java.time.Period is ISO 8601 period representation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1233.5.3A zero-length period is represented as zero days 'P0D'.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.6-133.6For an unspecified output type of a deserialization operation, as well as where output type is specified as Object.class, implementations MUST deserialize a JSON document using Java runtime types specified in table below: -object java.util.Map String,Object -array java.util.List Object -string java.lang.String -number java.math.BigDecimal -true, false java.lang.Boolean -null null -true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.6-233.6JSON object values are deserialized into an implementation of java.util.Map(String, Object) with a predictable iteration order.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7-133.7Any instance passed to a deserialization operation must have a public or protected no-argument constructor. Implementations SHOULD throw an error if this condition is not met.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7-233.7This limitation does not apply to serialization operations, as well as to classes which specify explicit instantiation methods as described in section 4.5.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-133.7.1For a deserialization operation of a Java property, if a matching public setter method exists, the method is called to set the value of the property. If a matching setter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching setter method exists and the field is public, then direct field assignment is used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-233.7.1For a serialization operation, if a matching public getter method exists, the method is called to obtain the value of the property. If a matching getter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching getter method exists and the field is public, then the value is obtained directly from the field.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-333.7.1JSON Binding implementations MUST NOT deserialize into transient, final or static fields and MUST ignore name/value pairs corresponding to such fields.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-433.7.1Implementations MUST support serialization of final fields.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-533.7.1Transient and static fields MUST be ignored during serialization operation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-633.7.1If a JSON document contains a name/value pair not corresponding to field or setter method, then this name/value pair MUST be ignored.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-733.7.1Public getter/setter methods without a corresponding field MUST be supported. When only public getter/setter method without corresponding field is present in the class, the getter method is called to obtain the value to serialize, and the setter method is called during deserialization operation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.2-133.7.2Implementations MUST support the binding of public and protected nested classes.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.2-233.7.2For deserialization operations, both nested and encapsulating classes MUST fulfill the same instantiation requirements as specified in 3.7.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.3-133.7.3Implementations MUST support the binding of public and protected static nested classes.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.3-233.7.3For deserialization operations, the nested class MUST fulfill the same instantiation requirements as specified in 3.7.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.4-133.7.4Deserialization into anonymous classes is not supported. Serialization of anonymous classes is supported by default object mapping.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.8-133.8Deserialization into polymorphic types is not supported by default mapping.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.9-133.9Serialization of an Enum instance to a JSON String value MUST follow the conversion process defined in javadoc specification for their name().true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.9-233.9Deserialization of a JSON value into an enum instance MUST be done by calling the enum’s valueOf(String) method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-133.10Implementations MUST support the deserialization of specific interfaces defined in 3.11 and 3.3.4.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-233.10Deserialization to other interfaces is not supported and implementations SHOULD report error in such case.false -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-333.10If a class property is defined with an interface and not concrete type, then the mapping for a serialized property is resolved based on its runtime type.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.11-133.11Implementations MUST support binding of the following collection interfaces, classes and their implementations. -java.util.Collection -java.util.Map -java.util.Set -java.util.HashSet -java.util.NavigableSet -java.util.SortedSet -java.util.TreeSet -java.util.LinkedHashSet -java.util.TreeHashSet -java.util.HashMap -java.util.NavigableMap -java.util.SortedMap -java.util.TreeMap -java.util.LinkedHashMap -java.util.TreeHashMap -java.util.List -java.util.ArrayList -java.util.LinkedList -java.util.Deque -java.util.ArrayDeque -java.util.Queue -java.util.PriorityQueue -java.util.EnumSet -java.util.EnumMap - -true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.11-233.11Implementations of interfaces below must provide accessible default constructor. JSON Binding implementations MUST report unmarshalling error if default constructor is not present or is not in accessible scope.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.12-133.12JSON Binding implementations MUST support binding of Java arrays of all supported Java types from this chapter into/from JSON array structures as defined in Section 5 of RFC 7159true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.12-233.12Arrays of primitive types and multi-dimensional arrays MUST be supported.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.13-133.13Declared fields MUST be serialized in lexicographical order into the resulting JSON document. In case of inheritance, declared fields of super class MUST be serialized before declared fields of child class.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.13-233.13When deserializing a JSON document, declared fields MUST be set in the order of attributes present in the JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-133.14.1The result of serializing a java field with a null value is the absence of the property in the resulting JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-233.14.1The deserialization operation of a property absent in JSON document MUST not set the value of the field, the setter (if available) MUST not be called, and thus original value of the field MUST be preserved.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-333.14.1The deserialization operation of a property with a null value in a JSON document MUST set the value of the field to null value (or call setter with null value if setter is present). The exception is java.util.Optional, OptionalInt, OptionalLong, OptionalDouble instances. In this case the value of the field is set to an empty optional value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-133.14.2The result of deserialization n-ary array represented in JSON document is n-ary Java array.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-233.14.2Null value in JSON array is represented by null value in Java array.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-333.14.2Serialization operation on Java array with null value at index i MUST output null value at index i of the array in resulting JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-133.15According to RFC 7159 Section 7 , every Java identifier name can be transformed using identity function into a valid JSON String. Identity function MUST be used for transforming Java identifier names into name Strings in JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-233.15For deserialization operations defined in 3.6 section, identity function is used to transform JSON name strings into Java String instances in the resulting map Map(String, Object).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-333.15Identity function is used also for other deseralization operations.true -
-		falsetechnologyremovedtrue
JSONB:SPEC:JSB-3.15-433.15If a Java identifier with corresponding name does not exist or is not accessible, the implementations MUST report error.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.16-133.16JSON Binding implementation MUST serialize numbers that express greater magnitude or precision than an IEEE 754 double precision number as strings.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-133.17JSON Binding implementations MUST support binding of generic types.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-233.17Due to type erasure, there are situations when it is not possible to obtain generic type information. There are two ways for JSON Binding implementations to obtain generic type information. If there is a class file available (in the following text referred as static type information), it is possible to obtain generic type information (effectively generic type declaration) from Signature attribute (if this information is present).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-333.17The second option is to provide generic type information at runtime. To provide generic type information at runtime, an argument of java.lang.reflect.Type MUST be passed to Jsonb::toJson or to Jsonb::fromJson method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-133.17.1There are several levels of information JSON Binding implementations may obtain about the type of field/class/interface: - 1. runtime type provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method - 2. static type provided in class file (effectively stored in Signature attribute) - 3. raw type - 4. no information about the typetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-233.17.1If there is no information about the type, JSON Binding implementation MUST treat this type as java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-333.17.1If only raw type of given field/class/interface is known, then the type MUST be treated like raw type.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-433.17.1For example, if the only available information is that given field/class/interface is of type java.util.ArrayList, than the type MUST be treated as java.util.ArrayList Object. JSON Binding implementations MUST use the most specific type derived from the information available.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-533.17.1Let's consider situation where there is only static type information of a given field/class/interface known, -and there is no runtime type information available. Let GenericClass T1; : : : ; Tn be part of generic type -declaration, where GenericClass is name of the generic type and T1; : : : ; Tn are type parameters. For every -Ti, where i in 1; : : : ; n, there are 3 possible options:true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-633.17.11. Ti is concrete parameter type -2. Ti is bounded parameter type -3. Ti is wildcard parameter type without bounds -In case 1, the most specific parameter type MUST be given concrete parameter type Ti.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-733.17.1For bounded parameter type, using bounds B1; : : : ;Bm. If m = 1, then the most specific parameter type MUST be derived from the given bound B1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-833.17.1If B1 is class or interface, the most specific parameter type MUST be the class or interface.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-933.17.1Otherwise, the most specific parameter type SHOULD be java.lang.Object.false -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1033.17.1If multiple bounds are specified, the first step is to resolve every bound separately. Let’s define result of such resolution as S1; : : : ; Sm specific parameter types. If S1; : : : ; Sm are java.lang.Object, then the bounded parameter type Ti MUST be java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1133.17.1If there is exactly one Sk, where 1 <= k <= m is different than java.lang.Object, then the most specific parameter type for this bounded parameter type Ti MUST be Sk.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1233.17.1If there exists Sk1; Sk2, where 1 <= k1 <= k2 <= m, then the most specific parameter type is Sk1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1333.17.1For wildcard parameter type without bounds, the most specific parameter type MUST be java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1433.17.1Any unresolved type parameter MUST be treated as java.lang.Object. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1533.17.1If runtime type is provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method, than that runtime type overrides static type declaration wherever applicabletrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.18-133.18When JSON Binding implementation encounters key in key/value pair that it does not recognize, it should treat the rest of the JSON document as if the element simply did not appear, and in particular, the implementation MUST NOT treat this as an error condition.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.19-133.19JSON Binding implementations MUST NOT produce JSON documents with members with duplicate names. In this context, "duplicate" means that the names, after processing any escaped characters, are identical sequences of Unicode characters.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.19-233.19When non-unique property (after override and rename) is found, implementation MUST throw an exception. This doesn't apply for customized user serialization behavior implemented with the usage of JsonbAdapter mechanism.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-133.20JSON Binding implementations MUST support binding of the following JSON Processing types. - -jakarta.json.JsonObject -jakarta.json.JsonArray -jakarta.json.JsonStructure -jakarta.json.JsonValue -jakarta.json.JsonPointer -jakarta.json.JsonString -jakarta.json.JsonNumber - true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-233.20Marshalling of supported jakarta.json.* objects/interfaces/fields MUST have the same result as marshalling these objects with jakarta.json.JsonWriter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-333.20Deserialization into supported jakarta.json.* objects/interfaces/fields MUST have the same result as unmarshalling into such objects with jakarta.json.JsonReader.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-144.1.1JSON Binding implementations MUST NOT serialize fields, JavaBean properties or types annotated with jakarta.json.bind.annotation.JsonbTransient.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-244.1.1JsonbTransient annotation is mutually exclusive with all other JSON Binding defined annotations. Implementations must throw JsonbException in the following cases: Class field is annotated with @JsonbTransient. Exception must be thrown when this field, getter or setter is annotated with other JSON Binding annotations.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-344.1.1Getter is annotated with @JsonbTransient. Exception is thrown if when the field or this getter are annotated with other JSON Binding annotations. Exception is not thrown if JSON Binding annotations are presented on the setter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-444.1.1Setter is annotated with @JsonbTransient. Exception is thrown if when the field or this setter are annotated with other JSON Binding annotations. Exception is not thrown if JSON Binding annotations are presented on the getter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-144.1.2To provide custom name for given field (or JavaBean property), -jakarta.json.bind.annotation.JsonbProperty may be used. JsonbProperty annotation may be specified on -field, getter or setter method. If specified on field, custom name is used both for serialization and -deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-244.1.2If jakarta.json.bind.annotation.JsonbProperty is specified on getter method, it is used -only for serialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-344.1.2If jakarta.json.bind.annotation.JsonbProperty is specified on setter method, it is used only for deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-444.1.2It is possible to specify different values for getter and setter method for jakarta.json.bind.annotation.JsonbProperty annotation. In such case the different custom name will be used for serialization and deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.3-144.1.3The way to set custom property naming strategy is to use jakarta.json.bin.JsonbConfig::withPropertyNamingStrategy method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.4-144.1.4If duplicate name is found exception MUST be thrown. The definition of duplicate (non-unique) property -can be found in 3.19.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.244.2The way to set custom property order strategy is to use jakarta.json.bin.JsonbConfig::withPropertyOrderStrategy method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.2-244.2To customize the order of serialized properties only for one specific type, JSON Binding provides jakarta.json.bind.annotation.JsonbPropertyOrder annotation. Order specified by JsonbPropertyOrder annotation overrides order specified by PropertyOrderStrategy.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3-144.3.1If annotations (JsonbNillable or JsonbProperty) on different level apply to the same field (or JavaBean property) or if there is config wide configuration and some annotation (JsonbNillable or JsonbProperty) which apply to the same field (or JavaBean property), the annotation with the smallest scope applies.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-144.3.1When given object (type or package) is annotated with jakarta.json.bind.annotation.JsonbNillable annotation, the result of null value will be presence of associated property in JSON document with explicit null value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-244.3.1The same behavior as JsonbNillable, but only at field, parameter and method (JavaBean property) level is provided by jakarta.json.bind.annotation.JsonbProperty annotation with its nillable parametertrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-344.3.1JSON Binding implementations MUST implement override of annotations according to target of the annotation (FIELD, PARAMETER, METHOD, TYPE, PACKAGE). Type level annotation overrides behavior set at the package level. Method, parameter or field level annotation overrides behavior set at the type level.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.2-144.3.2The way to enforce serialization of null values, is to call method jakarta.json.bind.JsonbConfig::withNullValues with parameter true. The way to skip serialization of null values is to call method jakarta.json.bind.JsonbConfig::withNullValues with parameter false.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4-144.4To enforce strict compliance of serialized JSON documents, JSON Binding implementations MUST implement configuration option jsonb.i-json.strict-ser-compliance.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-144.4.1Uppercase rather than lowercase letters MUST be used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-244.4.1The timezone MUST always be included and optional trailing seconds MUST be included even when their value is 00.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-344.4.1JSON Binding implementations MUST serialize java.util.Date, java.util.Calendar, java.util.GregorianCalendar, java.time.LocalDate, java.time.LocalDateTime and java.time.Instant in the same format as java.time.ZonedDateTime.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-444.4.1The result of serialization of duration must conform to the duration production in Appendix A of RFC 3339, with the same additional restrictionstrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-144.5At most one JsonbCreator annotation can be used to annotate custom constructor or static void factory method in a class, otherwise JsonbException MUST be thrown.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-244.5Factory method annotated with JsonbCreator annotation should return instance of particular class this annotation is used for, otherwise JsonbException MUST be thrown.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-344.5Mapping between parameters of constructor/factory method annotated with JsonbCreator and JSON fields is defined using JsonbProperty annotation on all parameters.In case JsonbProperty annotation on parameters is not used, parameters should be mapped from JSON fields with the same name. In this case the proper mapping is NOT guaranteed.In case a field required for a parameter mapping doesn’t exist in JSON document, JsonbException MUST be thrown.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.6-144.5To customize scope and field access strategy as specified in section 3.7.1, it is possible to specify jakarta.json.bind.annotation.JsonbVisibility annotation or to override default behavior globally calling JsonbConfig::withPropertyVisibilityStrategy method with given custom property visibility strategy.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-144.7.1On serialization of Original type JSONB calls JsonbAdapter::adaptToJson method of the adapter to convert Original to Adapted and serializes Adapted the standard way. There are two ways how to register JsonbAdapter: Using JsonbConfig::withAdapters method;true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-244.7.1Annotating a class field with JsonbTypeAdapter annotation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-344.7.1Implementations must provide a CDI support in adapters to allow injection of CDI managed beans into it.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-144.7.2Serializer is a class implementing jakarta.json.bind.serializers.JsonbSerializer interface. It is used to serialize the type it's registered on (Original). On marshalling of Original type JSONB calls JsonbSerializer::serialize method. This method has to contain a custom code to serialize Original type using provided JsonpGenerator.Deserializer is a class implementing jakarta.json.bind.serializers.JsonbDeserializer interface. It is used to deserialize the type it’s registered on (Original). On deserialization of Original type JSONB calls JsonbDeserializer::deserialize method. This method has to contain a custom code to deserialize Original type using provided JsonpParser. There are two ways how to register JsonbSerializer/JsonbDeserializer:Using JsonbConfig::withSerializers/ JsonbConfig::withDeserializers method;true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-244.7.2Annotating a type with JsonbSerializer/JsonbDeserializer annotation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-344.7.2Implementations must provide a CDI support in serializers/deserializers to allow injection of CDI managed beans into it.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-144.8JsonbDateFormat annotation can be applied to the following targets: field, method, type, parameter, packagetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-244.8Annotation applied to more specific target overrides the same annotation applied to target with wider scope and global configuration. For example, annotation applied to type target will override the same annotation applied to package target.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-344.8Default date format and default locale can be customized globally using jakarta.json.bind.JsonbConfig::withDateFormat and jakarta.json.bind.JsonbConfig::withLocale methods.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.9-144.9JsonbNumberFormat annotation can be applied to the following targets: field, getter/setter, method, type, parameter, packagetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.9-244.9Annotation applied to more specific target overrides the same annotation applied to target with wider scope. For example, annotation applied to type target will override the same annotation applied to package target. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.10-144.10The way to set custom binary data handling strategy is to use jakarta.json.bin.JsonbConfig::withBinaryDataStrategy method.true -
-		falsetechnologyactivetrue
- - diff --git a/install/jsonb/docs/index.html b/install/jsonb/docs/index.html deleted file mode 100644 index 5245fd3f6f..0000000000 --- a/install/jsonb/docs/index.html +++ /dev/null @@ -1,77 +0,0 @@ - - - - - - Welcome to the JSON-B TCK - - - -
-

Welcome to the Jakarta EE JSON Binding TCK, Version 2.0

-

- Your Starting Point

-
-
-

Guide to the Jakarta EE JSON Binding TCK 2.0 Documentation

-

The Jakarta EE JSON Binding (JSON-B) TCK 2.0 documentation includes the - following:

- -

JT Harness Documentation

-

The online version of the JT Harness version 5.0 documentation is - available here.

-
-

-
Copyright 2017, 2021 Oracle and/or its affiliates. All - rights reserved.
- -

- - - diff --git a/install/jsonb/other/testsuite.jtt b/install/jsonb/other/testsuite.jtt deleted file mode 100644 index 0fb21946c0..0000000000 --- a/install/jsonb/other/testsuite.jtt +++ /dev/null @@ -1,23 +0,0 @@ -# -# Copyright (c) 2017, 2018 Oracle and/or its affiliates. All rights reserved. -# -# This program and the accompanying materials are made available under the -# terms of the Eclipse Public License v. 2.0, which is available at -# http://www.eclipse.org/legal/epl-2.0. -# -# This Source Code may also be made available under the following Secondary -# Licenses when the conditions for such availability set forth in the -# Eclipse Public License v. 2.0 are satisfied: GNU General Public License, -# version 2 with the GNU Classpath Exception, which is available at -# https://www.gnu.org/software/classpath/license.html. -# -# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 -# - -# -# $Id$ -# - -name=JSON-B Compatibility Test Suite Version 1.0 -classpath=$TS_HOME/lib/tsharness.jar -testsuite=com.sun.ts.lib.harness.TS diff --git a/install/jsonb/other/vehicle.properties b/install/jsonb/other/vehicle.properties deleted file mode 100644 index 4495a48d00..0000000000 --- a/install/jsonb/other/vehicle.properties +++ /dev/null @@ -1,70 +0,0 @@ -# -# Copyright (c) 2017, 2018 Oracle and/or its affiliates. All rights reserved. -# -# This program and the accompanying materials are made available under the -# terms of the Eclipse Public License v. 2.0, which is available at -# http://www.eclipse.org/legal/epl-2.0. -# -# This Source Code may also be made available under the following Secondary -# Licenses when the conditions for such availability set forth in the -# Eclipse Public License v. 2.0 are satisfied: GNU General Public License, -# version 2 with the GNU Classpath Exception, which is available at -# https://www.gnu.org/software/classpath/license.html. -# -# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 -# - -# -# $Id$ -# - -# A properties file to determine whether a test directory is service test -# directory, and if so the vehicles in which the tests should be run. -# -# An entry key is a test directory relative to the testsutie root (i.e., -# ${TS_HOME}/src) with unix file separator (forward slash). An entry value -# is a list of vehilce names separated by a space. Althoug other reasonable -# delimiters may also work, a single space is recommended for consistency. -# Acceptable vehicle names are combinations of the following strings: -# ejb, servlet, jsp, appclient, and standalone. Each item may only appear -# once in one entry vale. -# -# For examples, some invalid entries: -# /files/ts/src/com/sun/ts/tests/samples/jdbc = ejb jsp servlet appclient -# com\sun\ts\tests\samples\jdbc = ejb jsp servlet appclient -# com\\sun\\ts\\tests\\samples\\jdbc = ejb jsp servlet appclient -# samples/jdbc = ejb jsp servlet appclient -# /com/sun/ts/tests/samples/jdbc = ejb servlet jsp appclient -# com/sun/ts/tests/samples/jdbc = ejb.servlet.jsp.appclient -# com/sun/ts/tests/samples/jdbc = ejb/servlet/jsp/appclient -# -# Entry order is insignificant. As a good practice, make the entry key -# (test directory) specific. For example, -# com/sun/ts/tests = ejb jsp servlet -# conveys to the harness that all tests under com/sun/ts/tests are service -# tests that should be run in 3 vehicles: ejb jsp servlet. -# -# This file may be modified for debugging purpose only. When testing for -# compatibility certification, the original version of this file must be -# used. Do NOT make modifications without maintaining a backup copy. -# - -com/sun/ts/tests/jsonb/api = standalone -com/sun/ts/tests/jsonb/cdi = servlet -com/sun/ts/tests/jsonb/customizedmapping = standalone -com/sun/ts/tests/jsonb/defaultmapping = standalone -com/sun/ts/tests/signaturetest/jsonb = standalone - -# If any test (sub-)directories that have been covered by entries above -# are not service test directories, list them in exclude.dir. It shoule -# arise rarely, and one possible senario could be: -# com/sun/ts/tests/foo is listed above as service tests, but later a -# non-service test dir com/sun/ts/tests/foo/non_service_tests is added, -# and you do not want to list a large number of subdirectories of foo -# in this properties file. -# If you get into this situation often, start questioning the test design -# The syntax: exclude.dir = com/sun/ts/tests/foo/non_service_test com/sun/ -# ts/tests/bar/non_service_test com/sun/ts/tests/buz/non_service_test -# - -exclude.dir = diff --git a/internal/docs/jsonb/JSONB1.0.TCD.txt b/internal/docs/jsonb/JSONB1.0.TCD.txt deleted file mode 100644 index 71c5f184a3..0000000000 --- a/internal/docs/jsonb/JSONB1.0.TCD.txt +++ /dev/null @@ -1,73 +0,0 @@ -TCK Coverage Document for JSR-367 Java API for JSON Binding (JSON-B) 1.0 Specification - - -TCK Components: ---------------- -- User's Guide -- Compatibility Rules -- Configuration Instructions -- Test Suite -- API Tests -- Signature Tests -- Framework Code -- JavaTest TM Harness - - -Terminology of Metrics ----------------------- -- Assertion: A specific statement of functionality or behavior derived from a - specification. A testable assertion is one that can be validated in an - implementation by testing. -- Test: A binary application (or script) comprised of one or more Test Cases. -- Test Case: A single set of test inputs, execution conditions, and expected - results developed to verify an implementation's conformance with a specific - assertion. -- Specification Assertion Coverage: Ratio of all assertions tested by at least - one test case to the total number of testable assertions defined by the - specification. -- API Coverage: Ratio of methods directly exercised by test cases to the total - number of methods defined by the specification. - - --------- -Coverage --------- -******************************************************************************** -Assertion details. These details will be removed from the final TCD but are -checked into revision history so we can backtrack the numbers later, if we need to. - -Assertions found by the coverage tools (May 10th, 2017 coverage report): ------------------------------------------------------------------------ - api testable total : 66 - api tested total : 66 - api percentage tested : 100% - spec testable total : 141 - spec tested total : 138 - spec percentage tested: 97.87% - -Number of tests in JSON-B TCK: 271 - - -Quality Assurance ------------------ -- TCK was run on the following platforms, note all platforms use Java Platform, Standard Edition 8 - (Java SE 8): - * Oracle Linux 7.1 - * Windows 10 - -- Code quality was demonstrated through the use of code reviews and inspections -- User's Guide was constructed from the standard TCK User's Guide template -- Documentation instructions were verified and tested - - -Justification of Adequacy -------------------------- -The JSON-B TCK Version 1.0 provides a comprehensive set of tests to ensure that all -implementations of the Java API for JSON Binding 1.0 Specification are compatible. As -with all TCKs it is impossible to provide tests for 100% assertion coverage. Note, -while the TCK may not have tests for all assertions in the Java API for JSON Binding -1.0 Specification, all implementations must be compatible with the specification. - -Untested assertions are due to the effects of late specification changes, optional -functionality, conditions that cannot be easily tested, and the availability and -cost of test development resources. diff --git a/internal/docs/jsonb/JSONB10JavadocAssertions.html b/internal/docs/jsonb/JSONB10JavadocAssertions.html deleted file mode 100644 index 30813a5b67..0000000000 --- a/internal/docs/jsonb/JSONB10JavadocAssertions.html +++ /dev/null @@ -1,846 +0,0 @@ - - - - - -JavaDoc Assertion Detail - - -
-
-

JSONB 1.0
JSONB 1.0 - 1.0
- JavaDoc Assertion Detail -

-
- - - - - - - - - - - -
TotalsTotalActiveDeprecatedRemoved
- # of Assertions - 808000
- # of Required Assertions - 808000
- # of Optional Assertions - 0000
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IDReturnMethod/FieldDescriptionRequiredDeprecatedTestable
JSONB:JAVADOC:1Objectjavax.json.bind.Jsonb.fromJson
- - ( - String - ,
Class - ) - 		Reads in a JSON data from the specified string and return the resulting content tree.true -
-		true
JSONB:JAVADOC:2Objectjavax.json.bind.Jsonb.fromJson
- - ( - String - ,
Class - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:3Objectjavax.json.bind.Jsonb.fromJson
- - ( - String - ,
Type - ) - 		Reads in a JSON data from the specified string and return the resulting content tree.true -
-		true
JSONB:JAVADOC:4Objectjavax.json.bind.Jsonb.fromJson
- - ( - String - ,
Type - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:5Objectjavax.json.bind.Jsonb.fromJson
- - ( - Reader - ,
Class - ) - 		Reads in a JSON data from the specified Reader and return the resulting content tree.true -
-		true
JSONB:JAVADOC:6Objectjavax.json.bind.Jsonb.fromJson
- - ( - Reader - ,
Class - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:7Objectjavax.json.bind.Jsonb.fromJson
- - ( - Reader - ,
Type - ) - 		Reads in a JSON data from the specified Reader and return the resulting content tree.true -
-		true
JSONB:JAVADOC:8Objectjavax.json.bind.Jsonb.fromJson
- - ( - Reader - ,
Type - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:9Objectjavax.json.bind.Jsonb.fromJson
- - ( - InputStream - ,
Class - ) - 		Reads in a JSON data from the specified InputStream and return the resulting content tree.true -
-		true
JSONB:JAVADOC:10Objectjavax.json.bind.Jsonb.fromJson
- - ( - InputStream - ,
Class - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:11Objectjavax.json.bind.Jsonb.fromJson
- - ( - InputStream - ,
Type - ) - 		Reads in a JSON data from the specified InputStream and return the resulting content tree.true -
-		true
JSONB:JAVADOC:12Objectjavax.json.bind.Jsonb.fromJson
- - ( - InputStream - ,
Type - ) -
throws - JsonbException
-		If any unexpected error(s) occur(s) during deserialization.true -
-		false
JSONB:JAVADOC:13Stringjavax.json.bind.Jsonb.toJson
- - ( - Object - ) - 		Writes the Java object tree with root object object to a String instance as JSON.true -
-		true
JSONB:JAVADOC:14Stringjavax.json.bind.Jsonb.toJson
- - ( - Object - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization, such as I/O error.true -
-		false
JSONB:JAVADOC:15Stringjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ) - 		Writes the Java object tree with root object object to a String instance as JSON.true -
-		true
JSONB:JAVADOC:16Stringjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization, such as I/O error.true -
-		false
JSONB:JAVADOC:17voidjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
Writer - ) - 		Writes the object content tree into a Writer character stream.true -
-		true
JSONB:JAVADOC:18voidjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
Writer - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization.true -
-		false
JSONB:JAVADOC:19voidjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ,
Writer - ) - 		Writes the object content tree into a Writer character stream.true -
-		true
JSONB:JAVADOC:20voidjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ,
Writer - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization.true -
-		false
JSONB:JAVADOC:21voidjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
OutputStream - ) - 		Writes the object content tree into output stream.true -
-		true
JSONB:JAVADOC:22voidjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
OutputStream - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization.true -
-		false
JSONB:JAVADOC:23voidjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ,
OutputStream - ) - 		Writes the object content tree into output stream.true -
-		true
JSONB:JAVADOC:24voidjavax.json.bind.Jsonb.toJson
- - ( - Object - ,
Type - ,
OutputStream - ) -
throws - JsonbException
-		If any unexpected problem occurs during the serialization.true -
-		false
JSONB:JAVADOC:25Jsonbjavax.json.bind.JsonbBuilder.build
-		Returns a new instance of javax.json.bind.Jsonb Jsonb based on the parameters and configuration specified previously in this builder.true -
-		true
JSONB:JAVADOC:26Jsonbjavax.json.bind.JsonbBuilder.create
-		Create a new javax.json.bind.Jsonb instance using the default JsonbBuilder implementation provided as returned from javax.json.bind.spi.JsonbProvider#provider() method.true -
-		true
JSONB:JAVADOC:27Jsonbjavax.json.bind.JsonbBuilder.create
- - ( - JsonbConfig - ) - 		Create a new javax.json.bind.Jsonb instance using the default JsonbBuilder implementation provided as returned from javax.json.bind.spi.JsonbProvider#provider() method, configured with provided configuration.true -
-		true
JSONB:JAVADOC:28JsonbBuilderjavax.json.bind.JsonbBuilder.newBuilder
-		Create a new JsonbBuilder instance as returned by the default javax.json.bind.spi.JsonbProvider#provider() method.true -
-		true
JSONB:JAVADOC:29JsonbBuilderjavax.json.bind.JsonbBuilder.newBuilder
- - ( - String - ) - 		Create a new JsonbBuilder instance as returned by javax.json.bind.spi.JsonbProvider#provider(String) method.true -
-		true
JSONB:JAVADOC:30JsonbBuilderjavax.json.bind.JsonbBuilder.newBuilder
- - ( - JsonbProvider - ) - 		Create a new JsonbBuilder instance as returned by provider#create call.true -
-		true
JSONB:JAVADOC:31JsonbBuilderjavax.json.bind.JsonbBuilder.withConfig
- - ( - JsonbConfig - ) - 		Set configuration which will be set to the newly created javax.json.bind.Jsonb Jsonb instance.true -
-		true
JSONB:JAVADOC:32JsonbBuilderjavax.json.bind.JsonbBuilder.withProvider
- - ( - JsonProvider - ) - 		Provides a JSON-P provider to be used for all JSON-P related operations.true -
-		true
JSONB:JAVADOC:33Mapjavax.json.bind.JsonbConfig.getAsMap
-		Return all configuration properties as an unmodifiable map.true -
-		true
JSONB:JAVADOC:34Optionaljavax.json.bind.JsonbConfig.getProperty
- - ( - String - ) - 		Return value of particular configuration property. The method can only be used to retrieve one of the standard JSON Binding properties defined in this class or a provider specific property. Attempting to get an undefined property will result in an empty Optional value. See Supported Properties.true -
-		true
JSONB:JAVADOC:35JsonbConfigjavax.json.bind.JsonbConfig.JsonbConfig
-		 -
-		true -
-		true
JSONB:JAVADOC:36JsonbConfigjavax.json.bind.JsonbConfig.setProperty
- - ( - String - ,
Object - ) - 		Set the particular configuration property to a new value. The method can only be used to set one of the standard JSON Binding properties defined in this class or a provider specific property.true -
-		true
JSONB:JAVADOC:37JsonbConfigjavax.json.bind.JsonbConfig.withAdapters
- - ( - JsonbAdapter[] - ) - 		Property used to specify custom mapping adapters. Configures value of ADAPTERS property. Calling withAdapters more than once will merge the adapters with previous value.true -
-		true
JSONB:JAVADOC:38JsonbConfigjavax.json.bind.JsonbConfig.withBinaryDataStrategy
- - ( - String - ) - 		Property used to specify custom binary data strategy. Configures value of BINARY_DATA_STRATEGY property.true -
-		true
JSONB:JAVADOC:39JsonbConfigjavax.json.bind.JsonbConfig.withDateFormat
- - ( - String - ,
Locale - ) - 		Property used to specify custom date format. This format will be used by default for all date classes serialization and deserialization.true -
-		true
JSONB:JAVADOC:40JsonbConfigjavax.json.bind.JsonbConfig.withDeserializers
- - ( - JsonbDeserializer[] - ) - 		Property used to specify custom deserializers. Configures value of DESERIALIZERS property. Calling withDeserializers more than once will merge the deserializers with previous value.true -
-		true
JSONB:JAVADOC:41JsonbConfigjavax.json.bind.JsonbConfig.withEncoding
- - ( - String - ) - 		The binding operations will default to this property for encoding of JSON data. For input data (fromJson), selected encoding is used if the encoding cannot be detected automatically. Default value is 'UTF-8'. Configures value of ENCODING property.true -
-		true
JSONB:JAVADOC:42JsonbConfigjavax.json.bind.JsonbConfig.withFormatting
- - ( - Boolean - ) - 		Property used to specify whether or not the serialized JSON data is formatted with linefeeds and indentation. Configures value of FORMATTING property.true -
-		true
JSONB:JAVADOC:43JsonbConfigjavax.json.bind.JsonbConfig.withLocale
- - ( - Locale - ) - 		Property used to specify custom locale.true -
-		true
JSONB:JAVADOC:44JsonbConfigjavax.json.bind.JsonbConfig.withNullValues
- - ( - Boolean - ) - 		Property used to specify whether null values should be serialized to JSON document or skipped. Configures value of NULL_VALUES property.true -
-		true
JSONB:JAVADOC:45JsonbConfigjavax.json.bind.JsonbConfig.withPropertyNamingStrategy
- - ( - PropertyNamingStrategy - ) - 		Property used to specify custom naming strategy. Configures value of JSONB_PROPERTY_NAMING_STRATEGY property.true -
-		true
JSONB:JAVADOC:46JsonbConfigjavax.json.bind.JsonbConfig.withPropertyNamingStrategy
- - ( - String - ) - 		Property used to specify custom naming strategy. Configures value of JSONB_PROPERTY_NAMING_STRATEGY property.true -
-		true
JSONB:JAVADOC:47JsonbConfigjavax.json.bind.JsonbConfig.withPropertyOrderStrategy
- - ( - String - ) - 		Property used to specify property order strategy. Configures values of JSONB_PROPERTY_ORDER_STRATEGY property.true -
-		true
JSONB:JAVADOC:48JsonbConfigjavax.json.bind.JsonbConfig.withPropertyVisibilityStrategy
- - ( - PropertyVisibilityStrategy - ) - 		Property used to specify custom property visibility strategy. Configures value of PROPERTY_VISIBILITY_STRATEGY property.true -
-		true
JSONB:JAVADOC:49JsonbConfigjavax.json.bind.JsonbConfig.withSerializers
- - ( - JsonbSerializer[] - ) - 		Property used to specify custom serializers. Configures value of SERIALIZERS property. Calling withSerializers more than once will merge the serializers with previous value.true -
-		true
JSONB:JAVADOC:50JsonbConfigjavax.json.bind.JsonbConfig.withStrictIJSON
- - ( - Boolean - ) - 		Property used to specify whether strict I-JSON serialization compliance should be enforced. Configures value of STRICT_IJSON property.true -
-		true
JSONB:JAVADOC:51JsonbExceptionjavax.json.bind.JsonbException.JsonbException
- - ( - String - ) - 		Constructs a new runtime exception with the specified detail message. The cause is not initialized, and may subsequently be initialized by a call to #initCause.true -
-		true
JSONB:JAVADOC:52JsonbExceptionjavax.json.bind.JsonbException.JsonbException
- - ( - String - ,
Throwable - ) - 		Constructs a new runtime exception with the specified detail message and cause. Note that the detail message associated with cause is not automatically incorporated in this runtime exception's detail message.true -
-		true
JSONB:JAVADOC:53Objectjavax.json.bind.adapter.JsonbAdapter.adaptFromJson
- - ( - Object - ) - 		This method is used on deserialization only. It contains a conversion logic from type Adapted to type Original.true -
-		true
JSONB:JAVADOC:54Objectjavax.json.bind.adapter.JsonbAdapter.adaptFromJson
- - ( - Object - ) -
throws - Exception
-		if there is an error during the conversion.true -
-		false
JSONB:JAVADOC:55Objectjavax.json.bind.adapter.JsonbAdapter.adaptToJson
- - ( - Object - ) - 		This method is used on serialization only. It contains a conversion logic from type Original to type Adapted. After conversion Adapted type will be mapped to JSON the standard way.true -
-		true
JSONB:JAVADOC:56Objectjavax.json.bind.adapter.JsonbAdapter.adaptToJson
- - ( - Object - ) -
throws - Exception
-		if there is an error during the conversion.true -
-		false
JSONB:JAVADOC:57Stringjavax.json.bind.annotation.JsonbDateFormat.locale
-		Custom java.util.Locale to use.true -
-		true
JSONB:JAVADOC:58Stringjavax.json.bind.annotation.JsonbDateFormat.value
-		Specifies the date pattern to use.true -
-		true
JSONB:JAVADOC:59booleanjavax.json.bind.annotation.JsonbNillable.value
-		True if field with null value should be serialized as key/value pair into JSON with null value.true -
-		true
JSONB:JAVADOC:60Stringjavax.json.bind.annotation.JsonbNumberFormat.locale
-		Custom java.util.Locale to use.true -
-		true
JSONB:JAVADOC:61Stringjavax.json.bind.annotation.JsonbNumberFormat.value
-		Specifies the number pattern to use.true -
-		true
JSONB:JAVADOC:62booleanjavax.json.bind.annotation.JsonbProperty.nillable
-		True if field with null value should be serialized as key/value pair into JSON with null value.true -
-		true
JSONB:JAVADOC:63Stringjavax.json.bind.annotation.JsonbProperty.value
-		Customized name of the field (or JavaBean property).true -
-		true
JSONB:JAVADOC:64String[]javax.json.bind.annotation.JsonbPropertyOrder.value
-		Order in which properties are serialized. Names must correspond to original names defined in Java class before any customization applied.true -
-		true
JSONB:JAVADOC:65Classjavax.json.bind.annotation.JsonbTypeAdapter.value
-		Custom JsonbAdapter which provides custom mapping for given field or JavaBean property.true -
-		true
JSONB:JAVADOC:66Classjavax.json.bind.annotation.JsonbTypeDeserializer.value
-		Custom JsonbDeserializer which provides custom mapping for given field or JavaBean property.true -
-		true
JSONB:JAVADOC:67Classjavax.json.bind.annotation.JsonbTypeSerializer.value
-		Custom JsonbSerializer which provides custom mapping for given field or JavaBean property.true -
-		true
JSONB:JAVADOC:68Classjavax.json.bind.annotation.JsonbVisibility.value
-		Custom property visibility strategy used to resolve visibility of the members.true -
-		true
JSONB:JAVADOC:69Stringjavax.json.bind.config.PropertyNamingStrategy.translateName
- - ( - String - ) - 		Translates the property name into its JSON field name representation.true -
-		true
JSONB:JAVADOC:70booleanjavax.json.bind.config.PropertyVisibilityStrategy.isVisible
- - ( - Field - ) - 		Responds whether the given field should be considered as the JsonbProperty.true -
-		true
JSONB:JAVADOC:71booleanjavax.json.bind.config.PropertyVisibilityStrategy.isVisible
- - ( - Method - ) - 		Responds whether the given method should be considered as the JsonbProperty.true -
-		true
JSONB:JAVADOC:72Objectjavax.json.bind.serializer.DeserializationContext.deserialize
- - ( - Class - ,
JsonParser - ) - 		Deserialize JSON stream into instance of provided class using javax.json.stream.JsonParser. JsonParser cursor have to be at KEY_NAME before START_OBJECT / START_ARRAY, or at START_OBJECT / START_ARRAY to call this method. After deserialization is complete JsonParser will be at END_OBJECT / END_ARRAY for deserialized JSON structure. If method is called for the same type, which is deserializer bound to, deserializer recursion is suppressed. Otherwise deserializers are reentrant during deserialization process started by this method. JsonParser instance of JSONB runtime is shared with custom deserializer.true -
-		true
JSONB:JAVADOC:73Objectjavax.json.bind.serializer.DeserializationContext.deserialize
- - ( - Type - ,
JsonParser - ) - 		Deserialize JSON stream into instance of provided class using javax.json.stream.JsonParser. JsonParser cursor have to be at KEY_NAME before START_OBJECT / START_ARRAY, or at START_OBJECT / START_ARRAY to call this method. After deserialization is complete JsonParser will be at END_OBJECT / END_ARRAY for deserialized JSON structure. If method is called for the same type, which is deserializer bound to, deserializer recursion is suppressed. Otherwise deserializers are reentrant during deserialization process started by this method. JsonParser instance of JSONB runtime is shared with custom deserializer.true -
-		true
JSONB:JAVADOC:74Objectjavax.json.bind.serializer.JsonbDeserializer.deserialize
- - ( - JsonParser - ,
DeserializationContext - ,
Type - ) - 		Deserialize JSON stream into object.true -
-		true
JSONB:JAVADOC:75voidjavax.json.bind.serializer.JsonbSerializer.serialize
- - ( - Object - ,
JsonGenerator - ,
SerializationContext - ) - 		Serializes object into JSON stream.true -
-		true
JSONB:JAVADOC:76voidjavax.json.bind.serializer.SerializationContext.serialize
- - ( - String - ,
Object - ,
JsonGenerator - ) - 		Serializes arbitrary object to JSON, using current javax.json.stream.JsonGenerator instance. Serialization is ran as serialization of a root type from user JsonbSerializer. JsonGenerator instance is shared with JSONB and user serializer.true -
-		true
JSONB:JAVADOC:77voidjavax.json.bind.serializer.SerializationContext.serialize
- - ( - Object - ,
JsonGenerator - ) - 		Serializes arbitrary object to JSON, using current javax.json.stream.JsonGenerator instance. Serialization is ran as serialization of a root type from user JsonbSerializer. JsonGenerator instance is shared with JSONB and user serializer. Method without key parameter is intended to serialize inside JSON_ARRAYs.true -
-		true
JSONB:JAVADOC:78JsonbBuilderjavax.json.bind.spi.JsonbProvider.create
-		Returns a new instance of javax.json.bind.JsonbBuilder JsonbBuilder class. javax.json.bind.JsonbBuilder JsonbBuilder provides necessary getter methods to access required parameters.true -
-		true
JSONB:JAVADOC:80JsonbProviderjavax.json.bind.spi.JsonbProvider.provider
-		Creates a JSON Binding provider object by using the java.util.ServiceLoader#load(Class) method. The first provider of JsonbProvider class from list of providers returned by ServiceLoader.load call is returned. If there are no available service providers, this method tries to load the default service provider using Class#forName(String) method.true -
-		true
JSONB:JAVADOC:81JsonbProviderjavax.json.bind.spi.JsonbProvider.provider
- - ( - String - ) - 		Creates a JSON Binding provider object by using the java.util.ServiceLoader#load(Class) method, matching providerName. The first provider of JsonbProvider class from list of providers returned by ServiceLoader.load call, matching providerName is returned. If no such provider is found, JsonbException is thrown.true -
-		true
- - diff --git a/internal/docs/jsonb/JSONB10JavadocAssertions.xml b/internal/docs/jsonb/JSONB10JavadocAssertions.xml deleted file mode 100644 index 4a29ae6944..0000000000 --- a/internal/docs/jsonb/JSONB10JavadocAssertions.xml +++ /dev/null @@ -1,891 +0,0 @@ - - - - - - 82 - 1 - JSONB - JSONB 1.0 - JSONB 1.0 - 1.0 - - - - - - - 1 - Reads in a JSON data from the specified string and return the resulting content tree. - javax.json.bind - Jsonb - - - java.lang.String - java.lang.Class - - - - - 2 - If any unexpected error(s) occur(s) during deserialization. - javax.json.bind - Jsonb - - - java.lang.String - java.lang.Class - - javax.json.bind.JsonbException - - - - 3 - Reads in a JSON data from the specified string and return the resulting content tree. - javax.json.bind - Jsonb - - - java.lang.String - java.lang.reflect.Type - - - - - 4 - If any unexpected error(s) occur(s) during deserialization. - javax.json.bind - Jsonb - - - java.lang.String - java.lang.reflect.Type - - javax.json.bind.JsonbException - - - - 5 - Reads in a JSON data from the specified Reader and return the resulting content tree. - javax.json.bind - Jsonb - - - java.io.Reader - java.lang.Class - - - - - 6 - If any unexpected error(s) occur(s) during deserialization. - javax.json.bind - Jsonb - - - java.io.Reader - java.lang.Class - - javax.json.bind.JsonbException - - - - 7 - Reads in a JSON data from the specified Reader and return the resulting content tree. - javax.json.bind - Jsonb - - - java.io.Reader - java.lang.reflect.Type - - - - - 8 - If any unexpected error(s) occur(s) during deserialization. - javax.json.bind - Jsonb - - - java.io.Reader - java.lang.reflect.Type - - javax.json.bind.JsonbException - - - - 9 - Reads in a JSON data from the specified InputStream and return the resulting content tree. - javax.json.bind - Jsonb - - - java.io.InputStream - java.lang.Class - - - - - 10 - If any unexpected error(s) occur(s) during deserialization. - javax.json.bind - Jsonb - - - java.io.InputStream - java.lang.Class - - javax.json.bind.JsonbException - - - - 11 - Reads in a JSON data from the specified InputStream and return the resulting content tree. - javax.json.bind - Jsonb - - - java.io.InputStream - java.lang.reflect.Type - - - - - 12 - If any unexpected error(s) occur(s) during deserialization. - javax.json.bind - Jsonb - - - java.io.InputStream - java.lang.reflect.Type - - javax.json.bind.JsonbException - - - - 13 - Writes the Java object tree with root object object to a String instance as JSON. - javax.json.bind - Jsonb - - - java.lang.Object - - - - - 14 - If any unexpected problem occurs during the serialization, such as I/O error. - javax.json.bind - Jsonb - - - java.lang.Object - - javax.json.bind.JsonbException - - - - 15 - Writes the Java object tree with root object object to a String instance as JSON. - javax.json.bind - Jsonb - - - java.lang.Object - java.lang.reflect.Type - - - - - 16 - If any unexpected problem occurs during the serialization, such as I/O error. - javax.json.bind - Jsonb - - - java.lang.Object - java.lang.reflect.Type - - javax.json.bind.JsonbException - - - - 17 - Writes the object content tree into a Writer character stream. - javax.json.bind - Jsonb - - - java.lang.Object - java.io.Writer - - - - - 18 - If any unexpected problem occurs during the serialization. - javax.json.bind - Jsonb - - - java.lang.Object - java.io.Writer - - javax.json.bind.JsonbException - - - - 19 - Writes the object content tree into a Writer character stream. - javax.json.bind - Jsonb - - - java.lang.Object - java.lang.reflect.Type - java.io.Writer - - - - - 20 - If any unexpected problem occurs during the serialization. - javax.json.bind - Jsonb - - - java.lang.Object - java.lang.reflect.Type - java.io.Writer - - javax.json.bind.JsonbException - - - - 21 - Writes the object content tree into output stream. - javax.json.bind - Jsonb - - - java.lang.Object - java.io.OutputStream - - - - - 22 - If any unexpected problem occurs during the serialization. - javax.json.bind - Jsonb - - - java.lang.Object - java.io.OutputStream - - javax.json.bind.JsonbException - - - - 23 - Writes the object content tree into output stream. - javax.json.bind - Jsonb - - - java.lang.Object - java.lang.reflect.Type - java.io.OutputStream - - - - - 24 - If any unexpected problem occurs during the serialization. - javax.json.bind - Jsonb - - - java.lang.Object - java.lang.reflect.Type - java.io.OutputStream - - javax.json.bind.JsonbException - - - - 25 - Returns a new instance of javax.json.bind.Jsonb Jsonb based on the parameters and configuration specified previously in this builder. - javax.json.bind - JsonbBuilder - - - - 26 - Create a new javax.json.bind.Jsonb instance using the default JsonbBuilder implementation provided as returned from javax.json.bind.spi.JsonbProvider#provider() method. - javax.json.bind - JsonbBuilder - - - - 27 - Create a new javax.json.bind.Jsonb instance using the default JsonbBuilder implementation provided as returned from javax.json.bind.spi.JsonbProvider#provider() method, configured with provided configuration. - javax.json.bind - JsonbBuilder - - - javax.json.bind.JsonbConfig - - - - - 28 - Create a new JsonbBuilder instance as returned by the default javax.json.bind.spi.JsonbProvider#provider() method. - javax.json.bind - JsonbBuilder - - - - 29 - Create a new JsonbBuilder instance as returned by javax.json.bind.spi.JsonbProvider#provider(String) method. - javax.json.bind - JsonbBuilder - - - java.lang.String - - - - - 30 - Create a new JsonbBuilder instance as returned by provider#create call. - javax.json.bind - JsonbBuilder - - - javax.json.bind.spi.JsonbProvider - - - - - 31 - Set configuration which will be set to the newly created javax.json.bind.Jsonb Jsonb instance. - javax.json.bind - JsonbBuilder - - - javax.json.bind.JsonbConfig - - - - - 32 - Provides a JSON-P provider to be used for all JSON-P related operations. - javax.json.bind - JsonbBuilder - - - JsonProvider - - - - - 33 - Return all configuration properties as an unmodifiable map. - javax.json.bind - JsonbConfig - - - - 34 - Return value of particular configuration property. The method can only be used to retrieve one of the standard JSON Binding properties defined in this class or a provider specific property. Attempting to get an undefined property will result in an empty Optional value. See Supported Properties. - javax.json.bind - JsonbConfig - - - java.lang.String - - - - - 35 - - javax.json.bind - JsonbConfig - - - - 36 - Set the particular configuration property to a new value. The method can only be used to set one of the standard JSON Binding properties defined in this class or a provider specific property. - javax.json.bind - JsonbConfig - - - java.lang.String - java.lang.Object - - - - - 37 - Property used to specify custom mapping adapters. Configures value of ADAPTERS property. Calling withAdapters more than once will merge the adapters with previous value. - javax.json.bind - JsonbConfig - - - javax.json.bind.adapter.JsonbAdapter[] - - - - - 38 - Property used to specify custom binary data strategy. Configures value of BINARY_DATA_STRATEGY property. - javax.json.bind - JsonbConfig - - - java.lang.String - - - - - 39 - Property used to specify custom date format. This format will be used by default for all date classes serialization and deserialization. - javax.json.bind - JsonbConfig - - - java.lang.String - java.util.Locale - - - - - 40 - Property used to specify custom deserializers. Configures value of DESERIALIZERS property. Calling withDeserializers more than once will merge the deserializers with previous value. - javax.json.bind - JsonbConfig - - - javax.json.bind.serializer.JsonbDeserializer[] - - - - - 41 - The binding operations will default to this property for encoding of JSON data. For input data (fromJson), selected encoding is used if the encoding cannot be detected automatically. Default value is 'UTF-8'. Configures value of ENCODING property. - javax.json.bind - JsonbConfig - - - java.lang.String - - - - - 42 - Property used to specify whether or not the serialized JSON data is formatted with linefeeds and indentation. Configures value of FORMATTING property. - javax.json.bind - JsonbConfig - - - java.lang.Boolean - - - - - 43 - Property used to specify custom locale. - javax.json.bind - JsonbConfig - - - java.util.Locale - - - - - 44 - Property used to specify whether null values should be serialized to JSON document or skipped. Configures value of NULL_VALUES property. - javax.json.bind - JsonbConfig - - - java.lang.Boolean - - - - - 45 - Property used to specify custom naming strategy. Configures value of JSONB_PROPERTY_NAMING_STRATEGY property. - javax.json.bind - JsonbConfig - - - javax.json.bind.config.PropertyNamingStrategy - - - - - 46 - Property used to specify custom naming strategy. Configures value of JSONB_PROPERTY_NAMING_STRATEGY property. - javax.json.bind - JsonbConfig - - - java.lang.String - - - - - 47 - Property used to specify property order strategy. Configures values of JSONB_PROPERTY_ORDER_STRATEGY property. - javax.json.bind - JsonbConfig - - - java.lang.String - - - - - 48 - Property used to specify custom property visibility strategy. Configures value of PROPERTY_VISIBILITY_STRATEGY property. - javax.json.bind - JsonbConfig - - - javax.json.bind.config.PropertyVisibilityStrategy - - - - - 49 - Property used to specify custom serializers. Configures value of SERIALIZERS property. Calling withSerializers more than once will merge the serializers with previous value. - javax.json.bind - JsonbConfig - - - javax.json.bind.serializer.JsonbSerializer[] - - - - - 50 - Property used to specify whether strict I-JSON serialization compliance should be enforced. Configures value of STRICT_IJSON property. - javax.json.bind - JsonbConfig - - - java.lang.Boolean - - - - - 51 - Constructs a new runtime exception with the specified detail message. The cause is not initialized, and may subsequently be initialized by a call to #initCause. - javax.json.bind - JsonbException - - - java.lang.String - - - - - 52 - Constructs a new runtime exception with the specified detail message and cause. Note that the detail message associated with cause is not automatically incorporated in this runtime exception's detail message. - javax.json.bind - JsonbException - - - java.lang.String - java.lang.Throwable - - - - - 53 - This method is used on deserialization only. It contains a conversion logic from type Adapted to type Original. - javax.json.bind.adapter - JsonbAdapter - - - java.lang.Object - - - - - 54 - if there is an error during the conversion. - javax.json.bind.adapter - JsonbAdapter - - - java.lang.Object - - java.lang.Exception - - - - 55 - This method is used on serialization only. It contains a conversion logic from type Original to type Adapted. After conversion Adapted type will be mapped to JSON the standard way. - javax.json.bind.adapter - JsonbAdapter - - - java.lang.Object - - - - - 56 - if there is an error during the conversion. - javax.json.bind.adapter - JsonbAdapter - - - java.lang.Object - - java.lang.Exception - - - - 57 - Custom java.util.Locale to use. - javax.json.bind.annotation - JsonbDateFormat - - - - 58 - Specifies the date pattern to use. - javax.json.bind.annotation - JsonbDateFormat - - - - 59 - True if field with null value should be serialized as key/value pair into JSON with null value. - javax.json.bind.annotation - JsonbNillable - - - - 60 - Custom java.util.Locale to use. - javax.json.bind.annotation - JsonbNumberFormat - - - - 61 - Specifies the number pattern to use. - javax.json.bind.annotation - JsonbNumberFormat - - - - 62 - True if field with null value should be serialized as key/value pair into JSON with null value. - javax.json.bind.annotation - JsonbProperty - - - - 63 - Customized name of the field (or JavaBean property). - javax.json.bind.annotation - JsonbProperty - - - - 64 - Order in which properties are serialized. Names must correspond to original names defined in Java class before any customization applied. - javax.json.bind.annotation - JsonbPropertyOrder - - - - 65 - Custom JsonbAdapter which provides custom mapping for given field or JavaBean property. - javax.json.bind.annotation - JsonbTypeAdapter - - - - 66 - Custom JsonbDeserializer which provides custom mapping for given field or JavaBean property. - javax.json.bind.annotation - JsonbTypeDeserializer - - - - 67 - Custom JsonbSerializer which provides custom mapping for given field or JavaBean property. - javax.json.bind.annotation - JsonbTypeSerializer - - - - 68 - Custom property visibility strategy used to resolve visibility of the members. - javax.json.bind.annotation - JsonbVisibility - - - - 69 - Translates the property name into its JSON field name representation. - javax.json.bind.config - PropertyNamingStrategy - - - java.lang.String - - - - - 70 - Responds whether the given field should be considered as the JsonbProperty. - javax.json.bind.config - PropertyVisibilityStrategy - - - java.lang.reflect.Field - - - - - 71 - Responds whether the given method should be considered as the JsonbProperty. - javax.json.bind.config - PropertyVisibilityStrategy - - - java.lang.reflect.Method - - - - - 72 - Deserialize JSON stream into instance of provided class using javax.json.stream.JsonParser. JsonParser cursor have to be at KEY_NAME before START_OBJECT / START_ARRAY, or at START_OBJECT / START_ARRAY to call this method. After deserialization is complete JsonParser will be at END_OBJECT / END_ARRAY for deserialized JSON structure. If method is called for the same type, which is deserializer bound to, deserializer recursion is suppressed. Otherwise deserializers are reentrant during deserialization process started by this method. JsonParser instance of JSONB runtime is shared with custom deserializer. - javax.json.bind.serializer - DeserializationContext - - - java.lang.Class - JsonParser - - - - - 73 - Deserialize JSON stream into instance of provided class using javax.json.stream.JsonParser. JsonParser cursor have to be at KEY_NAME before START_OBJECT / START_ARRAY, or at START_OBJECT / START_ARRAY to call this method. After deserialization is complete JsonParser will be at END_OBJECT / END_ARRAY for deserialized JSON structure. If method is called for the same type, which is deserializer bound to, deserializer recursion is suppressed. Otherwise deserializers are reentrant during deserialization process started by this method. JsonParser instance of JSONB runtime is shared with custom deserializer. - javax.json.bind.serializer - DeserializationContext - - - java.lang.reflect.Type - JsonParser - - - - - 74 - Deserialize JSON stream into object. - javax.json.bind.serializer - JsonbDeserializer - - - JsonParser - javax.json.bind.serializer.DeserializationContext - java.lang.reflect.Type - - - - - 75 - Serializes object into JSON stream. - javax.json.bind.serializer - JsonbSerializer - - - java.lang.Object - JsonGenerator - javax.json.bind.serializer.SerializationContext - - - - - 76 - Serializes arbitrary object to JSON, using current javax.json.stream.JsonGenerator instance. Serialization is ran as serialization of a root type from user JsonbSerializer. JsonGenerator instance is shared with JSONB and user serializer. - javax.json.bind.serializer - SerializationContext - - - java.lang.String - java.lang.Object - JsonGenerator - - - - - 77 - Serializes arbitrary object to JSON, using current javax.json.stream.JsonGenerator instance. Serialization is ran as serialization of a root type from user JsonbSerializer. JsonGenerator instance is shared with JSONB and user serializer. Method without key parameter is intended to serialize inside JSON_ARRAYs. - javax.json.bind.serializer - SerializationContext - - - java.lang.Object - JsonGenerator - - - - - 78 - Returns a new instance of javax.json.bind.JsonbBuilder JsonbBuilder class. javax.json.bind.JsonbBuilder JsonbBuilder provides necessary getter methods to access required parameters. - javax.json.bind.spi - JsonbProvider - - - - 80 - Creates a JSON Binding provider object by using the java.util.ServiceLoader#load(Class) method. The first provider of JsonbProvider class from list of providers returned by ServiceLoader.load call is returned. If there are no available service providers, this method tries to load the default service provider using Class#forName(String) method. - javax.json.bind.spi - JsonbProvider - - - - 81 - Creates a JSON Binding provider object by using the java.util.ServiceLoader#load(Class) method, matching providerName. The first provider of JsonbProvider class from list of providers returned by ServiceLoader.load call, matching providerName is returned. If no such provider is found, JsonbException is thrown. - javax.json.bind.spi - JsonbProvider - - - java.lang.String - - - - - - diff --git a/internal/docs/jsonb/Jsonb10SpecAssertions.html b/internal/docs/jsonb/Jsonb10SpecAssertions.html deleted file mode 100644 index 6acddf3b56..0000000000 --- a/internal/docs/jsonb/Jsonb10SpecAssertions.html +++ /dev/null @@ -1,910 +0,0 @@ - - - - - -Specification Assertion Detail - - -
-
-

Java API for JSON Binding
JSONB - 1.0
- Specification Assertion Detail -

-
- - - - - - - - - - - -
TotalsTotalActiveDeprecatedRemoved
- # of Assertions - 15215101
- # of Required Assertions - 14514401
- # of Optional Assertions - 7700
-
Assertions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IDChapterSectionDescriptionRequiredDependencyImplementation SpecificDefined byStatusTestable
JSONB:SPEC:JSB-3.1-133.1JSON Binding implementations MUST support binding of JSON documents as defined in RFC 7159 JSON Grammar. Serialized JSON output MUST conform to the RFC 7159 JSON Grammar and be encoded in UTF-8 encoding as defined in Section 8.1 (Character Encoding) of RFC 7159 - true -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-233.1Implementations MUST support deserialization of documents conforming to RFC 7159 JSON Grammartrue -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-333.1In addition, implementations SHOULD NOT allow deserialization of RFC 7159 non-conforming text (e.g. unsupported encoding, ...) and report error in such casefalse -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-433.1Detection of UTF encoding of deserialized document is done as defined in the Section 3 (Encoding) of RFC 4627true -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-533.1Implementations SHOULD ignore presence of UTF byte order mark (BOM) and not treat it as an error.false -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.2-133.2Implementations SHOULD NOT allow unmarshalling of RFC 7159 non-conforming text (e.g. unsupported encoding) and report error in such case.false -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.2-233.2Implementation SHOULD also report error also during unmarshalling operation, if it is not possible to represent JSON document value in the expected Java typefalse -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.3-133.3Implementation MUST report binding of the following basic java classes and their corresponding primitive types -java.lang.String -java.lang.Character -java.lang.Byte -java.lang.Short -java.lang.Integer -java.lang.Long -java.lang.Float -java.lang.Double -java.lang.Booleantrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.1-133.3.1Instances of type java.lang.String and java.lang.Character are marshalled to JSON String values as defined within RFC 7159 Section 7 (Strings) in UTF-8 encoding without byte order mark. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.1-233.3.2Implementations SHOULD support deserialization of JSON text in other (than UTF-8) UTF encodings into java.lang.String instancesfalse -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.2-133.3.2Serialization of type java.lang.Byte, Short, Integer, Long, Float, Double and their corresponding primitive types to JSON Number MUST follow the conversion process defined in javadoc specification for the corresponding toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.2-233.3.2Deserialization of a JSON value into java.lang.Byte, Short, Integer, Long, Float, Double instance or corresponding primitive type MUST follow the conversion process as defined in the specification for their corresponding parse$Type method, such as java.lang.Byte.parseByte for Byte.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.3-133.3.3Serialization of type java.lang.Boolean and its corresponding boolean primitive type to JSON value MUST follow conversion process defined in specification for java.lang.Boolean.toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.3-233.3.3Deserialization of a JSON value into java.lang.Boolean instance or boolean primitive type MUST follow the conversion process as defined in specification for java.lang.Boolean.parseBoolean method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.4-133.3.4Serialization of type java.lang.Number (if their more concrete type is not defined elsewhere in this chapter) to JSON string MUST retrieve double value returned from java.lang.Number.doubleValue() method and converting the value to JSON Number as defined in subsection 3.3.2true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.4-233.3.4Deserialization of a JSON value into Java type java.lang.Number should return instance of java.math.BigDecimal by using conversion as defined in the specification for constructor of java.math.BigDecimal with java.lang.String.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4-133.4Implementations MUST support binding of the following standard Java SE classes: -java.math.BigInteger -java.math.BigDecimal -java.net.URL -java.net.URI -java.util.Optional -java.util.OptionalInt -java.util.OptionalLong -java.util.OptionalDouble true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.1-133.4.1Serialization of type java.math.BigInteger, BigDecimal to s JSON Number MUST follow the conversion process defined in specification for their toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.1-233.4.2Deserialization of JSON value into java.math.BigInteger, BigDecimal instance MUST follow the conversion process as defined in the specification for constructor of java.math.BigInteger, BigDecimal with java.lang.String.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.2-133.4.2Serialization of type java.net.URL, URI to a JSON String value MUST follow the conversion process defined in specification for their toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.2-233.4.2Deserialization of a JSON value into java.net.URL, URI instance MUST follow the conversion process as defined in the specification for constructor of java.net.URL, URI with java.lang.String input.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-133.4.3Non-empty instances of type java.util.Optional, OptionalInt, OptionalLong, OptionalDouble are serialized to a JSON value by retrieving their contained instance and converting it to JSON value based on its type and corresponding mapping definitions within this chapter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-233.4.3Class fields containing empty optional instances are treated as having a null value and serialized based on 3.14.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-333.4.3Empty optional instances in array items are serialized as null.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-433.4.3Deserializing into Optional, OptionalInt, OptionalLong, OptionalDouble return empty optional value for properties containing a null value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-533.4.3Otherwise any non-empty Optional, OptionalInt, OptionalLong, OptionalDouble value is constructed of type unmarshalled based on mappings defined in this chapter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-633.4.3Instances of type java.util.Optional T are serialized to a JSON value as JSON objects when T alone would be serialized as JSON object. When T would be serialized as a JSON value (e.g. java.lang.String, java.lang.Integer), an instance of java.util.Optional T is serialized as a JSON value (without curly brackets).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-733.4.3Deserialization of a JSON value into java.util.Optional(T) MUST be supported if deserialization of a JSON value into instance of T is supported.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-133.5Implementations MUST support binding of the following standard Java date/time classes: java.util.Date -java.util.Calendar -java.util.GregorianCalendar -java.util.TimeZone -java.util.SimpleTimeZone -java.time.Instant -java.time.Duration -java.time.Period -java.time.LocalDate -java.time.LocalTime -java.time.LocalDateTime -java.time.ZonedDateTime -java.time.ZoneId -java.time.ZoneOffset -java.time.OffsetDateTime -java.time.OffsetTimetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-233.5If not specified otherwise in this section, GMT standard time zone and offset specified from UTC Greenwich is used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-333.5If not specified otherwise, date time format for marshalling and unmarshalling is ISO 8601 without offset, as specified in java.time.format.DateTimeFormatter.ISO_DATE.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-433.5Implementations MUST report error if the date/time string in JSON document does not correspond to the expected datetime format. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-533.5If in strict I-JSON compliance mode, default date format is changed as it’s described in 4.4.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-133.5.1The serialization format of java.util.Date, Calendar, GregorianCalendar instances with no time information is ISO_DATE.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-233.5.1If time information is present, the format is ISO_DATE_TIMEtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-333.5.1Implementations MUST support deserialization of both ISO_DATE and ISO_DATE_TIME into java.util.Date, Calendar and GregorianCalendar instances.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-133.5.2Implementations MUST support deserialization of any time zone format specified in java.util.TimeZone into a field or property of type java.util.TimeZone and SimpleTimeZone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-233.5.2Implementations MUST report an error for deprecated three-letter time zone IDs as specified in java.util.Timezone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-333.5.2The serialization format of java.util.TimeZone and SimpleTimeZone is NormalizedCustomID as specified in java.util.TimeZone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-133.5.3The serialization output for a java.time.Instant instance MUST be in a ISO_INSTANT format, as specified in java.time.format.DateTimeFormatter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-233.5.3Implementations MUST support the deserialization of an ISO_INSTANT formatted JSON string to a java.time.Instant instance.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-333.5.3Analogically, for other java.time.* classes, following mapping table matches Java types and corresponding formats: -java.time.Instant ISO_INSTANT -java.time.LocalDate ISO_LOCAL_DATE -java.time.LocalTime ISO_LOCAL_TIME -java.time.LocalDateTime ISO_LOCAL_DATE_TIME -java.time.ZonedDateTime ISO_ZONED_DATE_TIME -java.time.OffsetDateTime ISO_OFFSET_DATE_TIME -java.time.OffsetTime ISO_OFFSET_TIMEtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-433.5.3Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneId into a field or property of type java.time.ZoneId.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-533.5.3The serialization format of java.time.ZoneId is the normalized zone ID as specified in java.time.ZoneId.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-633.5.3Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneOffset into a field or property of type java.time.ZoneOffset.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-733.5.3The serialization format of java.time.ZoneOffset is the normalized zone ID as specified in java.time.ZoneOffset.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-833.5.3Implementations MUST support the deserialization of any duration format specified in java.time.Duration into a field or property of type java.time.Duration.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-933.5.3This is super-set of ISO 8601 duration format. The serialization format of java.time.Duration is the ISO 8601 seconds based representation, such as PT8H6M12.345S.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1033.5.3Implementations MUST support the deserialization of any period format specified in java.time.Period into a field or property of type java.time.Period.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1133.5.3This is a super-set of ISO 8601 period format. The serialization format of java.time.Period is ISO 8601 period representation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1233.5.3A zero-length period is represented as zero days 'P0D'.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.6-133.6For an unspecified output type of a deserialization operation, as well as where output type is specified as Object.class, implementations MUST deserialize a JSON document using Java runtime types specified in table below: -object java.util.Map String,Object -array java.util.List Object -string java.lang.String -number java.math.BigDecimal -true, false java.lang.Boolean -null null -true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.6-233.6JSON object values are deserialized into an implementation of java.util.Map(String, Object) with a predictable iteration order.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7-133.7Any instance passed to a deserialization operation must have a public or protected no-argument constructor. Implementations SHOULD throw an error if this condition is not met.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7-233.7This limitation does not apply to serialization operations, as well as to classes which specify explicit instantiation methods as described in section 4.5.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-133.7.1For a deserialization operation of a Java property, if a matching public setter method exists, the method is called to set the value of the property. If a matching setter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching setter method exists and the field is public, then direct field assignment is used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-233.7.1For a serialization operation, if a matching public getter method exists, the method is called to obtain the value of the property. If a matching getter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching getter method exists and the field is public, then the value is obtained directly from the field.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-333.7.1JSON Binding implementations MUST NOT deserialize into transient, final or static fields and MUST ignore name/value pairs corresponding to such fields.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-433.7.1Implementations MUST support serialization of final fields.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-533.7.1Transient and static fields MUST be ignored during serialization operation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-633.7.1If a JSON document contains a name/value pair not corresponding to field or setter method, then this name/value pair MUST be ignored.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-733.7.1Public getter/setter methods without a corresponding field MUST be supported. When only public getter/setter method without corresponding field is present in the class, the getter method is called to obtain the value to serialize, and the setter method is called during deserialization operation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.2-133.7.2Implementations MUST support the binding of public and protected nested classes.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.2-233.7.2For deserialization operations, both nested and encapsulating classes MUST fulfill the same instantiation requirements as specified in 3.7.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.3-133.7.3Implementations MUST support the binding of public and protected static nested classes.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.3-233.7.3For deserialization operations, the nested class MUST fulfill the same instantiation requirements as specified in 3.7.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.4-133.7.4Deserialization into anonymous classes is not supported. Serialization of anonymous classes is supported by default object mapping.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.8-133.8Deserialization into polymorphic types is not supported by default mapping.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.9-133.9Serialization of an Enum instance to a JSON String value MUST follow the conversion process defined in javadoc specification for their name().true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.9-233.9Deserialization of a JSON value into an enum instance MUST be done by calling the enum’s valueOf(String) method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-133.10Implementations MUST support the deserialization of specific interfaces defined in 3.11 and 3.3.4.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-233.10Deserialization to other interfaces is not supported and implementations SHOULD report error in such case.false -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-333.10If a class property is defined with an interface and not concrete type, then the mapping for a serialized property is resolved based on its runtime type.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.11-133.11Implementations MUST support binding of the following collection interfaces, classes and their implementations. -java.util.Collection -java.util.Map -java.util.Set -java.util.HashSet -java.util.NavigableSet -java.util.SortedSet -java.util.TreeSet -java.util.LinkedHashSet -java.util.TreeHashSet -java.util.HashMap -java.util.NavigableMap -java.util.SortedMap -java.util.TreeMap -java.util.LinkedHashMap -java.util.TreeHashMap -java.util.List -java.util.ArrayList -java.util.LinkedList -java.util.Deque -java.util.ArrayDeque -java.util.Queue -java.util.PriorityQueue -java.util.EnumSet -java.util.EnumMap - -true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.11-233.11Implementations of interfaces below must provide accessible default constructor. JSON Binding implementations MUST report unmarshalling error if default constructor is not present or is not in accessible scope.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.12-133.12JSON Binding implementations MUST support binding of Java arrays of all supported Java types from this chapter into/from JSON array structures as defined in Section 5 of RFC 7159true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.12-233.12Arrays of primitive types and multi-dimensional arrays MUST be supported.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.13-133.13Declared fields MUST be serialized in lexicographical order into the resulting JSON document. In case of inheritance, declared fields of super class MUST be serialized before declared fields of child class.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.13-233.13When deserializing a JSON document, declared fields MUST be set in the order of attributes present in the JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-133.14.1The result of serializing a java field with a null value is the absence of the property in the resulting JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-233.14.1The deserialization operation of a property absent in JSON document MUST not set the value of the field, the setter (if available) MUST not be called, and thus original value of the field MUST be preserved.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-333.14.1The deserialization operation of a property with a null value in a JSON document MUST set the value of the field to null value (or call setter with null value if setter is present). The exception is java.util.Optional, OptionalInt, OptionalLong, OptionalDouble instances. In this case the value of the field is set to an empty optional value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-133.14.2The result of deserialization n-ary array represented in JSON document is n-ary Java array.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-233.14.2Null value in JSON array is represented by null value in Java array.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-333.14.2Serialization operation on Java array with null value at index i MUST output null value at index i of the array in resulting JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-133.15According to RFC 7159 Section 7 , every Java identifier name can be transformed using identity function into a valid JSON String. Identity function MUST be used for transforming Java identifier names into name Strings in JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-233.15For deserialization operations defined in 3.6 section, identity function is used to transform JSON name strings into Java String instances in the resulting map Map(String, Object).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-333.15Identity function is used also for other deseralization operations.true -
-		falsetechnologyremovedtrue
JSONB:SPEC:JSB-3.15-433.15If a Java identifier with corresponding name does not exist or is not accessible, the implementations MUST report error.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.16-133.16JSON Binding implementation MUST serialize numbers that express greater magnitude or precision than an IEEE 754 double precision number as strings.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-133.17JSON Binding implementations MUST support binding of generic types.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-233.17Due to type erasure, there are situations when it is not possible to obtain generic type information. There are two ways for JSON Binding implementations to obtain generic type information. If there is a class file available (in the following text referred as static type information), it is possible to obtain generic type information (effectively generic type declaration) from Signature attribute (if this information is present).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-333.17The second option is to provide generic type information at runtime. To provide generic type information at runtime, an argument of java.lang.reflect.Type MUST be passed to Jsonb::toJson or to Jsonb::fromJson method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-133.17.1There are several levels of information JSON Binding implementations may obtain about the type of field/class/interface: - 1. runtime type provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method - 2. static type provided in class file (effectively stored in Signature attribute) - 3. raw type - 4. no information about the typetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-233.17.1If there is no information about the type, JSON Binding implementation MUST treat this type as java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-333.17.1If only raw type of given field/class/interface is known, then the type MUST be treated like raw type.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-433.17.1For example, if the only available information is that given field/class/interface is of type java.util.ArrayList, than the type MUST be treated as java.util.ArrayList Object. JSON Binding implementations MUST use the most specific type derived from the information available.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-533.17.1Let's consider situation where there is only static type information of a given field/class/interface known, -and there is no runtime type information available. Let GenericClass T1; : : : ; Tn be part of generic type -declaration, where GenericClass is name of the generic type and T1; : : : ; Tn are type parameters. For every -Ti, where i in 1; : : : ; n, there are 3 possible options:true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-633.17.11. Ti is concrete parameter type -2. Ti is bounded parameter type -3. Ti is wildcard parameter type without bounds -In case 1, the most specific parameter type MUST be given concrete parameter type Ti.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-733.17.1For bounded parameter type, using bounds B1; : : : ;Bm. If m = 1, then the most specific parameter type MUST be derived from the given bound B1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-833.17.1If B1 is class or interface, the most specific parameter type MUST be the class or interface.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-933.17.1Otherwise, the most specific parameter type SHOULD be java.lang.Object.false -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1033.17.1If multiple bounds are specified, the first step is to resolve every bound separately. Let’s define result of such resolution as S1; : : : ; Sm specific parameter types. If S1; : : : ; Sm are java.lang.Object, then the bounded parameter type Ti MUST be java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1133.17.1If there is exactly one Sk, where 1 <= k <= m is different than java.lang.Object, then the most specific parameter type for this bounded parameter type Ti MUST be Sk.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1233.17.1If there exists Sk1; Sk2, where 1 <= k1 <= k2 <= m, then the most specific parameter type is Sk1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1333.17.1For wildcard parameter type without bounds, the most specific parameter type MUST be java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1433.17.1Any unresolved type parameter MUST be treated as java.lang.Object. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1533.17.1If runtime type is provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method, than that runtime type overrides static type declaration wherever applicabletrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.18-133.18When JSON Binding implementation encounters key in key/value pair that it does not recognize, it should treat the rest of the JSON document as if the element simply did not appear, and in particular, the implementation MUST NOT treat this as an error condition.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.19-133.19JSON Binding implementations MUST NOT produce JSON documents with members with duplicate names. In this context, "duplicate" means that the names, after processing any escaped characters, are identical sequences of Unicode characters.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.19-233.19When non-unique property (after override and rename) is found, implementation MUST throw an exception. This doesn't apply for customized user serialization behavior implemented with the usage of JsonbAdapter mechanism.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-133.20JSON Binding implementations MUST support binding of the following JSON Processing types. - -javax.json.JsonObject -javax.json.JsonArray -javax.json.JsonStructure -javax.json.JsonValue -javax.json.JsonPointer -javax.json.JsonString -javax.json.JsonNumber - true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-233.20Marshalling of supported javax.json.* objects/interfaces/fields MUST have the same result as marshalling these objects with javax.json.JsonWriter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-333.20Deserialization into supported javax.json.* objects/interfaces/fields MUST have the same result as unmarshalling into such objects with javax.json.JsonReader.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-144.1.1JSON Binding implementations MUST NOT serialize fields, JavaBean properties or types annotated with javax.json.bind.annotation.JsonbTransient.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-244.1.1JsonbTransient annotation is mutually exclusive with all other JSON Binding defined annotations. Implementations must throw JsonbException in the following cases: Class field is annotated with @JsonbTransient. Exception must be thrown when this field, getter or setter is annotated with other JSON Binding annotations.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-344.1.1Getter is annotated with @JsonbTransient. Exception is thrown if when the field or this getter are annotated with other JSON Binding annotations. Exception is not thrown if JSON Binding annotations are presented on the setter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-444.1.1Setter is annotated with @JsonbTransient. Exception is thrown if when the field or this setter are annotated with other JSON Binding annotations. Exception is not thrown if JSON Binding annotations are presented on the getter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-144.1.2To provide custom name for given field (or JavaBean property), -javax.json.bind.annotation.JsonbProperty may be used. JsonbProperty annotation may be specified on -field, getter or setter method. If specified on field, custom name is used both for serialization and -deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-244.1.2If javax.json.bind.annotation.JsonbProperty is specified on getter method, it is used -only for serialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-344.1.2If javax.json.bind.annotation.JsonbProperty is specified on setter method, it is used only for deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-444.1.2It is possible to specify different values for getter and setter method for javax.json.bind.annotation.JsonbProperty annotation. In such case the different custom name will be used for serialization and deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.3-144.1.3The way to set custom property naming strategy is to use javax.json.bin.JsonbConfig::withPropertyNamingStrategy method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.4-144.1.4If duplicate name is found exception MUST be thrown. The definition of duplicate (non-unique) property -can be found in 3.19.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.244.2The way to set custom property order strategy is to use javax.json.bin.JsonbConfig::withPropertyOrderStrategy method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.2-244.2To customize the order of serialized properties only for one specific type, JSON Binding provides javax.json.bind.annotation.JsonbPropertyOrder annotation. Order specified by JsonbPropertyOrder annotation overrides order specified by PropertyOrderStrategy.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3-144.3.1If annotations (JsonbNillable or JsonbProperty) on different level apply to the same field (or JavaBean property) or if there is config wide configuration and some annotation (JsonbNillable or JsonbProperty) which apply to the same field (or JavaBean property), the annotation with the smallest scope applies.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-144.3.1When given object (type or package) is annotated with javax.json.bind.annotation.JsonbNillable annotation, the result of null value will be presence of associated property in JSON document with explicit null value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-244.3.1The same behavior as JsonbNillable, but only at field, parameter and method (JavaBean property) level is provided by javax.json.bind.annotation.JsonbProperty annotation with its nillable parametertrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-344.3.1JSON Binding implementations MUST implement override of annotations according to target of the annotation (FIELD, PARAMETER, METHOD, TYPE, PACKAGE). Type level annotation overrides behavior set at the package level. Method, parameter or field level annotation overrides behavior set at the type level.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.2-144.3.2The way to enforce serialization of null values, is to call method javax.json.bind.JsonbConfig::withNullValues with parameter true. The way to skip serialization of null values is to call method javax.json.bind.JsonbConfig::withNullValues with parameter false.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4-144.4To enforce strict compliance of serialized JSON documents, JSON Binding implementations MUST implement configuration option jsonb.i-json.strict-ser-compliance.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-144.4.1Uppercase rather than lowercase letters MUST be used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-244.4.1The timezone MUST always be included and optional trailing seconds MUST be included even when their value is 00.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-344.4.1JSON Binding implementations MUST serialize java.util.Date, java.util.Calendar, java.util.GregorianCalendar, java.time.LocalDate, java.time.LocalDateTime and java.time.Instant in the same format as java.time.ZonedDateTime.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-444.4.1The result of serialization of duration must conform to the duration production in Appendix A of RFC 3339, with the same additional restrictionstrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-144.5At most one JsonbCreator annotation can be used to annotate custom constructor or static void factory method in a class, otherwise JsonbException MUST be thrown.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-244.5Factory method annotated with JsonbCreator annotation should return instance of particular class this annotation is used for, otherwise JsonbException MUST be thrown.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-344.5Mapping between parameters of constructor/factory method annotated with JsonbCreator and JSON fields is defined using JsonbProperty annotation on all parameters.In case JsonbProperty annotation on parameters is not used, parameters should be mapped from JSON fields with the same name. In this case the proper mapping is NOT guaranteed.In case a field required for a parameter mapping doesn’t exist in JSON document, JsonbException MUST be thrown.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.6-144.5To customize scope and field access strategy as specified in section 3.7.1, it is possible to specify javax.json.bind.annotation.JsonbVisibility annotation or to override default behavior globally calling JsonbConfig::withPropertyVisibilityStrategy method with given custom property visibility strategy.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-144.7.1On serialization of Original type JSONB calls JsonbAdapter::adaptToJson method of the adapter to convert Original to Adapted and serializes Adapted the standard way. There are two ways how to register JsonbAdapter: Using JsonbConfig::withAdapters method;true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-244.7.1Annotating a class field with JsonbTypeAdapter annotation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-344.7.1Implementations must provide a CDI support in adapters to allow injection of CDI managed beans into it.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-144.7.2Serializer is a class implementing javax.json.bind.serializers.JsonbSerializer interface. It is used to serialize the type it's registered on (Original). On marshalling of Original type JSONB calls JsonbSerializer::serialize method. This method has to contain a custom code to serialize Original type using provided JsonpGenerator.Deserializer is a class implementing javax.json.bind.serializers.JsonbDeserializer interface. It is used to deserialize the type it’s registered on (Original). On deserialization of Original type JSONB calls JsonbDeserializer::deserialize method. This method has to contain a custom code to deserialize Original type using provided JsonpParser. There are two ways how to register JsonbSerializer/JsonbDeserializer:Using JsonbConfig::withSerializers/ JsonbConfig::withDeserializers method;true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-244.7.2Annotating a type with JsonbSerializer/JsonbDeserializer annotation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-344.7.2Implementations must provide a CDI support in serializers/deserializers to allow injection of CDI managed beans into it.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-144.8JsonbDateFormat annotation can be applied to the following targets: field, method, type, parameter, packagetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-244.8Annotation applied to more specific target overrides the same annotation applied to target with wider scope and global configuration. For example, annotation applied to type target will override the same annotation applied to package target.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-344.8Default date format and default locale can be customized globally using javax.json.bind.JsonbConfig::withDateFormat and javax.json.bind.JsonbConfig::withLocale methods.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.9-144.9JsonbNumberFormat annotation can be applied to the following targets: field, getter/setter, method, type, parameter, packagetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.9-244.9Annotation applied to more specific target overrides the same annotation applied to target with wider scope. For example, annotation applied to type target will override the same annotation applied to package target. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.10-144.10The way to set custom binary data handling strategy is to use javax.json.bin.JsonbConfig::withBinaryDataStrategy method.true -
-		falsetechnologyactivetrue
- - diff --git a/internal/docs/jsonb/Jsonb10SpecAssertions.xml b/internal/docs/jsonb/Jsonb10SpecAssertions.xml deleted file mode 100644 index 2c2257f534..0000000000 --- a/internal/docs/jsonb/Jsonb10SpecAssertions.xml +++ /dev/null @@ -1,2046 +0,0 @@ - - - - - - - - - - - JSONB - JSONB - Java API for JSON Binding - 1.0 - - - - -
-
-
-
-
-
-
- - - - -
- - - - -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - - - -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - - - -
-
- - - - - - - - JSONB:SPEC:JSB-3.1-1 - JSON Binding implementations MUST support binding of JSON documents as defined in RFC 7159 JSON Grammar. Serialized JSON output MUST conform to the RFC 7159 JSON Grammar and be encoded in UTF-8 encoding as defined in Section 8.1 (Character Encoding) of RFC 7159 - - - - - - - - - - - - JSONB:SPEC:JSB-3.1-2 - Implementations MUST support deserialization of documents conforming to RFC 7159 JSON Grammar - - - - - - - - - - - JSONB:SPEC:JSB-3.1-3 - In addition, implementations SHOULD NOT allow deserialization of RFC 7159 non-conforming text (e.g. unsupported encoding, ...) and report error in such case - - - - - - - - - - - JSONB:SPEC:JSB-3.1-4 - Detection of UTF encoding of deserialized document is done as defined in the Section 3 (Encoding) of RFC 4627 - - - - - - - - - - - JSONB:SPEC:JSB-3.1-5 - Implementations SHOULD ignore presence of UTF byte order mark (BOM) and not treat it as an error. - - - - - - - - - - - JSONB:SPEC:JSB-3.2-1 - Implementations SHOULD NOT allow unmarshalling of RFC 7159 non-conforming text (e.g. unsupported encoding) and report error in such case. - - - - - - - - - - - JSONB:SPEC:JSB-3.2-2 - Implementation SHOULD also report error also during unmarshalling operation, if it is not possible to represent JSON document value in the expected Java type - - - - - - - - - - - JSONB:SPEC:JSB-3.3-1 - Implementation MUST report binding of the following basic java classes and their corresponding primitive types -java.lang.String -java.lang.Character -java.lang.Byte -java.lang.Short -java.lang.Integer -java.lang.Long -java.lang.Float -java.lang.Double -java.lang.Boolean - - - - - - - - - - - JSONB:SPEC:JSB-3.3.1-1 - Instances of type java.lang.String and java.lang.Character are marshalled to JSON String values as defined within RFC 7159 Section 7 (Strings) in UTF-8 encoding without byte order mark. - - - - - - - - - - - JSONB:SPEC:JSB-3.3.1-2 - Implementations SHOULD support deserialization of JSON text in other (than UTF-8) UTF encodings into java.lang.String instances - - - - - - - - - - - JSONB:SPEC:JSB-3.3.2-1 - Serialization of type java.lang.Byte, Short, Integer, Long, Float, Double and their corresponding primitive types to JSON Number MUST follow the conversion process defined in javadoc specification for the corresponding toString method - - - - - - - - - - - JSONB:SPEC:JSB-3.3.2-2 - Deserialization of a JSON value into java.lang.Byte, Short, Integer, Long, Float, Double instance or corresponding primitive type MUST follow the conversion process as defined in the specification for their corresponding parse$Type method, such as java.lang.Byte.parseByte for Byte. - - - - - - - - - - - JSONB:SPEC:JSB-3.3.3-1 - Serialization of type java.lang.Boolean and its corresponding boolean primitive type to JSON value MUST follow conversion process defined in specification for java.lang.Boolean.toString method - - - - - - - - - - - JSONB:SPEC:JSB-3.3.3-2 - Deserialization of a JSON value into java.lang.Boolean instance or boolean primitive type MUST follow the conversion process as defined in specification for java.lang.Boolean.parseBoolean method. - - - - - - - - - - - JSONB:SPEC:JSB-3.3.4-1 - Serialization of type java.lang.Number (if their more concrete type is not defined elsewhere in this chapter) to JSON string MUST retrieve double value returned from java.lang.Number.doubleValue() method and converting the value to JSON Number as defined in subsection 3.3.2 - - - - - - - - - - - JSONB:SPEC:JSB-3.3.4-2 - Deserialization of a JSON value into Java type java.lang.Number should return instance of java.math.BigDecimal by using conversion as defined in the specification for constructor of java.math.BigDecimal with java.lang.String. - - - - - - - - - - - JSONB:SPEC:JSB-3.4-1 - Implementations MUST support binding of the following standard Java SE classes: -java.math.BigInteger -java.math.BigDecimal -java.net.URL -java.net.URI -java.util.Optional -java.util.OptionalInt -java.util.OptionalLong -java.util.OptionalDouble - - - - - - - - - - - JSONB:SPEC:JSB-3.4.1-1 - Serialization of type java.math.BigInteger, BigDecimal to s JSON Number MUST follow the conversion process defined in specification for their toString method - - - - - - - - - - - JSONB:SPEC:JSB-3.4.1-2 - Deserialization of JSON value into java.math.BigInteger, BigDecimal instance MUST follow the conversion process as defined in the specification for constructor of java.math.BigInteger, BigDecimal with java.lang.String. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.2-1 - Serialization of type java.net.URL, URI to a JSON String value MUST follow the conversion process defined in specification for their toString method - - - - - - - - - - - JSONB:SPEC:JSB-3.4.2-2 - Deserialization of a JSON value into java.net.URL, URI instance MUST follow the conversion process as defined in the specification for constructor of java.net.URL, URI with java.lang.String input. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-1 - Non-empty instances of type java.util.Optional, OptionalInt, OptionalLong, OptionalDouble are serialized to a JSON value by retrieving their contained instance and converting it to JSON value based on its type and corresponding mapping definitions within this chapter. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-2 - Class fields containing empty optional instances are treated as having a null value and serialized based on 3.14.1. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-3 - Empty optional instances in array items are serialized as null. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-4 - Deserializing into Optional, OptionalInt, OptionalLong, OptionalDouble return empty optional value for properties containing a null value. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-5 - Otherwise any non-empty Optional, OptionalInt, OptionalLong, OptionalDouble value is constructed of type unmarshalled based on mappings defined in this chapter. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-6 - Instances of type java.util.Optional T are serialized to a JSON value as JSON objects when T alone would be serialized as JSON object. When T would be serialized as a JSON value (e.g. java.lang.String, java.lang.Integer), an instance of java.util.Optional T is serialized as a JSON value (without curly brackets). - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-7 - Deserialization of a JSON value into java.util.Optional(T) MUST be supported if deserialization of a JSON value into instance of T is supported. - - - - - - - - - - - JSONB:SPEC:JSB-3.5-1 - Implementations MUST support binding of the following standard Java date/time classes: java.util.Date -java.util.Calendar -java.util.GregorianCalendar -java.util.TimeZone -java.util.SimpleTimeZone -java.time.Instant -java.time.Duration -java.time.Period -java.time.LocalDate -java.time.LocalTime -java.time.LocalDateTime -java.time.ZonedDateTime -java.time.ZoneId -java.time.ZoneOffset -java.time.OffsetDateTime -java.time.OffsetTime - - - - - - - - - - - JSONB:SPEC:JSB-3.5-2 - If not specified otherwise in this section, GMT standard time zone and offset specified from UTC Greenwich is used. - - - - - - - - - - - JSONB:SPEC:JSB-3.5-3 - If not specified otherwise, date time format for marshalling and unmarshalling is ISO 8601 without offset, as specified in java.time.format.DateTimeFormatter.ISO_DATE. - - - - - - - - - - - JSONB:SPEC:JSB-3.5-4 - Implementations MUST report error if the date/time string in JSON document does not correspond to the expected datetime format. - - - - - - - - - - - JSONB:SPEC:JSB-3.5-5 - If in strict I-JSON compliance mode, default date format is changed as it’s described in 4.4.1. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-1 - The serialization format of java.util.Date, Calendar, GregorianCalendar instances with no time information is ISO_DATE. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-2 - If time information is present, the format is ISO_DATE_TIME - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-3 - Implementations MUST support deserialization of both ISO_DATE and ISO_DATE_TIME into java.util.Date, Calendar and GregorianCalendar instances. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-1 - Implementations MUST support deserialization of any time zone format specified in java.util.TimeZone into a field or property of type java.util.TimeZone and SimpleTimeZone. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-2 - Implementations MUST report an error for deprecated three-letter time zone IDs as specified in java.util.Timezone. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-3 - The serialization format of java.util.TimeZone and SimpleTimeZone is NormalizedCustomID as specified in java.util.TimeZone. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-1 - The serialization output for a java.time.Instant instance MUST be in a ISO_INSTANT format, as specified in java.time.format.DateTimeFormatter. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-2 - Implementations MUST support the deserialization of an ISO_INSTANT formatted JSON string to a java.time.Instant instance. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-3 - Analogically, for other java.time.* classes, following mapping table matches Java types and corresponding formats: -java.time.Instant ISO_INSTANT -java.time.LocalDate ISO_LOCAL_DATE -java.time.LocalTime ISO_LOCAL_TIME -java.time.LocalDateTime ISO_LOCAL_DATE_TIME -java.time.ZonedDateTime ISO_ZONED_DATE_TIME -java.time.OffsetDateTime ISO_OFFSET_DATE_TIME -java.time.OffsetTime ISO_OFFSET_TIME - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-4 - Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneId into a field or property of type java.time.ZoneId. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-5 - The serialization format of java.time.ZoneId is the normalized zone ID as specified in java.time.ZoneId. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-6 - Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneOffset into a field or property of type java.time.ZoneOffset. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-7 - The serialization format of java.time.ZoneOffset is the normalized zone ID as specified in java.time.ZoneOffset. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-8 - Implementations MUST support the deserialization of any duration format specified in java.time.Duration into a field or property of type java.time.Duration. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-9 - This is super-set of ISO 8601 duration format. The serialization format of java.time.Duration is the ISO 8601 seconds based representation, such as PT8H6M12.345S. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-10 - Implementations MUST support the deserialization of any period format specified in java.time.Period into a field or property of type java.time.Period. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-11 - This is a super-set of ISO 8601 period format. The serialization format of java.time.Period is ISO 8601 period representation. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-12 - A zero-length period is represented as zero days 'P0D'. - - - - - - - - - - - JSONB:SPEC:JSB-3.6-1 - For an unspecified output type of a deserialization operation, as well as where output type is specified as Object.class, implementations MUST deserialize a JSON document using Java runtime types specified in table below: -object java.util.Map String,Object -array java.util.List Object -string java.lang.String -number java.math.BigDecimal -true, false java.lang.Boolean -null null - - - - - - - - - - - - JSONB:SPEC:JSB-3.6-2 - JSON object values are deserialized into an implementation of java.util.Map(String, Object) with a predictable iteration order. - - - - - - - - - - - JSONB:SPEC:JSB-3.7-1 - Any instance passed to a deserialization operation must have a public or protected no-argument constructor. Implementations SHOULD throw an error if this condition is not met. - - - - - - - - - - - JSONB:SPEC:JSB-3.7-2 - This limitation does not apply to serialization operations, as well as to classes which specify explicit instantiation methods as described in section 4.5. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-1 - For a deserialization operation of a Java property, if a matching public setter method exists, the method is called to set the value of the property. If a matching setter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching setter method exists and the field is public, then direct field assignment is used. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-2 - For a serialization operation, if a matching public getter method exists, the method is called to obtain the value of the property. If a matching getter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching getter method exists and the field is public, then the value is obtained directly from the field. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-3 - JSON Binding implementations MUST NOT deserialize into transient, final or static fields and MUST ignore name/value pairs corresponding to such fields. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-4 - Implementations MUST support serialization of final fields. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-5 - Transient and static fields MUST be ignored during serialization operation. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-6 - If a JSON document contains a name/value pair not corresponding to field or setter method, then this name/value pair MUST be ignored. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-7 - Public getter/setter methods without a corresponding field MUST be supported. When only public getter/setter method without corresponding field is present in the class, the getter method is called to obtain the value to serialize, and the setter method is called during deserialization operation. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.2-1 - Implementations MUST support the binding of public and protected nested classes. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.2-2 - For deserialization operations, both nested and encapsulating classes MUST fulfill the same instantiation requirements as specified in 3.7.1. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.3-1 - Implementations MUST support the binding of public and protected static nested classes. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.3-2 - For deserialization operations, the nested class MUST fulfill the same instantiation requirements as specified in 3.7.1. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.4-1 - Deserialization into anonymous classes is not supported. Serialization of anonymous classes is supported by default object mapping. - - - - - - - - - - - JSONB:SPEC:JSB-3.8-1 - Deserialization into polymorphic types is not supported by default mapping. - - - - - - - - - - - JSONB:SPEC:JSB-3.9-1 - Serialization of an Enum instance to a JSON String value MUST follow the conversion process defined in javadoc specification for their name(). - - - - - - - - - - - JSONB:SPEC:JSB-3.9-2 - Deserialization of a JSON value into an enum instance MUST be done by calling the enum’s valueOf(String) method. - - - - - - - - - - - JSONB:SPEC:JSB-3.10-1 - Implementations MUST support the deserialization of specific interfaces defined in 3.11 and 3.3.4. - - - - - - - - - - - JSONB:SPEC:JSB-3.10-2 - Deserialization to other interfaces is not supported and implementations SHOULD report error in such case. - - - - - - - - - - - JSONB:SPEC:JSB-3.10-3 - If a class property is defined with an interface and not concrete type, then the mapping for a serialized property is resolved based on its runtime type. - - - - - - - - - - - JSONB:SPEC:JSB-3.11-1 - Implementations MUST support binding of the following collection interfaces, classes and their implementations. -java.util.Collection -java.util.Map -java.util.Set -java.util.HashSet -java.util.NavigableSet -java.util.SortedSet -java.util.TreeSet -java.util.LinkedHashSet -java.util.TreeHashSet -java.util.HashMap -java.util.NavigableMap -java.util.SortedMap -java.util.TreeMap -java.util.LinkedHashMap -java.util.TreeHashMap -java.util.List -java.util.ArrayList -java.util.LinkedList -java.util.Deque -java.util.ArrayDeque -java.util.Queue -java.util.PriorityQueue -java.util.EnumSet -java.util.EnumMap - - - - - - - - - - - - - JSONB:SPEC:JSB-3.11-2 - Implementations of interfaces below must provide accessible default constructor. JSON Binding implementations MUST report unmarshalling error if default constructor is not present or is not in accessible scope. - - - - - - - - - - - JSONB:SPEC:JSB-3.12-1 - JSON Binding implementations MUST support binding of Java arrays of all supported Java types from this chapter into/from JSON array structures as defined in Section 5 of RFC 7159 - - - - - - - - - - - JSONB:SPEC:JSB-3.12-2 - Arrays of primitive types and multi-dimensional arrays MUST be supported. - - - - - - - - - - - JSONB:SPEC:JSB-3.13-1 - Declared fields MUST be serialized in lexicographical order into the resulting JSON document. In case of inheritance, declared fields of super class MUST be serialized before declared fields of child class. - - - - - - - - - - - JSONB:SPEC:JSB-3.13-2 - When deserializing a JSON document, declared fields MUST be set in the order of attributes present in the JSON document. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.1-1 - The result of serializing a java field with a null value is the absence of the property in the resulting JSON document. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.1-2 - The deserialization operation of a property absent in JSON document MUST not set the value of the field, the setter (if available) MUST not be called, and thus original value of the field MUST be preserved. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.1-3 - The deserialization operation of a property with a null value in a JSON document MUST set the value of the field to null value (or call setter with null value if setter is present). The exception is java.util.Optional, OptionalInt, OptionalLong, OptionalDouble instances. In this case the value of the field is set to an empty optional value. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-1 - The result of deserialization n-ary array represented in JSON document is n-ary Java array. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-2 - Null value in JSON array is represented by null value in Java array. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-3 - Serialization operation on Java array with null value at index i MUST output null value at index i of the array in resulting JSON document. - - - - - - - - - - - JSONB:SPEC:JSB-3.15-1 - According to RFC 7159 Section 7 , every Java identifier name can be transformed using identity function into a valid JSON String. Identity function MUST be used for transforming Java identifier names into name Strings in JSON document. - - - - - - - - - - - JSONB:SPEC:JSB-3.15-2 - For deserialization operations defined in 3.6 section, identity function is used to transform JSON name strings into Java String instances in the resulting map Map(String, Object). - - - - - - - - - - - JSONB:SPEC:JSB-3.15-3 - Identity function is used also for other deseralization operations. - - - - - - - - - - - JSONB:SPEC:JSB-3.15-4 - If a Java identifier with corresponding name does not exist or is not accessible, the implementations MUST report error. - - - - - - - - - - - JSONB:SPEC:JSB-3.16-1 - JSON Binding implementation MUST serialize numbers that express greater magnitude or precision than an IEEE 754 double precision number as strings. - - - - - - - - - - - JSONB:SPEC:JSB-3.17-1 - JSON Binding implementations MUST support binding of generic types. - - - - - - - - - - - JSONB:SPEC:JSB-3.17-2 - Due to type erasure, there are situations when it is not possible to obtain generic type information. There are two ways for JSON Binding implementations to obtain generic type information. If there is a class file available (in the following text referred as static type information), it is possible to obtain generic type information (effectively generic type declaration) from Signature attribute (if this information is present). - - - - - - - - - - - JSONB:SPEC:JSB-3.17-3 - The second option is to provide generic type information at runtime. To provide generic type information at runtime, an argument of java.lang.reflect.Type MUST be passed to Jsonb::toJson or to Jsonb::fromJson method. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-1 - There are several levels of information JSON Binding implementations may obtain about the type of field/class/interface: - 1. runtime type provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method - 2. static type provided in class file (effectively stored in Signature attribute) - 3. raw type - 4. no information about the type - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-2 - If there is no information about the type, JSON Binding implementation MUST treat this type as java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-3 - If only raw type of given field/class/interface is known, then the type MUST be treated like raw type. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-4 - For example, if the only available information is that given field/class/interface is of type java.util.ArrayList, than the type MUST be treated as java.util.ArrayList Object. JSON Binding implementations MUST use the most specific type derived from the information available. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-5 - Let's consider situation where there is only static type information of a given field/class/interface known, -and there is no runtime type information available. Let GenericClass T1; : : : ; Tn be part of generic type -declaration, where GenericClass is name of the generic type and T1; : : : ; Tn are type parameters. For every -Ti, where i in 1; : : : ; n, there are 3 possible options: - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-6 - 1. Ti is concrete parameter type -2. Ti is bounded parameter type -3. Ti is wildcard parameter type without bounds -In case 1, the most specific parameter type MUST be given concrete parameter type Ti. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-7 - For bounded parameter type, using bounds B1; : : : ;Bm. If m = 1, then the most specific parameter type MUST be derived from the given bound B1. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-8 - If B1 is class or interface, the most specific parameter type MUST be the class or interface. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-9 - Otherwise, the most specific parameter type SHOULD be java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-10 - If multiple bounds are specified, the first step is to resolve every bound separately. Let’s define result of such resolution as S1; : : : ; Sm specific parameter types. If S1; : : : ; Sm are java.lang.Object, then the bounded parameter type Ti MUST be java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-11 - If there is exactly one Sk, where 1 <= k <= m is different than java.lang.Object, then the most specific parameter type for this bounded parameter type Ti MUST be Sk. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-12 - If there exists Sk1; Sk2, where 1 <= k1 <= k2 <= m, then the most specific parameter type is Sk1. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-13 - For wildcard parameter type without bounds, the most specific parameter type MUST be java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-14 - Any unresolved type parameter MUST be treated as java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-15 - If runtime type is provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method, than that runtime type overrides static type declaration wherever applicable - - - - - - - - - - - JSONB:SPEC:JSB-3.18-1 - When JSON Binding implementation encounters key in key/value pair that it does not recognize, it should treat the rest of the JSON document as if the element simply did not appear, and in particular, the implementation MUST NOT treat this as an error condition. - - - - - - - - - - - JSONB:SPEC:JSB-3.19-1 - JSON Binding implementations MUST NOT produce JSON documents with members with duplicate names. In this context, "duplicate" means that the names, after processing any escaped characters, are identical sequences of Unicode characters. - - - - - - - - - - - JSONB:SPEC:JSB-3.19-2 - When non-unique property (after override and rename) is found, implementation MUST throw an exception. This doesn't apply for customized user serialization behavior implemented with the usage of JsonbAdapter mechanism. - - - - - - - - - - - JSONB:SPEC:JSB-3.20-1 - JSON Binding implementations MUST support binding of the following JSON Processing types. - -javax.json.JsonObject -javax.json.JsonArray -javax.json.JsonStructure -javax.json.JsonValue -javax.json.JsonPointer -javax.json.JsonString -javax.json.JsonNumber - - - - - - - - - - - - JSONB:SPEC:JSB-3.20-2 - Marshalling of supported javax.json.* objects/interfaces/fields MUST have the same result as marshalling these objects with javax.json.JsonWriter. - - - - - - - - - - - JSONB:SPEC:JSB-3.20-3 - Deserialization into supported javax.json.* objects/interfaces/fields MUST have the same result as unmarshalling into such objects with javax.json.JsonReader. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.1-1 - JSON Binding implementations MUST NOT serialize fields, JavaBean properties or types annotated with javax.json.bind.annotation.JsonbTransient. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.1-2 - JsonbTransient annotation is mutually exclusive with all other JSON Binding defined annotations. Implementations must throw JsonbException in the following cases: Class field is annotated with @JsonbTransient. Exception must be thrown when this field, getter or setter is annotated with other JSON Binding annotations. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.1-3 - Getter is annotated with @JsonbTransient. Exception is thrown if when the field or this getter are annotated with other JSON Binding annotations. Exception is not thrown if JSON Binding annotations are presented on the setter. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.1-4 - Setter is annotated with @JsonbTransient. Exception is thrown if when the field or this setter are annotated with other JSON Binding annotations. Exception is not thrown if JSON Binding annotations are presented on the getter. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.2-1 - To provide custom name for given field (or JavaBean property), -javax.json.bind.annotation.JsonbProperty may be used. JsonbProperty annotation may be specified on -field, getter or setter method. If specified on field, custom name is used both for serialization and -deserialization. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.2-2 - If javax.json.bind.annotation.JsonbProperty is specified on getter method, it is used -only for serialization. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.2-3 - If javax.json.bind.annotation.JsonbProperty is specified on setter method, it is used only for deserialization. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.2-4 - It is possible to specify different values for getter and setter method for javax.json.bind.annotation.JsonbProperty annotation. In such case the different custom name will be used for serialization and deserialization. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.3-1 - The way to set custom property naming strategy is to use javax.json.bin.JsonbConfig::withPropertyNamingStrategy method. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.4-1 - If duplicate name is found exception MUST be thrown. The definition of duplicate (non-unique) property -can be found in 3.19. - - - - - - - - - - - JSONB:SPEC:JSB-4.2 - The way to set custom property order strategy is to use javax.json.bin.JsonbConfig::withPropertyOrderStrategy method. - - - - - - - - - - - JSONB:SPEC:JSB-4.2-2 - To customize the order of serialized properties only for one specific type, JSON Binding provides javax.json.bind.annotation.JsonbPropertyOrder annotation. Order specified by JsonbPropertyOrder annotation overrides order specified by PropertyOrderStrategy. - - - - - - - - - - - JSONB:SPEC:JSB-4.3-1 - If annotations (JsonbNillable or JsonbProperty) on different level apply to the same field (or JavaBean property) or if there is config wide configuration and some annotation (JsonbNillable or JsonbProperty) which apply to the same field (or JavaBean property), the annotation with the smallest scope applies. - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-1 - When given object (type or package) is annotated with javax.json.bind.annotation.JsonbNillable annotation, the result of null value will be presence of associated property in JSON document with explicit null value. - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-2 - The same behavior as JsonbNillable, but only at field, parameter and method (JavaBean property) level is provided by javax.json.bind.annotation.JsonbProperty annotation with its nillable parameter - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-3 - JSON Binding implementations MUST implement override of annotations according to target of the annotation (FIELD, PARAMETER, METHOD, TYPE, PACKAGE). Type level annotation overrides behavior set at the package level. Method, parameter or field level annotation overrides behavior set at the type level. - - - - - - - - - - - JSONB:SPEC:JSB-4.3.2-1 - The way to enforce serialization of null values, is to call method javax.json.bind.JsonbConfig::withNullValues with parameter true. The way to skip serialization of null values is to call method javax.json.bind.JsonbConfig::withNullValues with parameter false. - - - - - - - - - - - JSONB:SPEC:JSB-4.4-1 - To enforce strict compliance of serialized JSON documents, JSON Binding implementations MUST implement configuration option jsonb.i-json.strict-ser-compliance. - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-1 - Uppercase rather than lowercase letters MUST be used. - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-2 - The timezone MUST always be included and optional trailing seconds MUST be included even when their value is 00. - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-3 - JSON Binding implementations MUST serialize java.util.Date, java.util.Calendar, java.util.GregorianCalendar, java.time.LocalDate, java.time.LocalDateTime and java.time.Instant in the same format as java.time.ZonedDateTime. - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-4 - The result of serialization of duration must conform to the duration production in Appendix A of RFC 3339, with the same additional restrictions - - - - - - - - - - - JSONB:SPEC:JSB-4.5-1 - At most one JsonbCreator annotation can be used to annotate custom constructor or static void factory method in a class, otherwise JsonbException MUST be thrown. - - - - - - - - - - - JSONB:SPEC:JSB-4.5-2 - Factory method annotated with JsonbCreator annotation should return instance of particular class this annotation is used for, otherwise JsonbException MUST be thrown. - - - - - - - - - - - JSONB:SPEC:JSB-4.5-3 - Mapping between parameters of constructor/factory method annotated with JsonbCreator and JSON fields is defined using JsonbProperty annotation on all parameters.In case JsonbProperty annotation on parameters is not used, parameters should be mapped from JSON fields with the same name. In this case the proper mapping is NOT guaranteed.In case a field required for a parameter mapping doesn’t exist in JSON document, JsonbException MUST be thrown. - - - - - - - - - - - JSONB:SPEC:JSB-4.6-1 - To customize scope and field access strategy as specified in section 3.7.1, it is possible to specify javax.json.bind.annotation.JsonbVisibility annotation or to override default behavior globally calling JsonbConfig::withPropertyVisibilityStrategy method with given custom property visibility strategy. - - - - - - - - - - - JSONB:SPEC:JSB-4.7.1-1 - On serialization of Original type JSONB calls JsonbAdapter::adaptToJson method of the adapter to convert Original to Adapted and serializes Adapted the standard way. There are two ways how to register JsonbAdapter: Using JsonbConfig::withAdapters method; - - - - - - - - - - - JSONB:SPEC:JSB-4.7.1-2 - Annotating a class field with JsonbTypeAdapter annotation. - - - - - - - - - - - JSONB:SPEC:JSB-4.7.1-3 - Implementations must provide a CDI support in adapters to allow injection of CDI managed beans into it. - - - - - - - - - - - JSONB:SPEC:JSB-4.7.2-1 - Serializer is a class implementing javax.json.bind.serializers.JsonbSerializer interface. It is used to serialize the type it's registered on (Original). On marshalling of Original type JSONB calls JsonbSerializer::serialize method. This method has to contain a custom code to serialize Original type using provided JsonpGenerator.Deserializer is a class implementing javax.json.bind.serializers.JsonbDeserializer interface. It is used to deserialize the type it’s registered on (Original). On deserialization of Original type JSONB calls JsonbDeserializer::deserialize method. This method has to contain a custom code to deserialize Original type using provided JsonpParser. There are two ways how to register JsonbSerializer/JsonbDeserializer:Using JsonbConfig::withSerializers/ JsonbConfig::withDeserializers method; - - - - - - - - - - - JSONB:SPEC:JSB-4.7.2-2 - Annotating a type with JsonbSerializer/JsonbDeserializer annotation. - - - - - - - - - - - JSONB:SPEC:JSB-4.7.2-3 - Implementations must provide a CDI support in serializers/deserializers to allow injection of CDI managed beans into it. - - - - - - - - - - - JSONB:SPEC:JSB-4.8-1 - JsonbDateFormat annotation can be applied to the following targets: field, method, type, parameter, package - - - - - - - - - - - JSONB:SPEC:JSB-4.8-2 - Annotation applied to more specific target overrides the same annotation applied to target with wider scope and global configuration. For example, annotation applied to type target will override the same annotation applied to package target. - - - - - - - - - - - JSONB:SPEC:JSB-4.8-3 - Default date format and default locale can be customized globally using javax.json.bind.JsonbConfig::withDateFormat and javax.json.bind.JsonbConfig::withLocale methods. - - - - - - - - - - - JSONB:SPEC:JSB-4.9-1 - JsonbNumberFormat annotation can be applied to the following targets: field, getter/setter, method, type, parameter, package - - - - - - - - - - - JSONB:SPEC:JSB-4.9-2 - Annotation applied to more specific target overrides the same annotation applied to target with wider scope. For example, annotation applied to type target will override the same annotation applied to package target. - - - - - - - - - - - JSONB:SPEC:JSB-4.10-1 - The way to set custom binary data handling strategy is to use javax.json.bin.JsonbConfig::withBinaryDataStrategy method. - - - - - - - - - - - diff --git a/internal/docs/jsonb/JsonbSpecAssertions.html b/internal/docs/jsonb/JsonbSpecAssertions.html deleted file mode 100644 index 54e4d509fe..0000000000 --- a/internal/docs/jsonb/JsonbSpecAssertions.html +++ /dev/null @@ -1,895 +0,0 @@ - - - - - -Specification Assertion Detail - - -
-
-

Java API for JSON Binding
JSONB - 1.0
- Specification Assertion Detail -

-
- - - - - - - - - - - -
TotalsTotalActiveDeprecatedRemoved
- # of Assertions - 14914810
- # of Required Assertions - 14714610
- # of Optional Assertions - 2200
-
Assertions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IDChapterSectionDescriptionRequiredDependencyImplementation SpecificDefined byStatusTestable
JSONB:SPEC:JSB-3.1-133.1JSON Binding implementations MUST support binding of JSON documents as defined in RFC 7159 JSON Grammar. Serialized JSON output MUST conform to the RFC 7159 JSON Grammar and be encoded in UTF-8 encoding as defined in Section 8.1 (Character Encoding) of RFC 7159 - true -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-233.1Implementations MUST support deserialization of documents conforming to RFC 7159 JSON Grammartrue -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-333.1In addition, implementations SHOULD NOT allow deserialization of RFC 7159 non-conforming text (e.g. unsupported encoding, ...) and report error in such casefalse -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-433.1Detection of UTF encoding of deserialized document is done as defined in the Section 3 (Encoding) of RFC 4627true -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.1-533.1Implementations SHOULD ignore presence of UTF byte order mark (BOM) and not treat it as an error.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.2-133.2Implementations SHOULD NOT allow unmarshalling of RFC 7159 non-conforming text (e.g. unsupported encoding) and report error in such case.true -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.2-233.2Implementation SHOULD also report error also during unmarshalling operation, if it is not possible to represent JSON document value in the expected Java typefalse -
-		falsetechnologyactivefalse
JSONB:SPEC:JSB-3.3-133.3Implementation MUST report binding of the following basic java classes and their corresponding primitive types -java.lang.String -java.lang.Character -java.lang.Byte -java.lang.Short -java.lang.Integer -java.lang.Long -java.lang.Float -java.lang.Double -java.lang.Booleantrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.1-133.3.1Instances of type java.lang.String and java.lang.Character are marshalled to JSON String values as defined within RFC 7159 Section 7 (Strings) in UTF-8 encoding without byte order mark. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.1-233.3.2Implementations SHOULD support deserialization of JSON text in other (than UTF-8) UTF encodings into java.lang.String instancestrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.2-133.3.2Serialization of type java.lang.Byte, Short, Integer, Long, Float, Double and their corresponding primitive types to JSON Number MUST follow the conversion process defined in javadoc specification for the corresponding toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.2-233.3.2Deserialization of a JSON value into java.lang.Byte, Short, Integer, Long, Float, Double instance or corresponding primitive type MUST follow the conversion process as defined in the specification for their corresponding parse$Type method, such as java.lang.Byte.parseByte for Byte.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.3-133.3.3Serialization of type java.lang.Boolean and its corresponding boolean primitive type to JSON value MUST follow conversion process defined in specification for java.lang.Boolean.toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.3-233.3.3Deserialization of a JSON value into java.lang.Boolean instance or boolean primitive type MUST follow the conversion process as defined in specification for java.lang.Boolean.parseBoolean method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.4-133.3.4Serialization of type java.lang.Number (if their more concrete type is not defined elsewhere in this chapter) to JSON string MUST retrieve double value returned from java.lang.Number.doubleValue() method and converting the value to JSON Number as defined in subsection 3.3.2true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.3.4-233.3.4Deserialization of a JSON value into Java type java.lang.Number should return instance of java.math.BigDecimal by using conversion as defined in the specification for constructor of java.math.BigDecimal with java.lang.String.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4-133.4Implementations MUST support binding of the following standard Java SE classes: -java.math.BigInteger -java.math.BigDecimal -java.net.URL -java.net.URI -java.util.Optional -java.util.OptionalInt -java.util.OptionalLong -java.util.OptionalDouble true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.1-133.4.1Serialization of type java.math.BigInteger, BigDecimal to s JSON Number MUST follow the conversion process defined in specification for their toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.1-233.4.2Deserialization of JSON value into java.math.BigInteger, BigDecimal instance MUST follow the conversion process as defined in the specification for constructor of java.math.BigInteger, BigDecimal with java.lang.String.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.2-133.4.2Serialization of type java.net.URL, URI to a JSON String value MUST follow the conversion process defined in specification for their toString methodtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.2-233.4.2Deserialization of a JSON value into java.net.URL, URI instance MUST follow the conversion process as defined in the specification for constructor of java.net.URL, URI with java.lang.String input.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-133.4.3Non-empty instances of type java.util.Optional, OptionalInt, OptionalLong, OptionalDouble are serialized to a JSON value by retrieving their contained instance and converting it to JSON value based on its type and corresponding mapping definitions within this chapter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-233.4.3Class fields containing empty optional instances are treated as having a null value and serialized based on 3.14.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-333.4.3Empty optional instances in array items are serialized as null.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-433.4.3Deserializing into Optional, OptionalInt, OptionalLong, OptionalDouble return empty optional value for properties containing a null value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-533.4.3Otherwise any non-empty Optional, OptionalInt, OptionalLong, OptionalDouble value is constructed of type unmarshalled based on mappings defined in this chapter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-633.4.3Instances of type java.util.Optional T are serialized to a JSON value as JSON objects when T alone would be serialized as JSON object. When T would be serialized as a JSON value (e.g. java.lang.String, java.lang.Integer), an instance of java.util.Optional T is serialized as a JSON value (without curly brackets).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.4.3-733.4.3Deserialization of a JSON value into java.util.Optional(T) MUST be supported if deserialization of a JSON value into instance of T is supported.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-133.5Implementations MUST support binding of the following standard Java date/time classes: java.util.Date -java.util.Calendar -java.util.GregorianCalendar -java.util.TimeZone -java.util.SimpleTimeZone -java.time.Instant -java.time.Duration -java.time.Period -java.time.LocalDate -java.time.LocalTime -java.time.LocalDateTime -java.time.ZonedDateTime -java.time.ZoneId -java.time.ZoneOffset -java.time.OffsetDateTime -java.time.OffsetTimetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-233.5If not specified otherwise in this section, GMT standard time zone and offset specified from UTC Greenwich is used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-333.5If not specified otherwise, date time format for marshalling and unmarshalling is ISO 8601 without offset, as specified in java.time.format.DateTimeFormatter.ISO_DATE.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5-433.5Implementations MUST report error if the date/time string in JSON document does not correspond to the expected datetime format. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-133.5.1The serialization format of java.util.Date, Calendar, GregorianCalendar instances with no time information is ISO_DATE.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-233.5.1If time information is present, the format is ISO_DATE_TIMEtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.1-333.5.1Implementations MUST support deserialization of both ISO_DATE and ISO_DATE_TIME into java.util.Date, Calendar and GregorianCalendar instances.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-133.5.2Implementations MUST support deserialization of any time zone format specified in java.util.TimeZone into a field or property of type java.util.TimeZone and SimpleTimeZone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-233.5.2Implementations MUST report an error for deprecated three-letter time zone IDs as specified in java.util.Timezone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.2-333.5.2The serialization format of java.util.TimeZone and SimpleTimeZone is NormalizedCustomID as specified in java.util.TimeZone.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-133.5.3The serialization output for a java.time.Instant instance MUST be in a ISO_INSTANT format, as specified in java.time.format.DateTimeFormatter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-233.5.3Implementations MUST support the deserialization of an ISO_INSTANT formatted JSON string to a java.time.Instant instance.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-333.5.3Analogically, for other java.time.* classes, following mapping table matches Java types and corresponding formats: -java.time.Instant ISO_INSTANT -java.time.LocalDate ISO_LOCAL_DATE -java.time.LocalTime ISO_LOCAL_TIME -java.time.LocalDateTime ISO_LOCAL_DATE_TIME -java.time.ZonedDateTime ISO_ZONED_DATE_TIME -java.time.OffsetDateTime ISO_OFFSET_DATE_TIME -java.time.OffsetTime ISO_OFFSET_TIMEtrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-433.5.3Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneId into a field or property of type java.time.ZoneId.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-533.5.3The serialization format of java.time.ZoneId is the normalized zone ID as specified in java.time.ZoneId.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-633.5.3Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneOffset into a field or property of type java.time.ZoneOffset.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-733.5.3The serialization format of java.time.ZoneOffset is the normalized zone ID as specified in java.time.ZoneOffset.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-833.5.3Implementations MUST support the deserialization of any duration format specified in java.time.Duration into a field or property of type java.time.Duration.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-933.5.3This is super-set of ISO 8601 duration format. The serialization format of java.time.Duration is the ISO 8601 seconds based representation, such as PT8H6M12.345S.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1033.5.3Implementations MUST support the deserialization of any period format specified in java.time.Period into a field or property of type java.time.Period.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1133.5.3This is a super-set of ISO 8601 period format. The serialization format of java.time.Period is ISO 8601 period representation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.5.3-1233.5.3A zero-length period is represented as zero days 'P0D'.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.6-133.6For an unspecified output type of a deserialization operation, as well as where output type is specified as Object.class, implementations MUST deserialize a JSON document using Java runtime types specified in table below: -object java.util.Map String,Object -array java.util.List Object -string java.lang.String -number java.math.BigDecimal -true, false java.lang.Boolean -null null -true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.6-233.6JSON object values are deserialized into an implementation of java.util.Map(String, Object) with a predictable iteration order.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7-133.7Any instance passed to a deserialization operation must have a public or protected no-argument constructor. Implementations SHOULD throw an error if this condition is not met.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7-233.7This limitation does not apply to serialization operations, as well as to classes which specify explicit instantiation methods as described in section 4.5.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-133.7.1For a deserialization operation of a Java property, if a matching public setter method exists, the method is called to set the value of the property. If a matching setter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching setter method exists and the field is public, then direct field assignment is used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-233.7.1For a serialization operation, if a matching public getter method exists, the method is called to obtain the value of the property. If a matching getter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching getter method exists and the field is public, then the value is obtained directly from the field.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-333.7.1JSON Binding implementations MUST NOT deserialize into transient, final or static fields and MUST ignore name/value pairs corresponding to such fields.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-433.7.1Implementations MUST support serialization of final fields.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-533.7.1Transient and static fields MUST be ignored during serialization operation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-633.7.1If a JSON document contains a name/value pair not corresponding to field or setter method, then this name/value pair MUST be ignored.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.1-733.7.1Public getter/setter methods without a corresponding field MUST be supported. When only public getter/setter method without corresponding field is present in the class, the getter method is called to obtain the value to serialize, and the setter method is called during deserialization operation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.2-133.7.2Implementations MUST support the binding of public and protected nested classes.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.2-233.7.2For deserialization operations, both nested and encapsulating classes MUST fulfill the same instantiation requirements as specified in 3.7.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.3-133.7.3Implementations MUST support the binding of public and protected static nested classes.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.3-233.7.3For deserialization operations, the nested class MUST fulfill the same instantiation requirements as specified in 3.7.1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.7.4-133.7.4Deserialization into anonymous classes is not supported. Serialization of anonymous classes is supported by default object mapping.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.8-133.8Deserialization into polymorphic types is not supported by default mapping.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.9-133.9Serialization of an Enum instance to a JSON String value MUST follow the conversion process defined in javadoc specification for their name().true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.9-233.9Deserialization of a JSON value into an enum instance MUST be done by calling the enum’s valueOf(String) method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-133.10Implementations MUST support the deserialization of specific interfaces defined in 3.11 and 3.3.4.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-233.10Deserialization to other interfaces is not supported and implementations SHOULD report error in such case.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.10-333.10If a class property is defined with an interface and not concrete type, then the mapping for a serialized property is resolved based on its runtime type.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.11-133.11Implementations MUST support binding of the following collection interfaces, classes and their implementations. -java.util.Collection -java.util.Map -java.util.Set -java.util.HashSet -java.util.NavigableSet -java.util.SortedSet -java.util.TreeSet -java.util.LinkedHashSet -java.util.TreeHashSet -java.util.HashMap -java.util.NavigableMap -java.util.SortedMap -java.util.TreeMap -java.util.LinkedHashMap -java.util.TreeHashMap -java.util.List -java.util.ArrayList -java.util.LinkedList -java.util.Deque -java.util.ArrayDeque -java.util.Queue -java.util.PriorityQueue -java.util.EnumSet -java.util.EnumMap - -true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.11-233.11Implementations of interfaces below must provide accessible default constructor. JSON Binding implementations MUST report unmarshalling error if default constructor is not present or is not in accessible scope.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.12-133.12JSON Binding implementations MUST support binding of Java arrays of all supported Java types from this chapter into/from JSON array structures as defined in Section 5 of RFC 7159true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.12-233.12Arrays of primitive types and multi-dimensional arrays MUST be supported.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.13-133.13Declared fields MUST be serialized in lexicographical order into the resulting JSON document. In case of inheritance, declared fields of super class MUST be serialized before declared fields of child class.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.13-233.13When deserializing a JSON document, declared fields MUST be set in the order of attributes present in the JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-133.14.1The result of serializing a java field with a null value is the absence of the property in the resulting JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-233.14.1The deserialization operation of a property absent in JSON document MUST not set the value of the field, the setter (if available) MUST not be called, and thus original value of the field MUST be preserved.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.1-333.14.1The deserialization operation of a property with a null value in a JSON document MUST set the value of the field to null value (or call setter with null value if setter is present). The exception is java.util.Optional, OptionalInt, OptionalLong, OptionalDouble instances. In this case the value of the field is set to an empty optional value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-133.14.2The result of deserialization n-ary array represented in JSON document is n-ary Java array.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-233.14.2Null value in JSON array is represented by null value in Java array.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.14.2-333.14.2Serialization operation on Java array with null value at index i MUST output null value at index i of the array in resulting JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-133.15According to RFC 7159 Section 7 , every Java identifier name can be transformed using identity function into a valid JSON String. Identity function MUST be used for transforming Java identifier names into name Strings in JSON document.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-233.15For deserialization operations defined in 3.6 section, identity function is used to transform JSON name strings into Java String instances in the resulting map Map(String, Object).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.15-333.15Identity function is used also for other deseralization operations.true -
-		falsetechnologydeprecatedtrue
JSONB:SPEC:JSB-3.15-433.15If a Java identifier with corresponding name does not exist or is not accessible, the implementations MUST report error.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.16-133.16JSON Binding implementation MUST serialize numbers that express greater magnitude or precision than an IEEE 754 double precision number as strings.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-133.17JSON Binding implementations MUST support binding of generic types.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-233.17Due to type erasure, there are situations when it is not possible to obtain generic type information. There are two ways for JSON Binding implementations to obtain generic type information. If there is a class file available (in the following text referred as static type information), it is possible to obtain generic type information (effectively generic type declaration) from Signature attribute (if this information is present).true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17-333.17The second option is to provide generic type information at runtime. To provide generic type information at runtime, an argument of java.lang.reflect.Type MUST be passed to Jsonb::toJson or to Jsonb::fromJson method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-133.17.1There are several levels of information JSON Binding implementations may obtain about the type of field/class/interface: - 1. runtime type provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method - 2. static type provided in class file (effectively stored in Signature attribute) - 3. raw type - 4. no information about the typetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-233.17.1If there is no information about the type, JSON Binding implementation MUST treat this type as java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-333.17.1If only raw type of given field/class/interface is known, then the type MUST be treated like raw type.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-433.17.1For example, if the only available information is that given field/class/interface is of type java.util.ArrayList, than the type MUST be treated as java.util.ArrayList Object. JSON Binding implementations MUST use the most specific type derived from the information available.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-533.17.1Let's consider situation where there is only static type information of a given field/class/interface known, -and there is no runtime type information available. Let GenericClass T1; : : : ; Tn be part of generic type -declaration, where GenericClass is name of the generic type and T1; : : : ; Tn are type parameters. For every -Ti, where i in 1; : : : ; n, there are 3 possible options:true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-633.17.11. Ti is concrete parameter type -2. Ti is bounded parameter type -3. Ti is wildcard parameter type without bounds -In case 1, the most specific parameter type MUST be given concrete parameter type Ti.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-733.17.1For bounded parameter type, using bounds B1; : : : ;Bm. If m = 1, then the most specific parameter type MUST be derived from the given bound B1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-833.17.1If B1 is class or interface, the most specific parameter type MUST be the class or interface.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-933.17.1Otherwise, the most specific parameter type SHOULD be java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1033.17.1If multiple bounds are specified, the first step is to resolve every bound separately. Let’s define result of such resolution as S1; : : : ; Sm specific parameter types. If S1; : : : ; Sm are java.lang.Object, then the bounded parameter type Ti MUST be java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1133.17.1If there is exactly one Sk, where 1 <= k <= m is different than java.lang.Object, then the most specific parameter type for this bounded parameter type Ti MUST be Sk.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1233.17.1If there exists Sk1; Sk2, where 1 <= k1 <= k2 <= m, then the most specific parameter type is Sk1.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1333.17.1For wildcard parameter type without bounds, the most specific parameter type MUST be java.lang.Object.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1433.17.1Any unresolved type parameter MUST be treated as java.lang.Object. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.17.1-1533.17.1If runtime type is provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method, than that runtime type overrides static type declaration wherever applicabletrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.18-133.18When JSON Binding implementation encounters key in key/value pair that it does not recognize, it should treat the rest of the JSON document as if the element simply did not appear, and in particular, the implementation MUST NOT treat this as an error condition.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.19-133.19JSON Binding implementations MUST NOT produce JSON documents with members with duplicate names. In this context, "duplicate" means that the names, after processing any escaped characters, are identical sequences of Unicode characters.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.19-233.19When non-unique property (after override and rename) is found, implementation MUST throw an exception. This doesn't apply for customized user serialization behavior implemented with the usage of JsonbAdapter mechanism.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-133.20JSON Binding implementations MUST support binding of the following JSON Processing types. - -javax.json.JsonObject -javax.json.JsonArray -javax.json.JsonStructure -javax.json.JsonValue -javax.json.JsonPointer -javax.json.JsonString -javax.json.JsonNumber - true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-233.20Marshalling of supported javax.json.* objects/interfaces/fields MUST have the same result as marshalling these objects with javax.json.JsonWriter.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-3.20-333.20Deserialization into supported javax.json.* objects/interfaces/fields MUST have the same result as unmarshalling into such objects with javax.json.JsonReader.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-144.1.1JSON Binding implementations MUST NOT serialize fields, JavaBean properties or types annotated with javax.json.bind.annotation.JsonbTransient.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.1-244.1.1JsonbTransient annotation is mutually exclusive with all other JSON Binding defined annotations. If this condition is not met, JSON Binding implementation MUST throw JsonbException.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-144.1.2To provide custom name for given field (or JavaBean property), -javax.json.bind.annotation.JsonbProperty may be used. JsonbProperty annotation may be specified on -field, getter or setter method. If specified on field, custom name is used both for serialization and -deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-244.1.2If javax.json.bind.annotation.JsonbProperty is specified on getter method, it is used -only for serialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-344.1.2If javax.json.bind.annotation.JsonbProperty is specified on setter method, it is used only for deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.2-444.1.2It is possible to specify different values for getter and setter method for javax.json.bind.annotation.JsonbProperty annotation. In such case the different custom name will be used for serialization and deserialization.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.3-144.1.2The way to set custom property naming strategy is to use javax.json.bin.JsonbConfig::withPropertyNamingStrategy method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.1.4-144.1.3If duplicate name is found exception MUST be thrown. The definition of duplicate (non-unique) property -can be found in 3.19.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.244.2The way to set custom property order strategy is to use javax.json.bin.JsonbConfig::withPropertyOrderStrategy method.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.2-244.2To customize the order of serialized properties only for one specific type, JSON Binding provides javax.json.bind.annotation.JsonbPropertyOrder annotation. Order specified by JsonbPropertyOrder annotation overrides order specified by PropertyOrderStrategy.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3-144.3.1If annotations (JsonbNillable or JsonbProperty) on different level apply to the same field (or JavaBean property) or if there is config wide configuration and some annotation (JsonbNillable or JsonbProperty) which apply to the same field (or JavaBean property), the annotation with the smallest scope applies.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-144.3.1When given object (type or package) is annotated with javax.json.bind.annotation.JsonbNillable annotation, the result of null value will be presence of associated property in JSON document with explicit null value.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-244.3.1The same behavior as JsonbNillable, but only at field, parameter and method (JavaBean property) level is provided by javax.json.bind.annotation.JsonbProperty annotation with its nillable parametertrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.1-344.3.1JSON Binding implementations MUST implement override of annotations according to target of the annotation (FIELD, PARAMETER, METHOD, TYPE, PACKAGE). Type level annotation overrides behavior set at the package level. Method, parameter or field level annotation overrides behavior set at the type level.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.3.2-144.3.2The way to enforce serialization of null values, is to call method javax.json.bind.JsonbConfig::withNullValues with parameter true. The way to skip serialization of null values is to call method javax.json.bind.JsonbConfig::withNullValues with parameter false.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4-144.4To enforce strict compliance of serialized JSON documents, JSON Binding implementations MUST implement configuration option jsonb.i-json.strict-ser-compliance.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-144.4.1Uppercase rather than lowercase letters MUST be used.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-244.4.1The timezone MUST always be included and optional trailing seconds MUST be included even when their value is 00.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-344.4.1JSON Binding implementations MUST serialize java.util.Date, java.util.Calendar, java.util.GregorianCalendar, java.time.LocalDate, java.time.LocalDateTime and java.time.Instant in the same format as java.time.ZonedDateTime.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.4.1-444.4.1The result of serialization of duration must conform to the duration production in Appendix A of RFC 3339, with the same additional restrictionstrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-144.5At most one JsonbCreator annotation can be used to annotate custom constructor or static void factory method in a class, otherwise JsonbException MUST be thrown.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-244.5Factory method annotated with JsonbCreator annotation should return instance of particular class this annotation is used for, otherwise JsonbException MUST be thrown.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.5-344.5Parameters of constructor/factory method annotated with JsonbCreator will be mapped from JSON fields with the same name. The name of a parameter can be changed annotating given parameter with JsonbProperty annotation. When a JSON field is not mappable to a parameter with the same name, JsonbException MUST be throwntrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.6-144.5To customize scope and field access strategy as specified in section 3.7.1, it is possible to specify javax.json.bind.annotation.JsonbVisibility annotation or to override default behavior globally calling JsonbConfig::withPropertyVisibilityStrategy method with given custom property visibility strategy.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-144.7.1On serialization of Original type JSONB calls JsonbAdapter::adaptToJson method of the adapter to convert Original to Adapted and serializes Adapted the standard way. There are two ways how to register JsonbAdapter: Using JsonbConfig::withAdapters method;true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-244.7.1Annotating a class field with JsonbTypeAdapter annotation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.1-344.7.1Implementations must provide a CDI support in adapters to allow injection of CDI managed beans into it.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-144.7.2Serializer is a class implementing javax.json.bind.serializers.JsonbSerializer interface. It is used to serialize the type it’s registered on (Original). On marshalling of Original type JSONB calls JsonbSerializer::serialize method. This method has to contain a custom code to serialize Original type using provided JsonpGenerator.Deserializer is a class implementing javax.json.bind.serializers.JsonbDeserializer interface. It is used to deserialize the type it’s registered on (Original). On deserialization of Original type JSONB calls JsonbDeserializer::deserialize method. This method has to contain a custom code to deserialize Original type using provided JsonpParser. There are two ways how to register JsonbSerializer/JsonbDeserializer:Using JsonbConfig::withSerializers/ JsonbConfig::withDeserializers method;true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-244.7.2Annotating a type with JsonbSerializer/JsonbDeserializer annotation.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.7.2-344.7.2Implementations must provide a CDI support in serializers/deserializers to allow injection of CDI managed beans into it.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-144.8JsonbDateFormat annotation can be applied to the following targets: field, method, type, parameter, packagetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-244.8Annotation applied to more specific target overrides the same annotation applied to target with wider scope and global configuration. For example, annotation applied to type target will override the same annotation applied to package target.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.8-344.8Default date format and default locale can be customized globally using javax.json.bind.JsonbConfig::withDateFormat and javax.json.bind.JsonbConfig::withLocale methods.true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.9-144.9 JsonbNumberFormat annotation can be applied to the following targets: field, method, type, parameter, packagetrue -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.9-244.9Annotation applied to more specific target overrides the same annotation applied to target with wider scope. For example, annotation applied to type target will override the same annotation applied to package target. true -
-		falsetechnologyactivetrue
JSONB:SPEC:JSB-4.10-144.10The way to set custom binary data handling strategy is to use javax.json.bin.JsonbConfig::withBinaryDataStrategy method.true -
-		falsetechnologyactivetrue
- - diff --git a/internal/docs/jsonb/JsonbSpecAssertions.xml b/internal/docs/jsonb/JsonbSpecAssertions.xml deleted file mode 100644 index f2f04bbcdf..0000000000 --- a/internal/docs/jsonb/JsonbSpecAssertions.xml +++ /dev/null @@ -1,2011 +0,0 @@ - - - - - - - - - - - JSONB - JSONB - Java API for JSON Binding - 1.0 - - - - -
-
-
-
-
-
-
- - - - -
- - - - -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - - - -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - - - -
-
- - - - - - - - JSONB:SPEC:JSB-3.1-1 - JSON Binding implementations MUST support binding of JSON documents as defined in RFC 7159 JSON Grammar. Serialized JSON output MUST conform to the RFC 7159 JSON Grammar and be encoded in UTF-8 encoding as defined in Section 8.1 (Character Encoding) of RFC 7159 - - - - - - - - - - - - JSONB:SPEC:JSB-3.1-2 - Implementations MUST support deserialization of documents conforming to RFC 7159 JSON Grammar - - - - - - - - - - - JSONB:SPEC:JSB-3.1-3 - In addition, implementations SHOULD NOT allow deserialization of RFC 7159 non-conforming text (e.g. unsupported encoding, ...) and report error in such case - - - - - - - - - - - JSONB:SPEC:JSB-3.1-4 - Detection of UTF encoding of deserialized document is done as defined in the Section 3 (Encoding) of RFC 4627 - - - - - - - - - - - JSONB:SPEC:JSB-3.1-5 - Implementations SHOULD ignore presence of UTF byte order mark (BOM) and not treat it as an error. - - - - - - - - - - - JSONB:SPEC:JSB-3.2-1 - Implementations SHOULD NOT allow unmarshalling of RFC 7159 non-conforming text (e.g. unsupported encoding) and report error in such case. - - - - - - - - - - - JSONB:SPEC:JSB-3.2-2 - Implementation SHOULD also report error also during unmarshalling operation, if it is not possible to represent JSON document value in the expected Java type - - - - - - - - - - - JSONB:SPEC:JSB-3.3-1 - Implementation MUST report binding of the following basic java classes and their corresponding primitive types -java.lang.String -java.lang.Character -java.lang.Byte -java.lang.Short -java.lang.Integer -java.lang.Long -java.lang.Float -java.lang.Double -java.lang.Boolean - - - - - - - - - - - JSONB:SPEC:JSB-3.3.1-1 - Instances of type java.lang.String and java.lang.Character are marshalled to JSON String values as defined within RFC 7159 Section 7 (Strings) in UTF-8 encoding without byte order mark. - - - - - - - - - - - JSONB:SPEC:JSB-3.3.1-2 - Implementations SHOULD support deserialization of JSON text in other (than UTF-8) UTF encodings into java.lang.String instances - - - - - - - - - - - JSONB:SPEC:JSB-3.3.2-1 - Serialization of type java.lang.Byte, Short, Integer, Long, Float, Double and their corresponding primitive types to JSON Number MUST follow the conversion process defined in javadoc specification for the corresponding toString method - - - - - - - - - - - JSONB:SPEC:JSB-3.3.2-2 - Deserialization of a JSON value into java.lang.Byte, Short, Integer, Long, Float, Double instance or corresponding primitive type MUST follow the conversion process as defined in the specification for their corresponding parse$Type method, such as java.lang.Byte.parseByte for Byte. - - - - - - - - - - - JSONB:SPEC:JSB-3.3.3-1 - Serialization of type java.lang.Boolean and its corresponding boolean primitive type to JSON value MUST follow conversion process defined in specification for java.lang.Boolean.toString method - - - - - - - - - - - JSONB:SPEC:JSB-3.3.3-2 - Deserialization of a JSON value into java.lang.Boolean instance or boolean primitive type MUST follow the conversion process as defined in specification for java.lang.Boolean.parseBoolean method. - - - - - - - - - - - JSONB:SPEC:JSB-3.3.4-1 - Serialization of type java.lang.Number (if their more concrete type is not defined elsewhere in this chapter) to JSON string MUST retrieve double value returned from java.lang.Number.doubleValue() method and converting the value to JSON Number as defined in subsection 3.3.2 - - - - - - - - - - - JSONB:SPEC:JSB-3.3.4-2 - Deserialization of a JSON value into Java type java.lang.Number should return instance of java.math.BigDecimal by using conversion as defined in the specification for constructor of java.math.BigDecimal with java.lang.String. - - - - - - - - - - - JSONB:SPEC:JSB-3.4-1 - Implementations MUST support binding of the following standard Java SE classes: -java.math.BigInteger -java.math.BigDecimal -java.net.URL -java.net.URI -java.util.Optional -java.util.OptionalInt -java.util.OptionalLong -java.util.OptionalDouble - - - - - - - - - - - JSONB:SPEC:JSB-3.4.1-1 - Serialization of type java.math.BigInteger, BigDecimal to s JSON Number MUST follow the conversion process defined in specification for their toString method - - - - - - - - - - - JSONB:SPEC:JSB-3.4.1-2 - Deserialization of JSON value into java.math.BigInteger, BigDecimal instance MUST follow the conversion process as defined in the specification for constructor of java.math.BigInteger, BigDecimal with java.lang.String. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.2-1 - Serialization of type java.net.URL, URI to a JSON String value MUST follow the conversion process defined in specification for their toString method - - - - - - - - - - - JSONB:SPEC:JSB-3.4.2-2 - Deserialization of a JSON value into java.net.URL, URI instance MUST follow the conversion process as defined in the specification for constructor of java.net.URL, URI with java.lang.String input. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-1 - Non-empty instances of type java.util.Optional, OptionalInt, OptionalLong, OptionalDouble are serialized to a JSON value by retrieving their contained instance and converting it to JSON value based on its type and corresponding mapping definitions within this chapter. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-2 - Class fields containing empty optional instances are treated as having a null value and serialized based on 3.14.1. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-3 - Empty optional instances in array items are serialized as null. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-4 - Deserializing into Optional, OptionalInt, OptionalLong, OptionalDouble return empty optional value for properties containing a null value. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-5 - Otherwise any non-empty Optional, OptionalInt, OptionalLong, OptionalDouble value is constructed of type unmarshalled based on mappings defined in this chapter. - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-6 - Instances of type java.util.Optional T are serialized to a JSON value as JSON objects when T alone would be serialized as JSON object. When T would be serialized as a JSON value (e.g. java.lang.String, java.lang.Integer), an instance of java.util.Optional T is serialized as a JSON value (without curly brackets). - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-7 - Deserialization of a JSON value into java.util.Optional(T) MUST be supported if deserialization of a JSON value into instance of T is supported. - - - - - - - - - - - JSONB:SPEC:JSB-3.5-1 - Implementations MUST support binding of the following standard Java date/time classes: java.util.Date -java.util.Calendar -java.util.GregorianCalendar -java.util.TimeZone -java.util.SimpleTimeZone -java.time.Instant -java.time.Duration -java.time.Period -java.time.LocalDate -java.time.LocalTime -java.time.LocalDateTime -java.time.ZonedDateTime -java.time.ZoneId -java.time.ZoneOffset -java.time.OffsetDateTime -java.time.OffsetTime - - - - - - - - - - - JSONB:SPEC:JSB-3.5-2 - If not specified otherwise in this section, GMT standard time zone and offset specified from UTC Greenwich is used. - - - - - - - - - - - JSONB:SPEC:JSB-3.5-3 - If not specified otherwise, date time format for marshalling and unmarshalling is ISO 8601 without offset, as specified in java.time.format.DateTimeFormatter.ISO_DATE. - - - - - - - - - - - JSONB:SPEC:JSB-3.5-4 - Implementations MUST report error if the date/time string in JSON document does not correspond to the expected datetime format. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-1 - The serialization format of java.util.Date, Calendar, GregorianCalendar instances with no time information is ISO_DATE. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-2 - If time information is present, the format is ISO_DATE_TIME - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-3 - Implementations MUST support deserialization of both ISO_DATE and ISO_DATE_TIME into java.util.Date, Calendar and GregorianCalendar instances. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-1 - Implementations MUST support deserialization of any time zone format specified in java.util.TimeZone into a field or property of type java.util.TimeZone and SimpleTimeZone. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-2 - Implementations MUST report an error for deprecated three-letter time zone IDs as specified in java.util.Timezone. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-3 - The serialization format of java.util.TimeZone and SimpleTimeZone is NormalizedCustomID as specified in java.util.TimeZone. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-1 - The serialization output for a java.time.Instant instance MUST be in a ISO_INSTANT format, as specified in java.time.format.DateTimeFormatter. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-2 - Implementations MUST support the deserialization of an ISO_INSTANT formatted JSON string to a java.time.Instant instance. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-3 - Analogically, for other java.time.* classes, following mapping table matches Java types and corresponding formats: -java.time.Instant ISO_INSTANT -java.time.LocalDate ISO_LOCAL_DATE -java.time.LocalTime ISO_LOCAL_TIME -java.time.LocalDateTime ISO_LOCAL_DATE_TIME -java.time.ZonedDateTime ISO_ZONED_DATE_TIME -java.time.OffsetDateTime ISO_OFFSET_DATE_TIME -java.time.OffsetTime ISO_OFFSET_TIME - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-4 - Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneId into a field or property of type java.time.ZoneId. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-5 - The serialization format of java.time.ZoneId is the normalized zone ID as specified in java.time.ZoneId. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-6 - Implementations MUST support the deserialization of any time zone ID format specified in java.time.ZoneOffset into a field or property of type java.time.ZoneOffset. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-7 - The serialization format of java.time.ZoneOffset is the normalized zone ID as specified in java.time.ZoneOffset. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-8 - Implementations MUST support the deserialization of any duration format specified in java.time.Duration into a field or property of type java.time.Duration. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-9 - This is super-set of ISO 8601 duration format. The serialization format of java.time.Duration is the ISO 8601 seconds based representation, such as PT8H6M12.345S. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-10 - Implementations MUST support the deserialization of any period format specified in java.time.Period into a field or property of type java.time.Period. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-11 - This is a super-set of ISO 8601 period format. The serialization format of java.time.Period is ISO 8601 period representation. - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-12 - A zero-length period is represented as zero days 'P0D'. - - - - - - - - - - - JSONB:SPEC:JSB-3.6-1 - For an unspecified output type of a deserialization operation, as well as where output type is specified as Object.class, implementations MUST deserialize a JSON document using Java runtime types specified in table below: -object java.util.Map String,Object -array java.util.List Object -string java.lang.String -number java.math.BigDecimal -true, false java.lang.Boolean -null null - - - - - - - - - - - - JSONB:SPEC:JSB-3.6-2 - JSON object values are deserialized into an implementation of java.util.Map(String, Object) with a predictable iteration order. - - - - - - - - - - - JSONB:SPEC:JSB-3.7-1 - Any instance passed to a deserialization operation must have a public or protected no-argument constructor. Implementations SHOULD throw an error if this condition is not met. - - - - - - - - - - - JSONB:SPEC:JSB-3.7-2 - This limitation does not apply to serialization operations, as well as to classes which specify explicit instantiation methods as described in section 4.5. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-1 - For a deserialization operation of a Java property, if a matching public setter method exists, the method is called to set the value of the property. If a matching setter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching setter method exists and the field is public, then direct field assignment is used. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-2 - For a serialization operation, if a matching public getter method exists, the method is called to obtain the value of the property. If a matching getter method with private, protected, or defaulted to package-only access exists, then this field is ignored. If no matching getter method exists and the field is public, then the value is obtained directly from the field. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-3 - JSON Binding implementations MUST NOT deserialize into transient, final or static fields and MUST ignore name/value pairs corresponding to such fields. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-4 - Implementations MUST support serialization of final fields. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-5 - Transient and static fields MUST be ignored during serialization operation. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-6 - If a JSON document contains a name/value pair not corresponding to field or setter method, then this name/value pair MUST be ignored. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-7 - Public getter/setter methods without a corresponding field MUST be supported. When only public getter/setter method without corresponding field is present in the class, the getter method is called to obtain the value to serialize, and the setter method is called during deserialization operation. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.2-1 - Implementations MUST support the binding of public and protected nested classes. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.2-2 - For deserialization operations, both nested and encapsulating classes MUST fulfill the same instantiation requirements as specified in 3.7.1. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.3-1 - Implementations MUST support the binding of public and protected static nested classes. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.3-2 - For deserialization operations, the nested class MUST fulfill the same instantiation requirements as specified in 3.7.1. - - - - - - - - - - - JSONB:SPEC:JSB-3.7.4-1 - Deserialization into anonymous classes is not supported. Serialization of anonymous classes is supported by default object mapping. - - - - - - - - - - - JSONB:SPEC:JSB-3.8-1 - Deserialization into polymorphic types is not supported by default mapping. - - - - - - - - - - - JSONB:SPEC:JSB-3.9-1 - Serialization of an Enum instance to a JSON String value MUST follow the conversion process defined in javadoc specification for their name(). - - - - - - - - - - - JSONB:SPEC:JSB-3.9-2 - Deserialization of a JSON value into an enum instance MUST be done by calling the enum’s valueOf(String) method. - - - - - - - - - - - JSONB:SPEC:JSB-3.10-1 - Implementations MUST support the deserialization of specific interfaces defined in 3.11 and 3.3.4. - - - - - - - - - - - JSONB:SPEC:JSB-3.10-2 - Deserialization to other interfaces is not supported and implementations SHOULD report error in such case. - - - - - - - - - - - JSONB:SPEC:JSB-3.10-3 - If a class property is defined with an interface and not concrete type, then the mapping for a serialized property is resolved based on its runtime type. - - - - - - - - - - - JSONB:SPEC:JSB-3.11-1 - Implementations MUST support binding of the following collection interfaces, classes and their implementations. -java.util.Collection -java.util.Map -java.util.Set -java.util.HashSet -java.util.NavigableSet -java.util.SortedSet -java.util.TreeSet -java.util.LinkedHashSet -java.util.TreeHashSet -java.util.HashMap -java.util.NavigableMap -java.util.SortedMap -java.util.TreeMap -java.util.LinkedHashMap -java.util.TreeHashMap -java.util.List -java.util.ArrayList -java.util.LinkedList -java.util.Deque -java.util.ArrayDeque -java.util.Queue -java.util.PriorityQueue -java.util.EnumSet -java.util.EnumMap - - - - - - - - - - - - - JSONB:SPEC:JSB-3.11-2 - Implementations of interfaces below must provide accessible default constructor. JSON Binding implementations MUST report unmarshalling error if default constructor is not present or is not in accessible scope. - - - - - - - - - - - JSONB:SPEC:JSB-3.12-1 - JSON Binding implementations MUST support binding of Java arrays of all supported Java types from this chapter into/from JSON array structures as defined in Section 5 of RFC 7159 - - - - - - - - - - - JSONB:SPEC:JSB-3.12-2 - Arrays of primitive types and multi-dimensional arrays MUST be supported. - - - - - - - - - - - JSONB:SPEC:JSB-3.13-1 - Declared fields MUST be serialized in lexicographical order into the resulting JSON document. In case of inheritance, declared fields of super class MUST be serialized before declared fields of child class. - - - - - - - - - - - JSONB:SPEC:JSB-3.13-2 - When deserializing a JSON document, declared fields MUST be set in the order of attributes present in the JSON document. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.1-1 - The result of serializing a java field with a null value is the absence of the property in the resulting JSON document. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.1-2 - The deserialization operation of a property absent in JSON document MUST not set the value of the field, the setter (if available) MUST not be called, and thus original value of the field MUST be preserved. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.1-3 - The deserialization operation of a property with a null value in a JSON document MUST set the value of the field to null value (or call setter with null value if setter is present). The exception is java.util.Optional, OptionalInt, OptionalLong, OptionalDouble instances. In this case the value of the field is set to an empty optional value. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-1 - The result of deserialization n-ary array represented in JSON document is n-ary Java array. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-2 - Null value in JSON array is represented by null value in Java array. - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-3 - Serialization operation on Java array with null value at index i MUST output null value at index i of the array in resulting JSON document. - - - - - - - - - - - JSONB:SPEC:JSB-3.15-1 - According to RFC 7159 Section 7 , every Java identifier name can be transformed using identity function into a valid JSON String. Identity function MUST be used for transforming Java identifier names into name Strings in JSON document. - - - - - - - - - - - JSONB:SPEC:JSB-3.15-2 - For deserialization operations defined in 3.6 section, identity function is used to transform JSON name strings into Java String instances in the resulting map Map(String, Object). - - - - - - - - - - - JSONB:SPEC:JSB-3.15-3 - Identity function is used also for other deseralization operations. - - - - - - - - - - - JSONB:SPEC:JSB-3.15-4 - If a Java identifier with corresponding name does not exist or is not accessible, the implementations MUST report error. - - - - - - - - - - - JSONB:SPEC:JSB-3.16-1 - JSON Binding implementation MUST serialize numbers that express greater magnitude or precision than an IEEE 754 double precision number as strings. - - - - - - - - - - - JSONB:SPEC:JSB-3.17-1 - JSON Binding implementations MUST support binding of generic types. - - - - - - - - - - - JSONB:SPEC:JSB-3.17-2 - Due to type erasure, there are situations when it is not possible to obtain generic type information. There are two ways for JSON Binding implementations to obtain generic type information. If there is a class file available (in the following text referred as static type information), it is possible to obtain generic type information (effectively generic type declaration) from Signature attribute (if this information is present). - - - - - - - - - - - JSONB:SPEC:JSB-3.17-3 - The second option is to provide generic type information at runtime. To provide generic type information at runtime, an argument of java.lang.reflect.Type MUST be passed to Jsonb::toJson or to Jsonb::fromJson method. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-1 - There are several levels of information JSON Binding implementations may obtain about the type of field/class/interface: - 1. runtime type provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method - 2. static type provided in class file (effectively stored in Signature attribute) - 3. raw type - 4. no information about the type - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-2 - If there is no information about the type, JSON Binding implementation MUST treat this type as java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-3 - If only raw type of given field/class/interface is known, then the type MUST be treated like raw type. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-4 - For example, if the only available information is that given field/class/interface is of type java.util.ArrayList, than the type MUST be treated as java.util.ArrayList Object. JSON Binding implementations MUST use the most specific type derived from the information available. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-5 - Let's consider situation where there is only static type information of a given field/class/interface known, -and there is no runtime type information available. Let GenericClass T1; : : : ; Tn be part of generic type -declaration, where GenericClass is name of the generic type and T1; : : : ; Tn are type parameters. For every -Ti, where i in 1; : : : ; n, there are 3 possible options: - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-6 - 1. Ti is concrete parameter type -2. Ti is bounded parameter type -3. Ti is wildcard parameter type without bounds -In case 1, the most specific parameter type MUST be given concrete parameter type Ti. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-7 - For bounded parameter type, using bounds B1; : : : ;Bm. If m = 1, then the most specific parameter type MUST be derived from the given bound B1. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-8 - If B1 is class or interface, the most specific parameter type MUST be the class or interface. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-9 - Otherwise, the most specific parameter type SHOULD be java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-10 - If multiple bounds are specified, the first step is to resolve every bound separately. Let’s define result of such resolution as S1; : : : ; Sm specific parameter types. If S1; : : : ; Sm are java.lang.Object, then the bounded parameter type Ti MUST be java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-11 - If there is exactly one Sk, where 1 <= k <= m is different than java.lang.Object, then the most specific parameter type for this bounded parameter type Ti MUST be Sk. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-12 - If there exists Sk1; Sk2, where 1 <= k1 <= k2 <= m, then the most specific parameter type is Sk1. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-13 - For wildcard parameter type without bounds, the most specific parameter type MUST be java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-14 - Any unresolved type parameter MUST be treated as java.lang.Object. - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-15 - If runtime type is provided via java.lang.reflect.Type parameter passed to Jsonb::toJson or Jsonb::fromJson method, than that runtime type overrides static type declaration wherever applicable - - - - - - - - - - - JSONB:SPEC:JSB-3.18-1 - When JSON Binding implementation encounters key in key/value pair that it does not recognize, it should treat the rest of the JSON document as if the element simply did not appear, and in particular, the implementation MUST NOT treat this as an error condition. - - - - - - - - - - - JSONB:SPEC:JSB-3.19-1 - JSON Binding implementations MUST NOT produce JSON documents with members with duplicate names. In this context, "duplicate" means that the names, after processing any escaped characters, are identical sequences of Unicode characters. - - - - - - - - - - - JSONB:SPEC:JSB-3.19-2 - When non-unique property (after override and rename) is found, implementation MUST throw an exception. This doesn't apply for customized user serialization behavior implemented with the usage of JsonbAdapter mechanism. - - - - - - - - - - - JSONB:SPEC:JSB-3.20-1 - JSON Binding implementations MUST support binding of the following JSON Processing types. - -javax.json.JsonObject -javax.json.JsonArray -javax.json.JsonStructure -javax.json.JsonValue -javax.json.JsonPointer -javax.json.JsonString -javax.json.JsonNumber - - - - - - - - - - - - JSONB:SPEC:JSB-3.20-2 - Marshalling of supported javax.json.* objects/interfaces/fields MUST have the same result as marshalling these objects with javax.json.JsonWriter. - - - - - - - - - - - JSONB:SPEC:JSB-3.20-3 - Deserialization into supported javax.json.* objects/interfaces/fields MUST have the same result as unmarshalling into such objects with javax.json.JsonReader. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.1-1 - JSON Binding implementations MUST NOT serialize fields, JavaBean properties or types annotated with javax.json.bind.annotation.JsonbTransient. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.1-2 - JsonbTransient annotation is mutually exclusive with all other JSON Binding defined annotations. If this condition is not met, JSON Binding implementation MUST throw JsonbException. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.2-1 - To provide custom name for given field (or JavaBean property), -javax.json.bind.annotation.JsonbProperty may be used. JsonbProperty annotation may be specified on -field, getter or setter method. If specified on field, custom name is used both for serialization and -deserialization. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.2-2 - If javax.json.bind.annotation.JsonbProperty is specified on getter method, it is used -only for serialization. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.2-3 - If javax.json.bind.annotation.JsonbProperty is specified on setter method, it is used only for deserialization. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.2-4 - It is possible to specify different values for getter and setter method for javax.json.bind.annotation.JsonbProperty annotation. In such case the different custom name will be used for serialization and deserialization. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.3-1 - The way to set custom property naming strategy is to use javax.json.bin.JsonbConfig::withPropertyNamingStrategy method. - - - - - - - - - - - JSONB:SPEC:JSB-4.1.4-1 - If duplicate name is found exception MUST be thrown. The definition of duplicate (non-unique) property -can be found in 3.19. - - - - - - - - - - - JSONB:SPEC:JSB-4.2 - The way to set custom property order strategy is to use javax.json.bin.JsonbConfig::withPropertyOrderStrategy method. - - - - - - - - - - - JSONB:SPEC:JSB-4.2-2 - To customize the order of serialized properties only for one specific type, JSON Binding provides javax.json.bind.annotation.JsonbPropertyOrder annotation. Order specified by JsonbPropertyOrder annotation overrides order specified by PropertyOrderStrategy. - - - - - - - - - - - JSONB:SPEC:JSB-4.3-1 - If annotations (JsonbNillable or JsonbProperty) on different level apply to the same field (or JavaBean property) or if there is config wide configuration and some annotation (JsonbNillable or JsonbProperty) which apply to the same field (or JavaBean property), the annotation with the smallest scope applies. - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-1 - When given object (type or package) is annotated with javax.json.bind.annotation.JsonbNillable annotation, the result of null value will be presence of associated property in JSON document with explicit null value. - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-2 - The same behavior as JsonbNillable, but only at field, parameter and method (JavaBean property) level is provided by javax.json.bind.annotation.JsonbProperty annotation with its nillable parameter - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-3 - JSON Binding implementations MUST implement override of annotations according to target of the annotation (FIELD, PARAMETER, METHOD, TYPE, PACKAGE). Type level annotation overrides behavior set at the package level. Method, parameter or field level annotation overrides behavior set at the type level. - - - - - - - - - - - JSONB:SPEC:JSB-4.3.2-1 - The way to enforce serialization of null values, is to call method javax.json.bind.JsonbConfig::withNullValues with parameter true. The way to skip serialization of null values is to call method javax.json.bind.JsonbConfig::withNullValues with parameter false. - - - - - - - - - - - JSONB:SPEC:JSB-4.4-1 - To enforce strict compliance of serialized JSON documents, JSON Binding implementations MUST implement configuration option jsonb.i-json.strict-ser-compliance. - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-1 - Uppercase rather than lowercase letters MUST be used. - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-2 - The timezone MUST always be included and optional trailing seconds MUST be included even when their value is 00. - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-3 - JSON Binding implementations MUST serialize java.util.Date, java.util.Calendar, java.util.GregorianCalendar, java.time.LocalDate, java.time.LocalDateTime and java.time.Instant in the same format as java.time.ZonedDateTime. - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-4 - The result of serialization of duration must conform to the duration production in Appendix A of RFC 3339, with the same additional restrictions - - - - - - - - - - - JSONB:SPEC:JSB-4.5-1 - At most one JsonbCreator annotation can be used to annotate custom constructor or static void factory method in a class, otherwise JsonbException MUST be thrown. - - - - - - - - - - - JSONB:SPEC:JSB-4.5-2 - Factory method annotated with JsonbCreator annotation should return instance of particular class this annotation is used for, otherwise JsonbException MUST be thrown. - - - - - - - - - - - JSONB:SPEC:JSB-4.5-3 - Parameters of constructor/factory method annotated with JsonbCreator will be mapped from JSON fields with the same name. The name of a parameter can be changed annotating given parameter with JsonbProperty annotation. When a JSON field is not mappable to a parameter with the same name, JsonbException MUST be thrown - - - - - - - - - - - JSONB:SPEC:JSB-4.6-1 - To customize scope and field access strategy as specified in section 3.7.1, it is possible to specify javax.json.bind.annotation.JsonbVisibility annotation or to override default behavior globally calling JsonbConfig::withPropertyVisibilityStrategy method with given custom property visibility strategy. - - - - - - - - - - - JSONB:SPEC:JSB-4.7.1-1 - On serialization of Original type JSONB calls JsonbAdapter::adaptToJson method of the adapter to convert Original to Adapted and serializes Adapted the standard way. There are two ways how to register JsonbAdapter: Using JsonbConfig::withAdapters method; - - - - - - - - - - - JSONB:SPEC:JSB-4.7.1-2 - Annotating a class field with JsonbTypeAdapter annotation. - - - - - - - - - - - JSONB:SPEC:JSB-4.7.1-3 - Implementations must provide a CDI support in adapters to allow injection of CDI managed beans into it. - - - - - - - - - - - JSONB:SPEC:JSB-4.7.2-1 - Serializer is a class implementing javax.json.bind.serializers.JsonbSerializer interface. It is used to serialize the type it’s registered on (Original). On marshalling of Original type JSONB calls JsonbSerializer::serialize method. This method has to contain a custom code to serialize Original type using provided JsonpGenerator.Deserializer is a class implementing javax.json.bind.serializers.JsonbDeserializer interface. It is used to deserialize the type it’s registered on (Original). On deserialization of Original type JSONB calls JsonbDeserializer::deserialize method. This method has to contain a custom code to deserialize Original type using provided JsonpParser. There are two ways how to register JsonbSerializer/JsonbDeserializer:Using JsonbConfig::withSerializers/ JsonbConfig::withDeserializers method; - - - - - - - - - - - JSONB:SPEC:JSB-4.7.2-2 - Annotating a type with JsonbSerializer/JsonbDeserializer annotation. - - - - - - - - - - - JSONB:SPEC:JSB-4.7.2-3 - Implementations must provide a CDI support in serializers/deserializers to allow injection of CDI managed beans into it. - - - - - - - - - - - JSONB:SPEC:JSB-4.8-1 - JsonbDateFormat annotation can be applied to the following targets: field, method, type, parameter, package - - - - - - - - - - - JSONB:SPEC:JSB-4.8-2 - Annotation applied to more specific target overrides the same annotation applied to target with wider scope and global configuration. For example, annotation applied to type target will override the same annotation applied to package target. - - - - - - - - - - - JSONB:SPEC:JSB-4.8-3 - Default date format and default locale can be customized globally using javax.json.bind.JsonbConfig::withDateFormat and javax.json.bind.JsonbConfig::withLocale methods. - - - - - - - - - - - JSONB:SPEC:JSB-4.9-1 - JsonbNumberFormat annotation can be applied to the following targets: field, method, type, parameter, package - - - - - - - - - - - JSONB:SPEC:JSB-4.9-2 - Annotation applied to more specific target overrides the same annotation applied to target with wider scope. For example, annotation applied to type target will override the same annotation applied to package target. - - - - - - - - - - - JSONB:SPEC:JSB-4.10-1 - The way to set custom binary data handling strategy is to use javax.json.bin.JsonbConfig::withBinaryDataStrategy method. - - - - - - - - - - - - diff --git a/internal/docs/jsonb/README.txt b/internal/docs/jsonb/README.txt deleted file mode 100644 index 06ded981e0..0000000000 --- a/internal/docs/jsonb/README.txt +++ /dev/null @@ -1,80 +0,0 @@ -Simple README file with instructions to quickly install, setup, configure, -and run the JSON-B TCK 1.0 and related software against the JSON-B RI 1.0. For -more detailed instructions please refer to the JSON-B TCK 1.0 Users Guide. - ------------------------ -Installing the Software ------------------------ -Before you can run the JSON-B TCK tests, you need to install -and set up the following software components: - -1) Java SE 8 -2) JSON-B RI Version 1.0 -3) JSON-B TCK Version 1.0 - -1. Download and install Java SE 8 software. - - mkdir /javase8 - cd /javase8 - unzip - -2. Download and install the JSON-B 1.0 Reference Implementation. - - mkdir /ri - cd /ri - unzip - -3. Download and install the JSON-B TCK 1.0 software. - - mkdir /tck - cd /tck - unzip jsonbtck-1.0_10-May-2017.zip - ------------------------------------------ -Setup and Configuration of the JSON-B TCK ------------------------------------------ -1. Configure the JSON-B TCK to run against the JSON-B RI. Set the following - variables in your shell environment. - - setenv JAVA_HOME /javase8 - setenv TS_HOME /tck/jsonbtck - setenv ANT_HOME /tck/anthome - setenv PATH $JAVA_HOME/bin:$ANT_HOME/bin:$PATH - -2. Edit the $TS_HOME/bin/ts.jte file and set the following properties: - - jsonb.classes=/ri/jakarta.json.bind-ri-1.0/lib/yasson-1.0.jar - - Add the path to the JSON-B 1.0 Reference Implementation jar - ------------------------------- -Executing the JSON-B TCK Tests ------------------------------- -At this point we are ready to run the JSON-B TCK tests against the JSON-B 1.0 -Reference Implementation. - -1. Execute and run the JSON-B TCK tests. - - cd $TS_HOME/bin - ant run.all | tee run.log - - This will run all the JSON-B TCK tests including the signature tests. - -2. Another way to execute and run the JSON-B TCK tests. - - Run just the jsonb tree of tests: - - cd $TS_HOME/src/com/sun/ts/tests/jsonb/api - ant runclient | tee run.log - - Run just the jsonb signature tests: - - cd $TS_HOME/src/com/sun/ts/tests/signaturetests/jsonb - ant runclient | tee run.log - -3. The third way to execute and run the JSON-B TCK tests is to use the - JavaTest GUI. - - cd $TS_HOME/bin - ant gui // Follow the JSON-B TCK Users Guide and JavaTest Harness Guide - // to configure the JSON-B TCK via the JavaTest GUI configurator diff --git a/internal/docs/jsonb/extracted-ids.xml b/internal/docs/jsonb/extracted-ids.xml deleted file mode 100644 index 640bc6fb65..0000000000 --- a/internal/docs/jsonb/extracted-ids.xml +++ /dev/null @@ -1,1617 +0,0 @@ - - - - - - - - - - - - - - - - - - -
- - - - - - - - JSONB:SPEC:JSB-3.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.1-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.1-4 - - - - - - - - - - - - JSONB:SPEC:JSB-3.1-5 - - - - - - - - - - - - JSONB:SPEC:JSB-3.2-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.2-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3.2-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3.2-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3.3-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3.3-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3.4-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.3.4-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.2-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.2-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.3-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.2-4 - - - - - - - - - - - - JSONB:SPEC:JSB-3.4.2-5 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5-4 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.1-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.2-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-4 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-5 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-6 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-7 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-8 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-9 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-10 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-11 - - - - - - - - - - - - JSONB:SPEC:JSB-3.5.3-12 - - - - - - - - - - - - JSONB:SPEC:JSB-3.6-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.6-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.6-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-4 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-5 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.1-6 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.2-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.2-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.3-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.7.3-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.8-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.9-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.9-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.10-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.10-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.10-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.11-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.11-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.12-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.13-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.13-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.14.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.14.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.14.2-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.15-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.15-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.15-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.15-4 - - - - - - - - - - - - JSONB:SPEC:JSB-3.16-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.16-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.16-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-3 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-4 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-5 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-6 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-7 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-8 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-9 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-10 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-11 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-12 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-13 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-14 - - - - - - - - - - - - JSONB:SPEC:JSB-3.17.1-15 - - - - - - - - - - - - JSONB:SPEC:JSB-3.18-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.19-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.19-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.20-1 - - - - - - - - - - - - JSONB:SPEC:JSB-3.20-2 - - - - - - - - - - - - JSONB:SPEC:JSB-3.20-3 - - - - - - - - - - - - JSONB:SPEC:JSB-4.1.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.1.3-1 - - - - - - - - - - - - JSONB:SPEC:JSB-??-2 - - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-4.3.1-3 - - - - - - - - - - - - JSONB:SPEC:JSB-4.3.2-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.4-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-2 - - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-3 - - - - - - - - - - - - JSONB:SPEC:JSB-4.4.1-4 - - - - - - - - - - - - JSONB:SPEC:JSB-4.5-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.5-2 - - - - - - - - - - - - JSONB:SPEC:JSB-4.7-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.8-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.8-2 - - - - - - - - - - - - JSONB:SPEC:JSB-4.8-3 - - - - - - - - - - - - JSONB:SPEC:JSB-4.9-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.9-2 - - - - - - - - - - - - JSONB:SPEC:JSB-4.10-1 - - - - - - - - - - - - JSONB:SPEC:JSB-4.10-2 - - - - - - - - - - - - JSONB:SPEC:JSB-4.11-1 - - - - - - - - - - - - - diff --git a/internal/docs/jsonb/generateSpecAssertions b/internal/docs/jsonb/generateSpecAssertions deleted file mode 100644 index e62673c2a5..0000000000 --- a/internal/docs/jsonb/generateSpecAssertions +++ /dev/null @@ -1,29 +0,0 @@ -#!/bin/sh -# -# Copyright (c) 2018 Oracle and/or its affiliates. All rights reserved. -# -# This program and the accompanying materials are made available under the -# terms of the Eclipse Public License v. 2.0, which is available at -# http://www.eclipse.org/legal/epl-2.0. -# -# This Source Code may also be made available under the following Secondary -# Licenses when the conditions for such availability set forth in the -# Eclipse Public License v. 2.0 are satisfied: GNU General Public License, -# version 2 with the GNU Classpath Exception, which is available at -# https://www.gnu.org/software/classpath/license.html. -# -# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 -# - -# Generate Specification Assertions -# - -DOCS_DIR=/raja/spider/internal/docs/jsonb -TOOLS_DIR=/raja/cts-tools/trunk - -# Generate html output -# -cd ${TOOLS_DIR}/tools/xsl-transformer/scripts -./run.sh ${DOCS_DIR}/JsonbSpecAssertions.xml ${DOCS_DIR}/jsonbRegrouping.xsl ${DOCS_DIR}/JsonbSpecAssertions.html - - diff --git a/internal/docs/jsonb/jsonbRegrouping.xsl b/internal/docs/jsonb/jsonbRegrouping.xsl deleted file mode 100644 index 7add8460a8..0000000000 --- a/internal/docs/jsonb/jsonbRegrouping.xsl +++ /dev/null @@ -1,371 +0,0 @@ - - - - - - - - - - - - Specification Assertion Detail - - -
- - - - - -
-

- -
- - -
- Specification Assertion Detail -

-
- - - - - - - - - -
- - - - - - - Assertions - - - - - - - - - - - - - -
- ID - - Chapter - - Section - - Description - - Required - - Dependency - - Implementation Specific - - Defined by - - Status - - Testable -
- - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Totals - - Total - - Active - - Deprecated - - Removed -
- - # of Assertions - - - - - - - - - - - - - - - - - -
- - # of Required Assertions - - - - - - - - - - - - - - - - - -
- - # of Optional Assertions - - - - - - - - - - - - - - - - - -
-
- - diff --git a/release/tools/jsonb.xml b/release/tools/jsonb.xml deleted file mode 100644 index 24c800ce18..0000000000 --- a/release/tools/jsonb.xml +++ /dev/null @@ -1,172 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/user_guides/build_tckugs.sh b/user_guides/build_tckugs.sh index e4a93fa2f5..b5e2b11c73 100644 --- a/user_guides/build_tckugs.sh +++ b/user_guides/build_tckugs.sh @@ -1,6 +1,6 @@ #!/bin/bash -xe -# Copyright (c) 2019, 2021 Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2019, 2022 Oracle and/or its affiliates. All rights reserved. # # This program and the accompanying materials are made available under the # terms of the Eclipse Public License v. 2.0, which is available at @@ -27,7 +27,7 @@ export PATH=$JAVA_HOME/bin:$M2_HOME/bin:$PATH cd ${WORKSPACE} export BASEDIR=`pwd` export USERGUIDEDIR=$BASEDIR/user_guides -alltcks="caj concurrency el jacc jaspic jaxws jca jms jpa jsf jsonb jsp jstl jta saaj securityapi servlet websocket" +alltcks="caj concurrency el jacc jaspic jaxws jca jms jpa jsf jsp jstl jta saaj securityapi servlet websocket" cd $USERGUIDEDIR rm -rf $USERGUIDEDIR/tmp diff --git a/user_guides/jsonb/README.md b/user_guides/jsonb/README.md deleted file mode 100644 index a3ec2b697b..0000000000 --- a/user_guides/jsonb/README.md +++ /dev/null @@ -1,77 +0,0 @@ -# A JBake project template - -## About JBake - -JBake is a static site generator, it's inspired from jekyll and written -in java. The basic idea is to have templates for the structure of the -page, and the body generated from asciidoc content. - -## Pre requisites - -- Maven -- JDK8+ - -Deploying to Github will require password less authentication. - -This is done by exporting your SSH public key into your Github account. - -## Build the site locally - -The site is generated under target/staging. - -Open file:///PATH_TO_PROJECT_DIR/target/staging in a browser to view the site. - -``` -mvn generate-resources -``` - -Or you can invoke the JBake plugin directly. - -``` -mvn jbake:build -``` - -### Rebuild the site on changes - -``` -mvn jbake:watch -``` - -If you keep this command running, changes to the sources will be -detected and the site will be rendered incrementally. - -This is convenient when writing content. - -### Serve the site locally - -``` -mvn jbake:serve -``` - -If a webserver is required (e.g. absolute path are used), this command -will start a webserver (jetty) at http://localhost:8820. It will also -watch for changes and rebuild incrementally. - -## Deploy the site to Github Pages - -``` -mvn deploy -``` - -## Produce a zip file for download - -To produce a zip file containing the generated html files, use: - -``` -mvn package -``` - -When making a release on GitHub, this zip file should be added to the release. - -## Links - -- [JBake maven plugin documentation](https://github.com/Blazebit/jbake-maven-plugin) -- [JBake documentation](http://jbake.org/docs/2.5.1) -- [Freemarker documentation](http://freemarker.org/docs) -- [AsciiDoc User Guide](http://asciidoc.org/userguide.html) -- [Asciidoctor quick reference](http://asciidoctor.org/docs/asciidoc-syntax-quick-reference) diff --git a/user_guides/jsonb/pom.xml b/user_guides/jsonb/pom.xml deleted file mode 100644 index b046f04f02..0000000000 --- a/user_guides/jsonb/pom.xml +++ /dev/null @@ -1,258 +0,0 @@ - - - - - 4.0.0 - - org.eclipse.ee4j - project - 1.0.5 - - org.glassfish - tck_jsonb - pom - 2.0.1 - Eclipse Foundation Technology Compatibility Kit User's Guide for Jakarta JSON Binding for Jakarta EE, Release 2.0 - - - UTF-8 - ${project.build.directory}/staging - true - 2.4.2 - 2.1.0 - 2.1.0 - 1.5.3 - 0.3.3 - 2.3.30 - - - Jakarta-JSON-Binding-TCK-Users-Guide.pdf - true - - - - - scm:git:git@github.com:eclipse-ee4j/jakartaee-tck.git - - - - - package - - - org.apache.maven.plugins - maven-clean-plugin - - - - src/main/jbake/content - - toc.adoc - - - - - - - org.apache.maven.plugins - maven-enforcer-plugin - - - enforce-versions - - enforce - - - - - [1.8.0,) - You need JDK8 or newer - - - - - - - - org.glassfish.doc - glassfish-doc-maven-plugin - - - generate-toc - generate-resources - - toc - - - - [0-9]+\s.*,Preface.*,Part\s.* - - - - - generate-book - generate-resources - - book - - - - - - org.jbake - jbake-maven-plugin - - ${site.output.dir} - - ${status} - - - - - build-site - generate-resources - - generate - - - - - - org.asciidoctor - asciidoctor-maven-plugin - - ${project.build.directory}/book - book.adoc - - ${project.build.directory}/staging/ - pdf - ${doc.pdf} - - ${project.basedir}/src/theme - jakartaee - book - ${status} - - - font - - - font - true - - - - true - true - - - - - generate-pdf-doc - generate-resources - - process-asciidoc - - - - - - org.apache.maven.plugins - maven-scm-publish-plugin - - - deploy-site - deploy - - publish-scm - - - gh-pages - false - Update site - - - - - - - - - - org.apache.maven.plugins - maven-clean-plugin - 3.1.0 - - - org.glassfish.doc - glassfish-doc-maven-plugin - 1.3 - - - org.apache.maven.plugins - maven-enforcer-plugin - 3.0.0-M3 - - - org.apache.maven.plugins - maven-assembly-plugin - 3.3.0 - - - org.apache.maven.plugins - maven-scm-publish-plugin - 3.1.0 - - - org.jbake - jbake-maven-plugin - ${jbake.maven.plugin.version} - - - org.asciidoctor - asciidoctorj - ${asciidoctorj.version} - - - org.asciidoctor - asciidoctorj-diagram - ${asciidoctorj.diagram.version} - - - org.freemarker - freemarker - ${freemarker.version} - - - - - org.asciidoctor - asciidoctor-maven-plugin - ${asciidoctorj.maven.plugin.version} - - - org.asciidoctor - asciidoctorj-pdf - ${asciidoctorj.pdf.version} - - - - - - - diff --git a/user_guides/jsonb/src/main/jbake/assets/README.md b/user_guides/jsonb/src/main/jbake/assets/README.md deleted file mode 100644 index f8f962c0ab..0000000000 --- a/user_guides/jsonb/src/main/jbake/assets/README.md +++ /dev/null @@ -1,4 +0,0 @@ -# About - -The {{site.title}} project contains the [AsciiDoc](http://asciidoc.org/) -source code for the ... diff --git a/user_guides/jsonb/src/main/jbake/assets/_config.yml b/user_guides/jsonb/src/main/jbake/assets/_config.yml deleted file mode 100644 index 016e614ac8..0000000000 --- a/user_guides/jsonb/src/main/jbake/assets/_config.yml +++ /dev/null @@ -1,14 +0,0 @@ -remote_theme: jakartaee/jekyll-theme-jakarta-ee - -title: [tck_jsonb_v1_0] -description: [Oracle Technology Compatibility Kit User's Guide for Java API for JSON Binding 1.0 for Technology Licensees, Release 1.0] - -# sidebar links url -links: - source: https://github.com/javaee/tck_jsonb_v1_0 - download: https://github.com/javaee/tck_jsonb_v1_0/releases - #mailinglist: https://javaee.groups.io/g/tck_jsonb_v1_0 - #javadocs: - docs: https://javaee.github.io/tck_jsonb_v1_0 - #faq: - diff --git a/user_guides/jsonb/src/main/jbake/assets/css/style.css b/user_guides/jsonb/src/main/jbake/assets/css/style.css deleted file mode 100644 index 182f7559b6..0000000000 --- a/user_guides/jsonb/src/main/jbake/assets/css/style.css +++ /dev/null @@ -1,313 +0,0 @@ -/* CSS */ -/*! normalize.css v3.0.2 | MIT License | git.io/normalize */ -/** 1. Set default font family to sans-serif. 2. Prevent iOS text size adjust after orientation change, without disabling user zoom. */ -html { font-family: sans-serif; /* 1 */ -ms-text-size-adjust: 100%; /* 2 */ -webkit-text-size-adjust: 100%; /* 2 */ } - -/* HTML5 display definitions ========================================================================== */ -/** Correct `block` display not defined for any HTML5 element in IE 8/9. Correct `block` display not defined for `details` or `summary` in IE 10/11 and Firefox. Correct `block` display not defined for `main` in IE 11. */ -article, aside, details, figcaption, figure, footer, header, hgroup, main, menu, nav, section, summary { display: block; } - -/** 1. Correct `inline-block` display not defined in IE 8/9. 2. Normalize vertical alignment of `progress` in Chrome, Firefox, and Opera. */ -audio, canvas, progress, video { display: inline-block; /* 1 */ vertical-align: baseline; /* 2 */ } - -/** Prevent modern browsers from displaying `audio` without controls. Remove excess height in iOS 5 devices. */ -audio:not([controls]) { display: none; height: 0; } - -/** Address `[hidden]` styling not present in IE 8/9/10. Hide the `template` element in IE 8/9/11, Safari, and Firefox < 22. */ -[hidden], template { display: none; } - -/* Links ========================================================================== */ -/** Remove the gray background color from active links in IE 10. */ -a { background-color: transparent; } - -/** Improve readability when focused and also mouse hovered in all browsers. */ -a:active, a:hover { outline: 0; } - -/* Text-level semantics ========================================================================== */ -/** Address styling not present in IE 8/9/10/11, Safari, and Chrome. */ -abbr[title] { border-bottom: 1px dotted; } - -/** Address style set to `bolder` in Firefox 4+, Safari, and Chrome. */ -b, strong { font-weight: bold; } - -/** Address styling not present in Safari and Chrome. */ -dfn { font-style: italic; } - -/** Address variable `h1` font-size and margin within `section` and `article` contexts in Firefox 4+, Safari, and Chrome. */ -h1 { font-size: 2em; margin: 0.67em 0; } - -/** Address styling not present in IE 8/9. */ -mark { background: #ff0; color: #000; } - -/** Address inconsistent and variable font size in all browsers. */ -small { font-size: 80%; } - -/** Prevent `sub` and `sup` affecting `line-height` in all browsers. */ -sub, sup { font-size: 75%; line-height: 0; position: relative; vertical-align: baseline; } - -sup { top: -0.5em; } - -sub { bottom: -0.25em; } - -/* Embedded content ========================================================================== */ -/** Remove border when inside `a` element in IE 8/9/10. */ -img { border: 0; } - -/** Correct overflow not hidden in IE 9/10/11. */ -svg:not(:root) { overflow: hidden; } - -/* Grouping content ========================================================================== */ -/** Address margin not present in IE 8/9 and Safari. */ -figure { margin: 1em 40px; } - -/** Address differences between Firefox and other browsers. */ -hr { box-sizing: content-box; height: 0; } - -/** Contain overflow in all browsers. */ -pre { overflow: auto; } - -/** Address odd `em`-unit font size rendering in all browsers. */ -code, kbd, pre, samp { font-family: monospace, monospace; font-size: 1em; } - -/* Forms ========================================================================== */ -/** Known limitation: by default, Chrome and Safari on OS X allow very limited styling of `select`, unless a `border` property is set. */ -/** 1. Correct color not being inherited. Known issue: affects color of disabled elements. 2. Correct font properties not being inherited. 3. Address margins set differently in Firefox 4+, Safari, and Chrome. */ -button, input, optgroup, select, textarea { color: inherit; /* 1 */ font: inherit; /* 2 */ margin: 0; /* 3 */ } - -/** Address `overflow` set to `hidden` in IE 8/9/10/11. */ -button { overflow: visible; } - -/** Address inconsistent `text-transform` inheritance for `button` and `select`. All other form control elements do not inherit `text-transform` values. Correct `button` style inheritance in Firefox, IE 8/9/10/11, and Opera. Correct `select` style inheritance in Firefox. */ -button, select { text-transform: none; } - -/** 1. Avoid the WebKit bug in Android 4.0.* where (2) destroys native `audio` and `video` controls. 2. Correct inability to style clickable `input` types in iOS. 3. Improve usability and consistency of cursor style between image-type `input` and others. */ -button, html input[type="button"], input[type="reset"], input[type="submit"] { -webkit-appearance: button; /* 2 */ cursor: pointer; /* 3 */ } - -/** Re-set default cursor for disabled elements. */ -button[disabled], html input[disabled] { cursor: default; } - -/** Remove inner padding and border in Firefox 4+. */ -button::-moz-focus-inner, input::-moz-focus-inner { border: 0; padding: 0; } - -/** Address Firefox 4+ setting `line-height` on `input` using `!important` in the UA stylesheet. */ -input { line-height: normal; } - -/** It's recommended that you don't attempt to style these elements. Firefox's implementation doesn't respect box-sizing, padding, or width. 1. Address box sizing set to `content-box` in IE 8/9/10. 2. Remove excess padding in IE 8/9/10. */ -input[type="checkbox"], input[type="radio"] { box-sizing: border-box; /* 1 */ padding: 0; /* 2 */ } - -/** Fix the cursor style for Chrome's increment/decrement buttons. For certain `font-size` values of the `input`, it causes the cursor style of the decrement button to change from `default` to `text`. */ -input[type="number"]::-webkit-inner-spin-button, input[type="number"]::-webkit-outer-spin-button { height: auto; } - -/** 1. Address `appearance` set to `searchfield` in Safari and Chrome. 2. Address `box-sizing` set to `border-box` in Safari and Chrome (include `-moz` to future-proof). */ -input[type="search"] { -webkit-appearance: textfield; /* 1 */ /* 2 */ box-sizing: content-box; } - -/** Remove inner padding and search cancel button in Safari and Chrome on OS X. Safari (but not Chrome) clips the cancel button when the search input has padding (and `textfield` appearance). */ -input[type="search"]::-webkit-search-cancel-button, input[type="search"]::-webkit-search-decoration { -webkit-appearance: none; } - -/** Define consistent border, margin, and padding. */ -fieldset { border: 1px solid #c0c0c0; margin: 0 2px; padding: 0.35em 0.625em 0.75em; } - -/** 1. Correct `color` not being inherited in IE 8/9/10/11. 2. Remove padding so people aren't caught out if they zero out fieldsets. */ -legend { border: 0; /* 1 */ padding: 0; /* 2 */ } - -/** Remove default vertical scrollbar in IE 8/9/10/11. */ -textarea { overflow: auto; } - -/** Don't inherit the `font-weight` (applied by a rule above). NOTE: the default cannot safely be changed in Chrome and Safari on OS X. */ -optgroup { font-weight: bold; } - -/* Tables ========================================================================== */ -/** Remove most spacing between table cells. */ -table { border-collapse: collapse; border-spacing: 0; } - -td, th { padding: 0; } - -/* LAYOUT STYLES */ - -p { margin-top: 0; } - -code, pre { margin-bottom: 30px; font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; font-size: 13px; color: #222; } - -code { padding: 0 3px; background-color: #f2f8fc; border: solid 1px #dbe7f3; } - -pre { padding: 20px; overflow: auto; text-shadow: none; background: #fff; border: solid 1px #f2f2f2; } - -pre code { padding: 0; color: #2879d0; background-color: #fff; border: none; } - -ul, ol, dl { margin-bottom: 20px; } - -/* COMMON STYLES */ - -td.halign-right { text-align: right; } - -td.halign-center { text-align: center; } - -form { padding: 20px; background: #f2f2f2; } - -h2 { - font-size: 2em; - line-height: 1.2em; - font-weight: 200; - letter-spacing: 0; -} - -h3 { - font-size: 1.4em; - line-height: 1.2em; - font-weight: normal; - letter-spacing: 0; -} - -.sect1 { - margin-left: 4%; - margin-right: 4%; - font: 13px/20px Arial, Helvetica, sans-serif -} - -a:link { - text-decoration: none; - color: #09569d; -} - -#preamble hr{ - margin-left: 0%; - margin-right: 0%; -} - -#preamble .sectionbody table { - font-weight: 200; - margin-left: 4%; - margin-right: 4%; -} - -hr { - margin-bottom: 12px; -} - -table.tableblock.frame-all.grid-all.spread { - font-size: 12px; -} - -code { - font-size:.9em; - border: 1px solid #eaeaea; - background-color: #f6f6f6; - border-radius: 3px; - padding: 1px; - padding-left:2px; - padding-right:2px; -} - -pre.prettyprint.highlight { - border: 1px solid #eaeaea; - background-color: #f6f6f6; - border-radius: 4px; - padding: 8px; - padding-top:4px; - padding-bottom:4px; -} - -.language-oac_no_warn { - font-size:.9em; - color:#222; - background-color: transparent; -} - -#doc-title { - margin-left: 4%; -} - -#top-nav { - margin-left: 4%; - font-size: 12px; -} - -#bottom-nav { - margin-left: 4%; - font-size: 12px; -} - -.vector-font { - color:grey; - font-size: 20px; -} - -#copyright { - padding-top: 10px; - padding-bottom: 4px; - display: table; - margin:0 auto; - color: grey; - font-size: 12px; - vertical-align: middle; -} - -.beta {color: #FF0000} - -/* GENERAL ELEMENT TYPE STYLES */ - -/* #Media Queries -================================================== */ -/* Smaller than standard 960 (devices and browsers) */ -/* Tablet Portrait size to standard 960 (devices and browsers) */ -@media only screen and (min-width: 768px) and (max-width: 959px) { .inner { width: 740px; } - header h1, header h2 { width: 340px; } - header h1 { font-size: 60px; } - header h2 { font-size: 30px; } -} -/* All Mobile Sizes (devices and browser) */ -@media only screen and (max-width: 767px) { .inner { width: 93%; } - header { padding: 20px 0; } - header .inner { position: relative; } - header h1, header h2 { width: 100%; } - header h1 { font-size: 48px; } - header h2 { font-size: 24px; } - header a.button { position: relative; display: inline-block; width: auto; height: auto; padding: 5px 10px; margin-top: 15px; font-size: 13px; line-height: 1; color: #2879d0; text-align: center; background-color: #9ddcff; background-image: none; border-radius: 5px; -moz-border-radius: 5px; -webkit-border-radius: 5px; } - header a.button small { display: inline; font-size: 13px; } -} -/* Mobile Landscape Size to Tablet Portrait (devices and browsers) */ -/* Mobile Portrait Size to Mobile Landscape Size (devices and browsers) */ - -header h1 { padding-top: 14px; font-size: 2em; font-weight: 200; line-height: 1.4; color: #FFFFFF; letter-spacing: 0px; border-bottom: 0px; } - -header h2 { font-size: 1.2em; margin-top: 0; margin-bottom: 0; font-weight: 200; line-height: .8; color: #ec7D11; letter-spacing: 0; } - -//header a.button { background: transparent url(../images/logo.png) 0 0 no-repeat; padding-left: 32px; } - -header a:hover { text-decoration: none; } - -/* Admonition (Note) block */ -.admonitionblock > table { - border: 0; - background: none; - width: 100%; - table-layout: auto; - margin-bottom: 10.5px; -} -.admonitionblock > table td.icon { - text-align: center; - width: 60px; -} -.admonitionblock > table td.icon img { - max-width: none; -} -.admonitionblock > table td.icon .title { - text-transform: uppercase; -} -.admonitionblock > table td.content { - padding-left: 1em; - padding-right: 1em; - border-left: 3px solid #ddd; -} -.admonitionblock > table td.content > :last-child > :last-child { - margin-bottom: 0; -} -.admonitionblock td.icon [class^="fa icon-"]:before { - font-size: 2.5em; - text-shadow: 1px 1px 2px rgba(0, 0, 0, 0.5); - cursor: default; -} -.admonitionblock td.icon .icon-note:before { - content: "\f05a"; - color: #5bc0de; -} diff --git a/user_guides/jsonb/src/main/jbake/assets/img/eclipse_foundation_logo_tiny.png b/user_guides/jsonb/src/main/jbake/assets/img/eclipse_foundation_logo_tiny.png deleted file mode 100644 index ee830aeb9332b27a4b4b16ab4b7b452d3db1b23b..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 3612 zcmV+%4&(8OP)}6qTo5r>1r>2e8xyQrMLX89RqIk)9c`5wb*#8BBG!#o z#8z#rjJDOfOjQ(G?Lt))663gn3xXRF5s=3s5A+du+pmA*M6P+s@0Z^L3Oeu1WL|z* zZtlHjx#xV(xvxM9g^rG92kP%`Ko4MF;4okyP!F^Ki-1|cOF$E_PP2n{x@fDSLaCdf zqxS`d13v{$0cwGEVeV(Z7s6~!UU7kGz`MXwpr{H=7i~GJNoq2HW(S0hek3p&_`cj; z2s{D!z&pUlnjM6R_jd!n4eTbGy{c=9w=#_uCKoh2D29%H888m$Be%x@j{u7_J7_Is z=H*%esL|}8rE7|}GK#f1boB9|qZj3PH+1y9Lr1StpNpR@)lTxfi?$L5%lRb=ll{=q zcj;o-H-l77Jp#C1e!c~qrP;yaG}GKgU(+=@boAc9gTRTvI^ZzP4&Lly@;6VThYOPd zF5Xm3woIeb_tWm>z1EpFH@2OPnS+fTS1yefFyvm~Y~XF+K+O(XRYuE4yH(hBtLyn~ zSp#rAKmOfIK$!kwVHN-p>A=i_JPceN507G2M8u2A@D6#@TBA1%`;2v(4VFBIjS zc6B^z|I)5org4abse1w4fmOhpz*Da02U+b{rcnb_S2*wMg;zx&j*!}Gh!C!m<-!D@ zEsmuV@%Fk3KX^NES=!(&)6gu_I2yPbFftf2S^6^@Xj3NQN?^P)sO}Z^YaTF2&aVY- zQtk~Ez-Om2!m<*09JoWkp`tRjxSv&)X&eLm0oXHZjx5ud3S8xS{s$?{o}yUVytISN zTX$eCa3pYXl}K4npaFPMvx8!WB-07WN@H?AU=r|D7L$ce1zrHIvrMChG68D4YdX=d z&$Id{LjHMhPdV^o>^1regC&gaR%)0S!Mn_?N7DjeGvVy*51 zo(1ZFXMjO9vOYtERezSFv7$Uz3eT=rCrn{-E$}EXBJuq5z(>;N?!eJ{ufo0eC;BhO`2vG*rr)Pt%M^2_{b!^SumcmQL0I+XJ@%`v5-! zR%NY)n~~Z98j;~8c(~PzfOFRoq!>VVvKM-e{sUXO#}V|+z8wc z{Jl(n?f~vCqhRg83h^OUD%Tg*upuF_w1TWtgX{Tuv|rWc{eT}Sw;lv8a6LavI4+^< z`Kv9{I0dM8J-=xSFgd11*Yg`w9LXmv)7S<0oj6N_g|V~c(cVfM?X_>|~ zL>a$bVi{2w-zID5rg|iatXzHCX{6dIraliwM@fs zJ%4TqW^XG;DcU{@?5Pp%PXmUD)-BI50c*>|);$s$->jfCg}B38xkgt3Gjc$YD}me6 z#^ZYarxG@ewoGG)Ab^8`1AxQD5w4bbe-7BO#C$XpRr6#~w-j8U1LAc*@K>N;4n{Wv zdkBn|7cg0&gk#kbyWjma(CBjXF>tNx`CcM&=pewZ=g$*VE`FxFAbb}KANpCQagyu# z|H$~(4T3hdm9apn!cZd>B{L+BJ|T4UIc3)B0uaWIR!--o%`%O51PG}Dj<8H)pzHYy zGBDoGc%_?z0>KtkbJ!v%;%wki*YoEH5>`~#ak zT8TzF<#nUkK||>1w}^z@q1nOuO%Yxt%-+MYR%wDYUuT)d`62{g;>3xGI?(m}*S8Rp z+XV}skpN8EfTkEnkUkexZI%dQ954Vl%Juw4RalkrR3+xJl(x2amdOA$aonug!NZ}W zj|6T8Mwf}Fhg+txx{PPO$o2eB6e)krGL5Hz(-g0@zhxR1x}HB@odC-;4iFS*U&}Pk zOu&mJz2XW&qFfND>-kG64F3v(a_uU=eakdXjI&e;Ix~S3zFOi_11-}yyo4|m#1DGQ z_57AJ(~ZLHvqMLp5jwh|*?}JeD91h8!JB?M$0SVzu1H)v3)r6xK>snohn8ssz#O@D zFtD@o&Sc9p4stzzPRciSuuP*Iv+s00|I$t>LZOo(*%;s<`MozV-!hGvz)V>Rb^=BU z#2eE**Ylq((e6cZl=Gi<2bQFHmT`G6a(<+&)q`@z)wx0w(W+M9J0d7*HK`8#K#rXg z4&6T!j$c)U{b)_GHd$>Il>1ekVYF!YyVfIRa1b-}pJB*I`-z5@DcX39-jsL8@Si?{Dmn? zOd$Pj$!UGoWP07|4~5z7p`*`IB)&}~vb_S6wnb3K18aGzxwQ-E&)+sFYCc>g)D z-1Yo5DQoOhqO@i)XFrlzv`g4fMUwP07K+1Is{%WfYP9sX8F<7pjsMCR`^eu~2{l)W zrD}*16)Efe1i-0atnK7WHH%npqT1{%upz5Ps$A_Hj^Ch()B6Rc`;CsLanjL&7*Xkuy3)D8` z-j0IEwMw5?0WWBF5QdIkNUM>H#}PXES-=OtD=GWSdIQI%c0b^d;yCnl{ii`<|0`hR81_3iCiz? zXFIT7vx8;{PxFrD1fqJg(=zKO=;gqNa?GdW z?u|B)vH?JKVr|(~)}Jisu1AWgYbznC^_m_0k*Jz<98oQGISe}PPY(evR;76M!^KoD z3myGZqMZ&+$WGJEu!T4VmiAPakhiSmUoJ+A&d%$*t0t0Yt@m z4Zw@ZXhD35UPL866T~Up1~@)+^u0F2?$YVvWj~Ox1e4_NBc-5b%?_RcMv34S%VOP? zfaYoLyFydM1AIJm^!LT<9wyGqxQur$73rK8I{JK~eC`6GeM?D36h+Hp4P6pC`WW$A zv$hjyfU9U@6Ywj|4rV7p!oi{)6E!=yLechqM0>1$E!cJ1H_E}o?aBVhx0i&DemU^x z(9zclj=u*{xz#Am4i;vljMeWwAj`|pjn(KP(awq44%SG*;#}Z$G4WRs?YUl+ z7Vv9!@D@=v=OJ)hF{*bhbVK0000/bin/ts.jte -:jtxFileName: /bin/ts.jtx -:TCKPackageName: jakarta-jsonb-tck-2.0.1.zip -// Directory names used in examples in using.adoc. -:sigTestDirectoryExample: /src/com/sun/ts/tests/signaturetest/jsonb -:singleTestDirectoryExample: /src/com/sun/ts/tests/jsonb -:subsetTestDirectoryExample: /src/com/sun/ts/tests/jsonb -// Define this attribute (uncomment it) if the TCK needs the rebuild appendix. -// :rebuild: diff --git a/user_guides/jsonb/src/main/jbake/content/config.adoc b/user_guides/jsonb/src/main/jbake/content/config.adoc deleted file mode 100644 index ff8b8639ff..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/config.adoc +++ /dev/null @@ -1,353 +0,0 @@ -type=page -status=published -title=Setup and Configuration -next=using.html -prev=install.html -~~~~~~ -include::attributes.conf[] -Setup and Configuration -======================= - -[[GBFVV]] - - - -[[setup-and-configuration]] -4 Setup and Configuration -------------------------- - - -[NOTE] -==== -The Jakarta EE Specification process provides for any number of compatible implementations. -As additional implementations become available, refer to project or product documentation from -those vendors for specific TCK setup and operational guidance. - -==== - -This chapter describes how to set up the {TechnologyShortName} TCK and -JavaTest harness software. Before proceeding with the instructions in -this chapter, be sure to install all required software, as described in -link:install.html#GBFTP[Chapter 3, "Installation."] - -After completing the instructions in this chapter, proceed to -link:using.html#GBFWO[Chapter 5, "Executing Tests,"] for instructions on -running the {TechnologyShortName} TCK. - -include::config.inc[] - -[[GHGDH]][[custom-configuration-handlers]] - -4.4 Custom Configuration Handlers -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Configuration handlers are used to configure and unconfigure a -{TechnologyShortName} {TechnologyVersion} implementation during the -certification process. These are similar to deployment handlers but -used for configuration. A configuration handler is an Ant build file -that contains at least the required targets listed below: - - * `config.vi` - to configure the vendor implementation - * `clean.vi` - to unconfigure the vendor implementation - -These targets are called from the `/bin/build.xml` file and -call down into the implementation-specific configuration handlers. - -To provide your own configuration handler, create a config.vi.xml file -with the necessary configuration steps for your implementation and place -the file under the `/bin/xml/impl/` directory. - -For more information, you may wish to view `/bin/xml/impl/glassfish/config.vi.xml`, -the configuration file for Jakarta EE {JakartaEEVersion} Compatible Implementation, Eclipse GlassFish. - -[[GBFWG]][[custom-deployment-handlers]] - -4.5 Custom Deployment Handlers -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Deployment handlers are used to deploy and undeploy the WAR files that -contain the tests to be run during the certification process. A deployment -handler is an Ant build file that contains at least the required targets -listed in the table below. - -The {TechnologyShortName} TCK provides these deployment handlers: - -* `/bin/xml/impl/none/deploy.xml` -* `/bin/xml/impl/glassfish/deploy.xml` -* `/bin/xml/impl/tomcat/deploy.xml` - -The `deploy.xml` files in each of these directories are used to control -deployment to a specific container (no deployment, deployment to -the Eclipse GlassFish Web container, deployment to the Tomcat Web container) -denoted by the name of the directory in which each `deploy.xml` file -resides. The primary `build.xml` file in the `/bin` directory -has a target to invoke any of the required targets (`-deploy`, `-undeploy`, -`-deploy.all`, `-undeploy.all`). - -[[GBFVA]][[create-custom-deployment-handler]] - -4.5.1 To Create a Custom Deployment Handler -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -To deploy tests to another {TechnologyShortName} implementation, you -must create a custom handler. - -1. Create a new directory in the `/bin/xml/impl` directory tree. - For example, create the `/bin/xml/impl/my_deployment_handler` directory. - Replace my_deployment_handler with the value of the impl.vi - property that you set in Step 5 of the configuration procedure - described in Section 4.2, "Configuring Your Environment to Repackage - and Run the TCK Against the Vendor Implementation". - -2. Copy the deploy.xml file from the `/bin/xml/impl/none` - directory to the directory that you created. - -3. Modify the required targets in the `deploy.xml` file. This is what - the `deploy.xml` file for the "none" deployment handler looks like. - -+ -[source,oac_no_warn] ----- - - - - - - - - - - - - - - - ----- -+ -Although this example just echoes messages, it does include the four -required Ant targets (`-deploy`, `-undeploy`, `-deploy.all`, `-undeploy.all`) -that your custom `deploy.xml` file must contain. With this as your -starting point, look at the required targets in the `deploy.xml` files -in the Tomcat and Eclipse Glassfish directories for guidance as you create -the same targets for the Web container in which you will run your -implementation of {TechnologyShortName}. - -The following Ant targets can be called from anywhere under the -`/src` directory: - -* `deploy` -* `undeploy` -* `deploy.all` -* `undeploy.all` - -The `deploy.all` and `undeploy.all` targets can also be called from the -`/bin` directory. - -[NOTE] -======================================================================= -The targets in the `deploy.xml` file are never called directly. -They are called indirectly by the targets listed above. -======================================================================= - -[[GBFUY]][[using-the-javatest-harness-software]] - -4.6 Using the JavaTest Harness Software -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -There are two general ways to run the {TechnologyShortName} TCK test -suite using the JavaTest harness software: - -* Through the JavaTest GUI; if using this method, please continue on to -link:#GBFWG[Section 4.7, "Using the JavaTest Harness Configuration -GUI."] -* In JavaTest batch mode, from the command line in your shell -environment; if using this method, please proceed directly to -link:using.html#GBFWO[Chapter 5, "Executing Tests."] - -[[GBFWG]][[using-the-javatest-harness-configuration-gui]] - -4.7 Using the JavaTest Harness Configuration GUI -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -You can use the JavaTest harness GUI to modify general test settings and -to quickly get started with the default {TechnologyShortName} TCK test -environment. This section covers the following topics: - -* link:#GBFVA[Configuration GUI Overview] -* link:#GBFVD[Starting the Configuration GUI] -* link:#GBFVX[To Configure the JavaTest Harness to Run the -{TechnologyShortName} TCK Tests] -* link:#GBFUU[Modifying the Default Test Configuration] - - -[NOTE] -======================================================================= - -It is only necessary to proceed with this section if you want to run the -JavaTest harness in GUI mode. If you plan to run the JavaTest harness in -command-line mode, skip the remainder of this chapter, and continue with -link:using.html#GBFWO[Chapter 5, "Executing Tests."] - -======================================================================= - - -[[GBFVA]][[configuration-gui-overview]] - -4.7.1 Configuration GUI Overview -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -In order for the JavaTest harness to execute the test suite, it requires -information about how your computing environment is configured. The -JavaTest harness requires two types of configuration information: - -* Test environment: This is data used by the tests. For example, the -path to the Java runtime, how to start the product being tested, network -resources, and other information required by the tests in order to run. -This information does not change frequently and usually stays constant -from test run to test run. -* Test parameters: This is information used by the JavaTest harness to -run the tests. Test parameters are values used by the JavaTest harness -that determine which tests in the test suite are run, how the tests -should be run, and where the test reports are stored. This information -often changes from test run to test run. - -The first time you run the JavaTest harness software, you are asked to -specify the test suite and work directory that you want to use. (These -parameters can be changed later from within the JavaTest harness GUI.) - -Once the JavaTest harness GUI is displayed, whenever you choose Start, -then Run Tests to begin a test run, the JavaTest harness determines -whether all of the required configuration information has been supplied: - -* If the test environment and parameters have been completely -configured, the test run starts immediately. -* If any required configuration information is missing, the -configuration editor displays a series of questions asking you the -necessary information. This is called the configuration interview. When -you have entered the configuration data, you are asked if you wish to -proceed with running the test. - -[[GBFVD]][[starting-the-configuration-gui]] - -4.7.2 Starting the Configuration GUI -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Before you start the JavaTest harness software, you must have a valid -test suite and Java SE {SEversion} installed on your system. - -The {TechnologyShortName} TCK includes an Ant script that is used to execute the -JavaTest harness from the `` directory. Using this Ant script -to start the JavaTest harness is part of the procedure described in -link:#GBFVX[Section 4.7.3, "To Configure the JavaTest Harness to Run the -TCK Tests."] - -When you execute the JavaTest harness software for the first time, the -JavaTest harness displays a Welcome dialog box that guides you through -the initial startup configuration. - -* If it is able to open a test suite, the JavaTest harness displays a -Welcome to JavaTest dialog box that guides you through the process of -either opening an existing work directory or creating a new work -directory as described in the JavaTest online help. -* If the JavaTest harness is unable to open a test suite, it displays a -Welcome to JavaTest dialog box that guides you through the process of -opening both a test suite and a work directory as described in the -JavaTest documentation. - -After you specify a work directory, you can use the Test Manager to -configure and run tests as described in link:#GBFVX[Section 4.7.3, "To -Configure the JavaTest Harness to Run the TCK Tests."] - -[[GBFVX]][[to-configure-the-javatest-harness-to-run-the-tck-tests]] - -4.7.3 To Configure the JavaTest Harness to Run the TCK Tests -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The answers you give to some of the configuration interview questions -are specific to your site. For example, the name of the host on which -the JavaTest harness is running. Other configuration parameters can be -set however you wish. For example, where you want test report files to -be stored. - -Note that you only need to complete all these steps the first time you -start the JavaTest test harness. After you complete these steps, you can -either run all of the tests by completing the steps in -link:using.html#GBFUZ[Section 5.1, "Starting JavaTest,"] or run a subset -of the tests by completing the steps in link:using.html#GBFWM[Section -5.2, "Running a Subset of the Tests."] - -1. Change to the `/bin` directory and start the JavaTest test -harness: + -`cd /bin` + -`ant gui` -2. From the File menu, click *Open Quick Start Wizard*. + -The Welcome screen displays. -3. Select *Start a new test run*, and then click *Next*. + -You are prompted to create a new configuration or use a configuration -template. -4. Select *Create a new configuration*, and then click *Next*. + -You are prompted to select a test suite. -5. Accept the default suite (`/src`), and then click *Next*. + -You are prompted to specify a work directory to use to store your test -results. -6. Type a work directory name or use the *Browse* button to select a work -directory, and then click *Next*. + -You are prompted to start the configuration editor or start a test run. -At this point, the {TechnologyShortName} TCK is configured to run the -default test suite. -7. Deselect the *Start the configuration editor* option, and then click -*Finish*. -8. Click *Run Tests*, then click *Start*. + -The JavaTest harness starts running the tests. -9. To reconfigure the JavaTest test harness, do one of the following: -* Click *Configuration*, then click *New Configuration*. -* Click *Configuration*, then click *Change Configuration*. -10. Click *Report*, and then click *Create Report*. -11. Specify the directory in which the JavaTest test harness will write -the report, and then click *OK*. + -A report is created, and you are asked whether you want to view it. -12. Click *Yes* to view the report. - -[[GBFUU]][[modifying-the-default-test-configuration]] - -4.7.4 Modifying the Default Test Configuration -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The JavaTest GUI enables you to configure numerous test options. These -options are divided into two general dialog box groups: - -* Group 1: Available from the JavaTest *Configure/Change Configuration* -submenus, the following options are displayed in a tabbed dialog box: - -** *Tests to Run* - -** *Exclude List* - -** *Keywords* - -** *Prior Status* - -** *Test Environment* - -** *Concurrency* - -** *Timeout Factor* -* Group 2: Available from the JavaTest *Configure/Change -Configuration/Other Values* submenu, or by pressing `Ctrl+E`, the following -options are displayed in a paged dialog box: - -** *Environment Files* - -** *Test Environment* - -** *Specify Tests to Run* - -** *Specify an Exclude List* - -Note that there is some overlap between the functions in these two -dialog boxes; for those functions use the dialog box that is most -convenient for you. Please refer to the JavaTest Harness documentation -or the online help for complete information about these various options. - - diff --git a/user_guides/jsonb/src/main/jbake/content/config.inc b/user_guides/jsonb/src/main/jbake/content/config.inc deleted file mode 100644 index 615e057763..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/config.inc +++ /dev/null @@ -1,107 +0,0 @@ -/////////////////////////////////////////////////////////////////////// -NOTE TO WRITERS: -The following sections should be customized for the technology. -This text was originally from the JAX-RS TCK. Most references -to JAX-RS have been parameterized to serve as a simple starting -point for customization. There are still many details that will -need to be changed or removed. The major sections 4.1, 4.2, and -4.3 should be preserved. If their titles are changed, the links -at the top of config.adoc will need to be changed as well as well -as toc.adoc. -/////////////////////////////////////////////////////////////////////// - -[[GBFVU]][[configuring-your-environment-to-run-the-tck-against-the-reference-implementation]] - -4.1 Configuring Your Environment to Run the TCK Against the Reference Implementation -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -After configuring your environment as described in this section, -continue with the instructions in link:#GBFUY[Section 4.6, "Using the -JavaTest Harness Software."] - - -[NOTE] -======================================================================= - -In these instructions, variables in angle brackets need to be expanded -for each platform. For example, `` becomes `$TS_HOME` on -Solaris/Linux and `%TS_HOME%` on Windows. In addition, the forward -slashes (`/`) used in all of the examples need to be replaced with -backslashes (`\`) for Windows. Finally, be sure to use the appropriate -separator for your operating system when specifying multiple path -entries (`;` on Windows, `:` on UNIX/Linux). - -On Windows, you must escape any backslashes with an extra backslash in -path separators used in any of the following properties, or use forward -slashes as a path separator instead. - -======================================================================= - - -1. Set the following environment variables in your shell environment: - a. `JAVA_HOME` to the directory in which Java SE 8 or Java SE 11 is installed - b. `TS_HOME` to the directory in which the {TechnologyShortName} TCK - {TechnologyVersion} software is installed - c. `PATH` to include the following directories: `JAVA_HOME/bin`, - +{TechnologyHomeEnv}/bin+, and `ANT_HOME/bin` -2. Copy /bin/ts.jte.jdk11 as /bin/ts.jte if JAVA_HOME is Java SE 11. -Edit your `/bin/ts.jte` file and set the following -environment variables: - a. Set the `jsonb.classes` property to the jar file(s) that contain - the {TechnologyShortName} implementation. + - For example, if you were using the {TechnologyFullName} {TechnologyVersion} RI, you would set - this property to `jsonb.classes=yasson-{TechnologyVersion}.jar`. - b. It is also needed to add all of the runtime dependencies required by the implementation. - Add these dependencies as another entries to the `jsonb.classes` property. Use - proper separator between the entries (`;` on Windows, `:` on UNIX/Linux). - -[[GCLHU]][[configuring-your-environment-to-repackage-and-run-the-tck-against-the-vendor-implementation]] - -4.2 Configuring Your Environment to Repackage and Run the TCK Against the Vendor Implementation -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -After configuring your environment as described in this section, -continue with the instructions in link:#GBFUY[Section 4.4, "Using the -JavaTest Harness Software."] - - -[NOTE] -======================================================================= - -In these instructions, variables in angle brackets need to be expanded -for each platform. For example, `` becomes `$TS_HOME` on -Solaris/Linux and `%TS_HOME%` on Windows. In addition, the forward -slashes (`/`) used in all of the examples need to be replaced with -backslashes (`\`) for Windows. Finally, be sure to use the appropriate -separator for your operating system when specifying multiple path -entries (`;` on Windows, `:` on UNIX/Linux). - -On Windows, you must escape any backslashes with an extra backslash in -path separators used in any of the following properties, or use forward -slashes as a path separator instead. - -======================================================================= - - -1. Set the following environment variables in your shell environment: - a. `JAVA_HOME` to the directory in which Java SE 8 or Java SE 11 is installed - b. `TS_HOME` to the directory in which the {TechnologyShortName} TCK - {TechnologyVersion} software is installed - c. `PATH` to include the following directories: `JAVA_HOME/bin`, - +{TechnologyHomeEnv}/bin+, and `ANT_HOME/bin` -2. Copy /bin/ts.jte.jdk11 as /bin/ts.jte if JAVA_HOME is Java SE 11. -Edit your `/bin/ts.jte` file and set the following -environment variables: - a. Set the `jsonb.classes` property to the jar file(s) that contain - the {TechnologyShortName} implementation. - b. It is also needed to add all of the runtime dependencies required by the implementation. - Add these dependencies as another entries to the `jsonb.classes` property. Use - proper separator between the entries (`;` on Windows, `:` on UNIX/Linux). - - -[[GHGDG]][[publishing-the-test-applications]] - -4.3 Publishing the Test Applications -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Not needed for the {TechnologyShortName} TCK. diff --git a/user_guides/jsonb/src/main/jbake/content/debug-tips.inc b/user_guides/jsonb/src/main/jbake/content/debug-tips.inc deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/user_guides/jsonb/src/main/jbake/content/debug.adoc b/user_guides/jsonb/src/main/jbake/content/debug.adoc deleted file mode 100644 index 5208c401a6..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/debug.adoc +++ /dev/null @@ -1,174 +0,0 @@ -type=page -status=published -title=Debugging Test Problems -next=faq.html -prev=using.html -~~~~~~ -include::attributes.conf[] -Debugging Test Problems -======================= - -[[GBFUV]] - - -[[debugging-test-problems]] -6 Debugging Test Problems -------------------------- - -There are a number of reasons that tests can fail to execute properly. -This chapter provides some approaches for dealing with these failures. -Please note that most of these suggestions are only relevant when -running the test harness in GUI mode. - -This chapter includes the following topics: - -* link:#GBFYP[Overview] -* link:#GBFVF[Test Tree] -* link:#GBFWI[Folder Information] -* link:#GBFVP[Test Information] -* link:#GBFVZ[Report Files] -* link:#GBFYF[Configuration Failures] - -[[GBFYP]][[overview]] - -6.1 Overview -~~~~~~~~~~~~ - -The goal of a test run is for all tests in the test suite that are not -filtered out to have passing results. If the root test suite folder -contains tests with errors or failing results, you must troubleshoot and -correct the cause to satisfactorily complete the test run. - -* Errors: Tests with errors could not be executed by the JavaTest -harness. These errors usually occur because the test environment is not -properly configured. -* Failures: Tests that fail were executed but had failing results. - -The Test Manager GUI provides you with a number of tools for effectively -troubleshooting a test run. See the JavaTest User's Guide and JavaTest -online help for detailed descriptions of the tools described in this -chapter. Ant test execution tasks provide command-line users with -immediate test execution feedback to the display. Available JTR report -files and log files can also help command-line users troubleshoot test -run problems. - -For every test run, the JavaTest harness creates a set of report files -in the reports directory, which you specified by setting the -`report.dir` property in the +{jteFileName}+ file. The report files contain -information about the test description, environment, messages, -properties used by the test, status of the test, and test result. After -a test run is completed, the JavaTest harness writes HTML reports for -the test run. You can view these files in the JavaTest ReportBrowser -when running in GUI mode, or in the Web browser of your choice outside -the JavaTest interface. To see all of the HTML report files, enter the -URL of the `report.html` file. This file is the root file that links to -all of the other HTML reports. - -The JavaTest harness also creates a `summary.txt` file in the report -directory that you can open in any text editor. The `summary.txt` file -contains a list of all tests that were run, their test results, and -their status messages. - -The work directory, which you specified by setting the `work.dir` -property in the +{jteFileName}+ file, contains several files that were -deposited there during test execution: `harness.trace`, `log.txt`, -`lastRun.txt`, and `testsuite`. Most of these files provide information -about the harness and environment in which the tests were executed. - -[NOTE] -======================================================================= - -You can set `harness.log.traceflag=true` in +{jteFileName}+ to -get more debugging information. - -======================================================================= - -If a large number of tests failed, you should read -link:#GBFYF[Configuration Failures] to see if a -configuration issue is the cause of the failures. - - -[[GBFVF]][[test-tree]] - -6.2 Test Tree -~~~~~~~~~~~~~ - -Use the test tree in the JavaTest GUI to identify specific folders and -tests that had errors or failing results. Color codes are used to -indicate status as follows: - -* Green: Passed -* Blue: Test Error -* Red: Failed to pass test -* White: Test not run -* Gray: Test filtered out (not run) - -[[GBFWI]][[folder-information]] - -6.3 Folder Information -~~~~~~~~~~~~~~~~~~~~~~ - -Click a folder in the test tree in the JavaTest GUI to display its tabs. - -Choose the Error and the Failed tabs to view the lists of all tests in -and under a folder that were not successfully run. You can double-click -a test in the lists to view its test information. - -[[GBFVP]][[test-information]] - -6.4 Test Information -~~~~~~~~~~~~~~~~~~~~ - -To display information about a test in the JavaTest GUI, click its icon -in the test tree or double-click its name in a folder status tab. The -tab contains detailed information about the test run and, at the bottom -of the window, a brief status message identifying the type of failure or -error. This message may be sufficient for you to identify the cause of -the error or failure. - -If you need more information to identify the cause of the error or -failure, use the following tabs listed in order of importance: - -* Test Run Messages contains a Message list and a Message section that -display the messages produced during the test run. -* Test Run Details contains a two-column table of name/value pairs -recorded when the test was run. -* Configuration contains a two-column table of the test environment -name/value pairs derived from the configuration data actually used to -run the test. - - -[NOTE] -======================================================================= - -You can set `harness.log.traceflag=true` in +{jteFileName}+ to -get more debugging information. - -======================================================================= - - -[[GBFVZ]][[report-files]] - -6.5 Report Files -~~~~~~~~~~~~~~~~ - -Report files are another good source of troubleshooting information. You -may view the individual test results of a batch run in the JavaTest -Summary window, but there are also a wide range of HTML report files -that you can view in the JavaTest ReportBrowser or in the external -browser or your choice following a test run. See -link:using.html#GBFVK[Section 5.5, "Test Reports,"] for more information. - -[[GBFYF]][[configuration-failures]] - -6.6 Configuration Failures -~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Configuration failures are easily recognized because many tests fail the -same way. When all your tests begin to fail, you may want to stop the -run immediately and start viewing individual test output. However, in -the case of full-scale launching problems where no tests are actually -processed, report files are usually not created (though sometimes a -small `harness.trace` file in the report directory is written). - -include::debug-tips.inc[] diff --git a/user_guides/jsonb/src/main/jbake/content/defns.inc b/user_guides/jsonb/src/main/jbake/content/defns.inc deleted file mode 100644 index 038db2dda3..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/defns.inc +++ /dev/null @@ -1,46 +0,0 @@ -// NOTE TO WRITERS: -// Most technologies will only need the compatibility rules in rules.adoc. -// Some technologies will need additional definitions to go with additional -// rules. If they're needed, remove the comment characters below -// and update the definitions as appropriate. -// -// The first block below is additional definitions needed by -// Jakarta XML Web Services. -// -// The second block below is additional defintions needed by -// Jakarta Server Pages. -// -// NOTE: This set of examples is NOT complete, but should be. -// -// -// Jakarta XML Web Services -// -// |Development Kit |A software product that implements or incorporates a -// Compiler, a Schema Compiler, a Schema Generator, a Java-to-WSDL Tool, a -// WSDL-to-Java Tool, and/or an RMI Compiler. -// -// |Java-to-WSDL Output |Output of a Java-to-WSDL Tool that is required for -// Web service deployment and invocation. -// -// |Java-to-WSDL Tool |A software development tool that implements or -// incorporates a function that generates web service endpoint descriptions -// in WSDL and XML schema format from Source Code as specified by the -// Jakarta XML Web Services Specification. -// -// |WSDL-to-Java Output |Output of a WSDL-to-Java tool that is required for -// Web service deployment and invocation. -// -// |WSDL-to-Java Tool |A software development tool that implements or -// incorporates a function that generates web service interfaces for -// clients and endpoints from a WSDL description as specified by the -// Jakarta XML Web Services Specification. -// -// -// Jakarta Server Pages -// -// |Jakarta Server Page |A text-based document that uses Jakarta Server -// Pages technology. -// -// |Jakarta Server Page Implementation Class |A program constructed by -// transforming the Jakarta Server Page text into a Java language program -// using the transformation rules described in the Specifications. diff --git a/user_guides/jsonb/src/main/jbake/content/faq.adoc b/user_guides/jsonb/src/main/jbake/content/faq.adoc deleted file mode 100644 index 97ca394c55..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/faq.adoc +++ /dev/null @@ -1,62 +0,0 @@ -type=page -status=published -title=Appendix A: Frequently Asked Questions -next=rebuild.html -prev=debug.html -~~~~~~ -include::attributes.conf[] -Appendix A: Frequently Asked Questions -====================================== - -[[GBFYD]] - - -[[a-frequently-asked-questions]] -A Frequently Asked Questions ----------------------------- - -This appendix contains the following questions. - -* link:#GBFYQ[Where do I start to debug a test failure?] -* link:#GBFYR[How do I restart a crashed test run?] -* link:#GBFWU[What would cause tests be added to the exclude list?] - -[[GBFYQ]][[a.1-where-do-i-start-to-debug-a-test-failure]] - -A.1 Where do I start to debug a test failure? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -From the JavaTest GUI, you can view recently run tests using the Test -Results Summary, by selecting the red Failed tab or the blue Error tab. -See link:debug.html#GBFUV[Chapter 6, "Debugging Test Problems,"] for more -information. - -[[GBFYR]][[a.2-how-do-i-restart-a-crashed-test-run]] - -A.2 How do I restart a crashed test run? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -If you need to restart a test run, you can figure out which test crashed -the test suite by looking at the `harness.trace` file. The -`harness.trace` file is in the report directory that you supplied to the -JavaTest GUI or parameter file. Examine this trace file, then change the -JavaTest GUI initial files to that location or to a directory location -below that file, and restart. This will overwrite only `.jtr` files that -you rerun. As long as you do not change the value of the GUI work -directory, you can continue testing and then later compile a complete -report to include results from all such partial runs. - -[[GBFWU]][[a.3-what-would-cause-tests-be-added-to-the-exclude-list]] - -A.3 What would cause tests be added to the exclude list? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The JavaTest exclude file (+{jtxFileName}+) contains all tests that are not -required to be run. The following is a list of reasons for a test to be -included in the Exclude List: - -* An error in a Compatible Implementation that does not allow the test to -execute properly has been discovered. -* An error in the specification that was used as the basis of the test -has been discovered. -* An error in the test has been discovered. diff --git a/user_guides/jsonb/src/main/jbake/content/install-server-vi.inc b/user_guides/jsonb/src/main/jbake/content/install-server-vi.inc deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/user_guides/jsonb/src/main/jbake/content/install-server.inc b/user_guides/jsonb/src/main/jbake/content/install-server.inc deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/user_guides/jsonb/src/main/jbake/content/install.adoc b/user_guides/jsonb/src/main/jbake/content/install.adoc deleted file mode 100644 index a3b93e73ac..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/install.adoc +++ /dev/null @@ -1,86 +0,0 @@ -type=page -status=published -title=Installation -next=config.html -prev=rules.html -~~~~~~ -include::attributes.conf[] -Installation -============ - -[[GBFTP]] - - -[[installation]] -3 Installation --------------- - -This chapter explains how to install the {TechnologyFullName} TCK software. - -After installing the software according to the instructions in this -chapter, proceed to link:config.html#GBFVV[Chapter 4, "Setup and -Configuration,"] for instructions on configuring your test environment. - -[[GBFUD]][[obtaining-the-reference-implementation]] - -3.1 Obtaining a Compatible Implementation -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Each compatible implementation (CI) will provide instructions for obtaining -their implementation. -{TechnologyRI} is a compatible implementation which may be obtained -from {TechnologyRIURL} - -[[GBFTS]][[installing-the-software]] - -3.2 Installing the Software -~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Before you can run the {TechnologyShortName} TCK tests, you must -install and set up the following software components: - -include::req-software.inc[] -* Java SE {SEversion} -* Apache Ant {AntVersion} -* A CI for {TechnologyShortName} {TechnologyVersion}, one example is {TechnologyRI} -* {TechnologyShortName} TCK version {TechnologyVersion}, which includes: -include::tck-packages.inc[] -* The {TechnologyShortName} {TechnologyVersion} Vendor Implementation (VI) - -Follow these steps: - -. Install the Java SE {SEversion} software, if it is not already installed. + -Download and install the Java SE {SEversion} software from -http://www.oracle.com/technetwork/java/javase/downloads/index.html. -Refer to the installation instructions that accompany the software for -additional information. -. Install the Apache Ant {AntVersion} software, if it is not already installed. + -Download and install Apache Ant {AntVersion} software from Apache Ant -Project. For complete information about Ant, refer to the extensive documentation -on the Apache Ant Project site. The Apache Ant Manual is available at -`http://ant.apache.org/manual/index.html`. -Apache Ant is protected under the Apache Software, License 2.0, which is -is available on the Apache Ant Project license page at -`http://ant.apache.org/license.html`. -. Install the {TechnologyShortName} TCK {TechnologyVersion} software. - a. Copy or download the {TechnologyShortName} TCK software to your - local system. + - You can obtain the {TechnologyShortName} TCK software from the - Jakarta EE site {SpecificationURL}. - b. Use the `unzip` command to extract the bundle in the directory of - your choice: + - +unzip {TCKPackageName}+ + - This creates the TCK directory. The TCK is the test suite home, - ``. -include::install-server.inc[] -. Install a {TechnologyShortName} {TechnologyVersion} Compatible -Implementation. + -A Compatible Implementation is used to validate your initial -configuration and setup of the {TechnologyShortName} TCK -{TechnologyVersion} tests, which are explained further in -link:config.html#GBFVV[Chapter 4, "Setup and Configuration."] + -The Compatible Implementations for {TechnologyShortName} are listed on -the Jakarta EE Specifications web site: {SpecificationURL}. -include::install-server-vi.inc[] -. Install the {TechnologyShortName} VI to be tested. + -Follow the installation instructions for the particular VI under test. diff --git a/user_guides/jsonb/src/main/jbake/content/intro.adoc b/user_guides/jsonb/src/main/jbake/content/intro.adoc deleted file mode 100644 index 774adfd371..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/intro.adoc +++ /dev/null @@ -1,349 +0,0 @@ -type=page -status=published -title=Introduction -next=rules.html -prev=preface.html -~~~~~~ -include::attributes.conf[] -Introduction -============ - -[[GBFOW]] - - -[[introduction]] -1 Introduction --------------- - -This chapter provides an overview of the principles that apply -generally to all Technology Compatibility Kits (TCKs) and describes the -{TechnologyFullName} TCK ({TechnologyShortName} {TechnologyVersion} TCK). -It also includes a high level listing -of what is needed to get up and running with the {TechnologyShortName} -TCK. - -This chapter includes the following topics: - -* link:#GBFTK[Compatibility Testing] -* link:#GBFQR[About the TCK] -* link:#GBFQW[Getting Started With the TCK] - -[[GBFTK]][[compatibility-testing]] - -1.1 Compatibility Testing -~~~~~~~~~~~~~~~~~~~~~~~~~ - -Compatibility testing differs from traditional product testing in a -number of ways. The focus of compatibility testing is to test those -features and areas of an implementation that are likely to differ across -other implementations, such as those features that: - -* Rely on hardware or operating system-specific behavior -* Are difficult to port -* Mask or abstract hardware or operating system behavior - -Compatibility test development for a given feature relies on a complete -specification and compatible implementation (CI) for that feature. -Compatibility testing is not primarily concerned with robustness, -performance, nor ease of use. - -[[GBFQN]][[why-compatibility-testing-is-important]] - -1.1.1 Why Compatibility Testing is Important -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Jakarta platform compatibility is important to different groups involved -with Jakarta technologies for different reasons: - -* Compatibility testing ensures that the Jakarta platform does not become -fragmented as it is ported to different operating systems and hardware -environments. -* Compatibility testing benefits developers working in the Jakarta -programming language, allowing them to write applications once and then -to deploy them across heterogeneous computing environments without -porting. -* Compatibility testing allows application users to obtain applications -from disparate sources and deploy them with confidence. -* Conformance testing benefits Jakarta platform implementors by ensuring a -level playing field for all Jakarta platform ports. - -[[GBFPR]][[tck-compatibility-rules]] - -1.1.2 TCK Compatibility Rules -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Compatibility criteria for all technology implementations are embodied -in the TCK Compatibility Rules that apply to a specified technology. -Each TCK tests for adherence to these Rules as described in -link:rules.html#GBFSN[Chapter 2, "Procedure for Certification."] - -[[GBFPW]][[tck-overview]] - -1.1.3 TCK Overview -^^^^^^^^^^^^^^^^^^ - -A TCK is a set of tools and tests used to verify that a vendor's compatible -implementation of a Jakarta EE technology conforms to the applicable -specification. All tests in the TCK are based on the written -specifications for the Jakarta EE platform. A TCK tests compatibility of a -vendor's compatible implementation of the technology to the applicable -specification of the technology. Compatibility testing is a means of -ensuring correctness, completeness, and consistency across all -implementations developed by technology licensees. - -The set of tests included with each TCK is called the test suite. Most -tests in a TCK's test suite are self-checking, but some tests may -require tester interaction. Most tests return either a Pass or Fail -status. For a given platform to be certified, all of the required tests -must pass. The definition of required tests may change from platform to -platform. - -The definition of required tests will change over time. Before your -final certification test pass, be sure to download the latest version -of this TCK. - -[[GBFPB]][[java-community-process-jcp-program-and-compatibility-testing]] - -1.1.4 Jakarta EE Specification Process (JESP) Program and Compatibility Testing -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The Jakarta EE Specification Process (JESP) program is the formalization of the -open process that has been used since 2019 to develop and revise Jakarta EE -technology specifications in cooperation with the international Jakarta EE -community. The JESP program specifies that the following three major -components must be included as deliverables in a final Jakarta EE technology -release under the direction of the responsible Expert Group: - -* Technology Specification -* Compatible Implementation (CI) -* Technology Compatibility Kit (TCK) - -For further information about the JESP program, go to Jakarta EE Specification -Process community page https://jakarta.ee/specifications. - -[[GBFQR]][[about-the-tck]] - -1.2 About the TCK -~~~~~~~~~~~~~~~~~ - -The {TechnologyShortName} TCK {TechnologyVersion} is designed as a -portable, configurable, automated test suite for verifying the -compatibility of a vendor's implementation of the -{TechnologyShortName} {TechnologyVersion} Specification. - -[[GBFQV]][[tck-specifications-and-requirements]] - -1.2.1 TCK Specifications and Requirements -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -This section lists the applicable requirements and specifications. - -* Specification Requirements: Software requirements for a -{TechnologyShortName} implementation are described in detail in the -{TechnologyShortName} {TechnologyVersion} Specification. Links to the -{TechnologyShortName} specification and other product information can -be found at {SpecificationURL}. -* {TechnologyShortName} Version: The {TechnologyShortName} {TechnologyVersion} TCK -is based on the {TechnologyShortName} -Specification, Version {TechnologyVersion}. -* Compatible Implementation: One {TechnologyShortName} -{TechnologyVersion} Compatible Implementation, {TechnologyRI} is -available from the Eclipse EE4J project -(https://projects.eclipse.org/projects/ee4j). See the CI documentation page at -{TechnologyRIURL} for more information. - -See the {TechnologyShortName} TCK Release Notes for more specific -information about Java SE version requirements, supported platforms, -restrictions, and so on. - -[[GBFSQ]][[tck-components]] - -1.2.2 TCK Components -^^^^^^^^^^^^^^^^^^^^ - -The {TechnologyShortName} TCK {TechnologyVersion} includes the -following components: - -* JavaTest harness version {JavaTestVersion} and related documentation. See -link:https://wiki.openjdk.java.net/display/CodeTools/JT+Harness[JT Harness web site] -for additional information. -* {TechnologyShortName} TCK signature tests; check that all public APIs -are supported and/or defined as specified in the {TechnologyShortName} -Version {TechnologyVersion} implementation under test. -* If applicable, an exclude list, which provides a list of tests that your -implementation is not required to pass. -ifndef::no-api-tests[] -* API tests for all of the {TechnologyShortName} API in all related packages: -include::packages.inc[] -endif::no-api-tests[] -ifdef::end-to-end-tests[] -* End-to-end tests that demonstrate compliance with the {TechnologyFullName} -Specification. -endif::end-to-end-tests[] - -The {TechnologyShortName} TCK tests run on the following platforms: - -include::platforms.inc[] - -[[GBFSA]][[javatest-harness]] - -1.2.3 JavaTest Harness -^^^^^^^^^^^^^^^^^^^^^^ - -The JavaTest harness version {JavaTestVersion} is a set of tools -designed to run and manage test suites on different Java platforms. -To JavaTest, Jakarta EE can be considered another platform. -The JavaTest harness can be described as both a Java application and a set -of compatibility testing tools. It can run tests on different kinds of -Java platforms and it allows the results to be browsed online within -the JavaTest GUI, or offline in the HTML reports that the JavaTest -harness generates. - -The JavaTest harness includes the applications and tools that are used -for test execution and test suite management. It supports the following -features: - -* Sequencing of tests, allowing them to be loaded and executed automatically -* Graphic user interface (GUI) for ease of use -* Automated reporting capability to minimize manual errors -* Failure analysis -* Test result auditing and auditable test specification framework -* Distributed testing environment support - -To run tests using the JavaTest harness, you specify which tests in the -test suite to run, how to run them, and where to put the results as -described in link:config.html#GBFVV[Chapter 4, "Setup and -Configuration."] - -[[GBFRA]][[tck-compatibility-test-suite]] - -1.2.4 TCK Compatibility Test Suite -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The test suite is the collection of tests used by the JavaTest harness -to test a particular technology implementation. In this case, it is the -collection of tests used by the {TechnologyShortName} TCK -{TechnologyVersion} to test a {TechnologyShortName} {TechnologyVersion} -implementation. The tests are designed to verify that a vendor's -runtime implementation of the technology complies with the appropriate -specification. The individual tests correspond to assertions of the -specification. - -The tests that make up the TCK compatibility test suite are precompiled -and indexed within the TCK test directory structure. When a test run is -started, the JavaTest harness scans through the set of tests that are -located under the directories that have been selected. While scanning, -the JavaTest harness selects the appropriate tests according to any -matches with the filters you are using and queues them up for execution. - -[[GBFSH]][[exclude-lists]] - -1.2.5 Exclude Lists -^^^^^^^^^^^^^^^^^^^ - -Each version of a TCK includes an Exclude List contained in a `.jtx` -file. -This is a list of test file URLs that identify tests which do not -have to be run for the specific version of the TCK being used. -Whenever tests are run, the JavaTest harness automatically excludes -any test on the Exclude List from being executed. - -A vendor's compatible implementation is not required to pass or run any test on the Exclude List. -The Exclude List file, +{jtxFileName}+, is included in the -{TechnologyShortName} TCK. - - -[NOTE] -======================================================================= - -From time to time, updates to the Exclude List are made available. -The exclude list is included in the Jakarta TCK ZIP archive. -Each time an update is approved and released, the version number -will be incremented. -You should always make sure you are using an up-to-date copy of the -Exclude List before running the {TechnologyShortName} TCK to verify your -implementation. - -======================================================================= - - -A test might be in the Exclude List for reasons such as: - -* An error in an underlying implementation API has been discovered which -does not allow the test to execute properly. -* An error in the specification that was used as the basis of the test -has been discovered. -* An error in the test itself has been discovered. -* The test fails due to a bug in the tools (such as the JavaTest -harness, for example). - -In addition, all tests are run against the compatible implementations. -Any tests that fail when run on a compatible Jakarta platform are put on the -Exclude List. Any test that is not specification-based, or for which the -specification is vague, may be excluded. Any test that is found to be -implementation dependent (based on a particular thread scheduling model, -based on a particular file system behavior, and so on) may be excluded. - - -[NOTE] -======================================================================= - -Vendors are not permitted to alter or modify Exclude Lists. Changes to -an Exclude List can only be made by using the procedure described in -link:rules.html#CJAJEAEI[Section 2.3.1, "TCK Test Appeals Steps."] - -======================================================================= - - -[[GBFRR]][[tck-configuration]] - -1.2.6 TCK Configuration -^^^^^^^^^^^^^^^^^^^^^^^ - -You need to set several variables in your test environment, modify -properties in the +{jteFileName}+ file, and then use the JavaTest -harness to configure and run the {TechnologyShortName} tests, as described in -link:config.html#GBFVV[Chapter 4, "Setup and Configuration."] - -include::intro.inc[] - -[[GBFQW]][[getting-started-with-the-tck]] - -[NOTE] -==== -The Jakarta EE Specification Process support multiple compatible implementations. -These instructions explain how to get started with the {TechnologyRI} CI. -If you are using another compatible implementation, refer to material provided -by that implementation for specific instructions and procedures. - -==== - -1.3 Getting Started With the TCK -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -This section provides an general overview of what needs to be done to -install, set up, test, and use the {TechnologyShortName} TCK. These -steps are explained in more detail in subsequent chapters of this -guide. - -1. Make sure that the following software has been correctly installed -on the system hosting the JavaTest harness: -include::req-software.inc[] -* Java SE {SEversion} -* Apache Ant {AntVersion} -* A CI for {TechnologyShortName} {TechnologyVersion}. One example is {TechnologyRI}. -* {TechnologyShortName} TCK version {TechnologyVersion}, which includes: -include::tck-packages.inc[] -* The {TechnologyShortName} {TechnologyVersion} Vendor Implementation (VI) + -See the documentation for each of these software applications for -installation instructions. See link:install.html#GBFTP[Chapter 3, -"Installation,"] for instructions on installing the {TechnologyShortName} TCK. -2. Set up the {TechnologyShortName} TCK software. + -See link:config.html#GBFVV[Chapter 4, "Setup and Configuration,"] for -details about the following steps. - a. Set up your shell environment. - b. Modify the required properties in the +{jteFileName}+ file. - c. Configure the JavaTest harness. -3. Test the {TechnologyShortName} {TechnologyVersion} implementation. + -Test the {TechnologyShortName} implementation installation by running -the test suite. See link:using.html#GBFWO[Chapter 5, "Executing Tests."] diff --git a/user_guides/jsonb/src/main/jbake/content/intro.inc b/user_guides/jsonb/src/main/jbake/content/intro.inc deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/user_guides/jsonb/src/main/jbake/content/packages.inc b/user_guides/jsonb/src/main/jbake/content/packages.inc deleted file mode 100644 index 0e15a8284c..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/packages.inc +++ /dev/null @@ -1,11 +0,0 @@ -** `jakarta.json.bind` - -** `jakarta.json.bind.adapter` - -** `jakarta.json.bind.annotation` - -** `jakarta.json.bind.config` - -** `jakarta.json.bind.serializer` - -** `jakarta.json.bind.spi` diff --git a/user_guides/jsonb/src/main/jbake/content/platforms.inc b/user_guides/jsonb/src/main/jbake/content/platforms.inc deleted file mode 100644 index 236beed78f..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/platforms.inc +++ /dev/null @@ -1 +0,0 @@ -* CentOS Linux 7 \ No newline at end of file diff --git a/user_guides/jsonb/src/main/jbake/content/preface.adoc b/user_guides/jsonb/src/main/jbake/content/preface.adoc deleted file mode 100644 index ea10c28728..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/preface.adoc +++ /dev/null @@ -1,147 +0,0 @@ -type=page -status=published -title=Preface -next=intro.html -prev=title.html -~~~~~~ -include::attributes.conf[] -Preface -======= - -[[TCJRS00001]][[GBFTI]] - - -[[preface]] -Preface -------- - -This guide describes how to install, configure, and run the Technology -Compatibility Kit (TCK) that is used to test the {TechnologyFullName} -({TechnologyShortName} {TechnologyVersion}) technology. - -The {TechnologyShortName} TCK is a portable, configurable automated -test suite for verifying the compatibility of a vendor's -implementation of the {TechnologyShortName} {TechnologyVersion} -Specification (hereafter referred to as the vendor implementation or VI). -The {TechnologyShortName} TCK uses the JavaTest harness version -{JavaTestVersion} to run the test suite - - -[NOTE] -======================================================================= - -Note All references to specific Web URLs are given for the sake of your -convenience in locating the resources quickly. These references are -always subject to changes that are in many cases beyond the control of -the authors of this guide. - -======================================================================= - -Jakarta EE is a community sponsored and community run program. -Organizations contribute, along side individual contributors who use, evolve -and assist others. -Commercial support is not available through the Eclipse Foundation resources. -Please refer to the Eclipse EE4J project site -(https://projects.eclipse.org/projects/ee4j). -There, you will find additional details as well as a list of all the associated sub-projects -(Implementations and APIs), that make up Jakarta EE and define these specifications. -If you have questions about this Specification you may -send inquiries to {SpecificationInquiryList}. -If you have questions about this TCK, you may send inquiries to -{TCKInquiryList}. - -[[TCJRS00034]][[GBFUS]] - - -[[who-should-use-this-book]] -Who Should Use This Book -~~~~~~~~~~~~~~~~~~~~~~~~ - -This guide is for vendors that implement the {TechnologyShortName} -{TechnologyVersion} technology to assist them in running the test suite -that verifies compatibility of their implementation of the -{TechnologyShortName} {TechnologyVersion} Specification. - - -[[TCJRS00035]][[GBFPO]] - - -[[before-you-read-this-book]] -Before You Read This Book -~~~~~~~~~~~~~~~~~~~~~~~~~ - -You should be familiar with the {TechnologyShortName} -{TechnologyVersion}, version {TechnologyVersion} Specification, -which can be found at {SpecificationURL}. - -Before running the tests in the {TechnologyShortName} TCK, you should -familiarize yourself with the JavaTest documentation which can be -accessed at the -link:https://wiki.openjdk.java.net/display/CodeTools/JT+Harness[JT Harness web site]. - -[[TCJRS00036]][[GBFWF]] - - -[[typographic-conventions]] -Typographic Conventions -~~~~~~~~~~~~~~~~~~~~~~~ - -The following table describes the typographic conventions that are used -in this book. - -[width="100%",cols="15%,40%,45%",options="header",] -|======================================================================= -|Convention |Meaning |Example -|*Boldface* |Boldface type indicates graphical user interface elements -associated with an action, terms defined in text, or what you type, -contrasted with onscreen computer output. a| -From the *File* menu, select *Open Project*. - -A *cache* is a copy that is stored locally. - -`machine_name% *su*` + -`Password:` - -|`Monospace` |Monospace type indicates the names of files and -directories, commands within a paragraph, URLs, code in examples, text -that appears on the screen, or text that you enter. a| -Edit your `.login` file. - -Use `ls` `-a` to list all files. - -`machine_name% you have mail.` - -|_Italic_ |Italic type indicates book titles, emphasis, or placeholder -variables for which you supply particular values. a| -Read Chapter 6 in the _User's Guide_. - -Do _not_ save the file. - -The command to remove a file is `rm` _filename_. - -|======================================================================= - - -[[TCJRS00037]][[FWBSD]] - - -[[shell-prompts-in-command-examples]] -Shell Prompts in Command Examples -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The following table shows the default UNIX system prompt and superuser -prompt for the C shell, Bourne shell, and Korn shell. - -[width="100%",cols="50%,50%",options="header",] -|===================================================== -|Shell |Prompt -|C shell |`machine_name%` -|C shell for superuser |`machine_name#` -|Bourne shell and Korn shell |`$` + -|Bourne shell and Korn shell for superuser |`#` + -|Bash shell |`shell_name-shell_version$` -|Bash shell for superuser |`shell_name-shell_version#` -|===================================================== - - - diff --git a/user_guides/jsonb/src/main/jbake/content/rebuild.adoc b/user_guides/jsonb/src/main/jbake/content/rebuild.adoc deleted file mode 100644 index e4021cfa19..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/rebuild.adoc +++ /dev/null @@ -1,20 +0,0 @@ -type=page -status=published -title=Appendix B: Rebuild Rules -prev=faq.html -~~~~~~ -include::attributes.conf[] - -Appendix B: Rebuild Rules -========================= - - -ifdef::rebuild[] -include::rebuild.inc[] -endif::rebuild[] -ifndef::rebuild[] - -<<< -Appendix B is not used for the {TechnologyShortName} TCK. - -endif::rebuild[] diff --git a/user_guides/jsonb/src/main/jbake/content/rebuild.inc b/user_guides/jsonb/src/main/jbake/content/rebuild.inc deleted file mode 100644 index f7b9651b26..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/rebuild.inc +++ /dev/null @@ -1,8 +0,0 @@ -/////////////////////////////////////////////////////////////////////// -NOTE TO WRITERS: -The following sections should be customized for the technology. -See the JAXRS User Guide for an example of this file. -/////////////////////////////////////////////////////////////////////// - -[[GCLIZ]] - diff --git a/user_guides/jsonb/src/main/jbake/content/req-software.inc b/user_guides/jsonb/src/main/jbake/content/req-software.inc deleted file mode 100644 index 48014f56ee..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/req-software.inc +++ /dev/null @@ -1,10 +0,0 @@ -/////////////////////////////////////////////////////////////////////// -NOTE TO WRITERS: -This is a list of software required in addition to the TCK and the RI. -For many Java EE APIs, the Java EE RI will be required, as described below. -For standalone technologies, no other software may be required, and the -below line can be removed. - -This is used in intro.adoc in section 1.3 and install.adoc in section 3.2. -/////////////////////////////////////////////////////////////////////// - diff --git a/user_guides/jsonb/src/main/jbake/content/rules.adoc b/user_guides/jsonb/src/main/jbake/content/rules.adoc deleted file mode 100644 index f6b08cebb9..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/rules.adoc +++ /dev/null @@ -1,403 +0,0 @@ -type=page -status=published -title=Procedure for Certification -next=install.html -prev=intro.html -~~~~~~ -include::attributes.conf[] -Procedure for Certification -=========================== - -[[GBFSN]] - - -[[procedure-for-certification]] -2 Procedure for Certification ------------------------------ - -This chapter describes the compatibility testing procedure and -compatibility requirements for {TechnologyFullName}. -This chapter contains the following sections: - -* link:#CJAFFDGI[Certification Overview] -* link:#CJAFGIGG[Compatibility Requirements] -* link:#CJAIIBDJ[Test Appeals Process] -* link:#CJAJECIE[Specifications for {TechnologyFullName}] -* link:#CJABAHGI[Libraries for {TechnologyFullName}] - -[[CJAFFDGI]][[certification-overview]] - -2.1 Certification Overview -~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The certification process for {technologyShortName} {TechnologyVersion} -consists of the following activities: - -* Install the appropriate version of the Technology Compatibility Kit -(TCK) and execute it in accordance with the instructions in this User's -Guide. -* Ensure that you meet the requirements outlined in -link:#CJAFGIGG[Compatibility Requirements] below. -* Certify to the Eclipse Foundation that you have finished -testing and that you meet all of the compatibility requirements, -as required by the Eclipse Foundation TCK License. - -[[CJAFGIGG]][[compatibility-requirements]] - -2.2 Compatibility Requirements -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The compatibility requirements for {TechnologyShortName} -{TechnologyVersion} consist of meeting the requirements set forth by -the rules and associated definitions contained in this section. - -[[sthref4]][[definitions]] - -2.2.1 Definitions -^^^^^^^^^^^^^^^^^ - -These definitions are for use only with these compatibility requirements -and are not intended for any other purpose. - -[[sthref5]][[sthref6]] - -Table 2-1 Definitions  - -[width="100%",cols="25%,75%",options="header",] -|======================================================================= -|Term |Definition -|API Definition Product |A Product for which the only Java class files -contained in the product are those corresponding to the application -programming interfaces defined by the Specifications, and which is -intended only as a means for formally specifying the application -programming interfaces defined by the Specifications. - -|Computational Resource a| -A piece of hardware or software that may vary in quantity, existence, or -version, which may be required to exist in a minimum quantity and/or at -a specific or minimum revision level so as to satisfy the requirements -of the Test Suite. - -Examples of computational resources that may vary in quantity are RAM -and file descriptors. - -Examples of computational resources that may vary in existence (that is, -may or may not exist) are graphics cards and device drivers. - -Examples of computational resources that may vary in version are -operating systems and device drivers. - -|Configuration Descriptor |Any file whose format is well defined by a -specification and which contains configuration information for a set of -Java classes, archive, or other feature defined in the specification. - -|Conformance Tests |All tests in the Test Suite for an indicated -Technology Under Test, as released and distributed by the -Eclipse Foundation, excluding those tests on the -published Exclude List for the Technology Under Test. - -|Container |An implementation of the associated Libraries, as specified -in the Specifications, and a version of a Java Platform, Standard -Edition Runtime Product, as specified in the Specifications, or a later -version of a Java Platform, Standard Edition Runtime Product that also -meets these compatibility requirements. - -|Documented |Made technically accessible and made known to users, -typically by means such as marketing materials, product documentation, -usage messages, or developer support programs. - -|Exclude List |The most current list of tests, released and distributed by the -Eclipse Foundation, that are not required to be passed to certify -conformance. The Jakarta EE Specification Committee may add to the Exclude List for that -Test Suite as needed at any time, in which case the updated TCK version -supplants any previous Exclude Lists for that Test Suite. - -|Libraries a| -The class libraries, as specified through the Jakarta EE Specification Process -(JESP), for the Technology Under Test. - -The Libraries for {TechnologyFullName} are listed at the end of this chapter. - -|Location Resource a| -A location of classes or native libraries that are components of the -test tools or tests, such that these classes or libraries may be -required to exist in a certain location in order to satisfy the -requirements of the test suite. - -For example, classes may be required to exist in directories named in a -CLASSPATH variable, or native libraries may be required to exist in -directories named in a PATH variable. - -|Maintenance Lead |The corresponding Jakarta EE Specification Project -is responsible for maintaining the Specification, and the TCK for the -Technology. The Specification Project Team will propose revisions and -updates to the Jakarta EE Specification Committee which will approve -and release new versions of the specification and TCK. - -|Operating Mode a| -Any Documented option of a Product that can be changed by a user in -order to modify the behavior of the Product. - -For example, an Operating Mode can be binary (enable/disable -optimization), an enumeration (select from a list of protocols), or a -range (set the maximum number of active threads). - -Note that an Operating Mode may be selected by a command line switch, an -environment variable, a GUI user interface element, a configuration or -control file, etc. - -|Product |A vendor's product in which the Technology Under Test is -implemented or incorporated, and that is subject to compatibility -testing. - -|Product Configuration a| -A specific setting or instantiation of an Operating Mode. - -For example, a Product supporting an Operating Mode that permits user -selection of an external encryption package may have a Product -Configuration that links the Product to that encryption package. - -|Rebuildable Tests |Tests that must be built using an -implementation-specific mechanism. This mechanism must produce -specification-defined artifacts. Rebuilding and running these tests -against a known compatible implementation verifies that the mechanism generates -compatible artifacts. - -|Resource |A Computational Resource, a Location Resource, or a Security -Resource. - -|Rules |These definitions and rules in this Compatibility Requirements -section of this User's Guide. - -|Runtime |The Containers specified in the Specifications. - -|Security Resource a| -A security privilege or policy necessary for the proper execution of the -Test Suite. - -For example, the user executing the Test Suite will need the privilege -to access the files and network resources necessary for use of the -Product. - -|Specifications a| -The documents produced through the Jakarta EE Specification Process (JESP) -that define a particular Version of a Technology. - -The Specifications for the Technology Under Test are referenced later in -this chapter. - -|Technology |Specifications and one or more compatible implementations produced -through the Jakarta EE Specification Process (JESP). - -|Technology Under Test |Specifications and a compatible implementation -for {TechnologyFullName} Version {TechnologyVersion}. - -|Test Suite |The requirements, tests, and testing tools distributed by -the Maintenance Lead as applicable to a given Version of the Technology. - -|Version |A release of the Technology, as produced through the -Jakarta EE Specification Process (JESP). - -include::defns.inc[] -|======================================================================= - - -[[sthref7]][[rules-for-products]] - -2.2.2 Rules for {TechnologyFullName} Products -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following rules apply for each version of an operating system, -software component, and hardware platform Documented as supporting the -Product: - -*{techID}1* The Product must be able to satisfy all applicable compatibility -requirements, including passing all Conformance Tests, in every Product -Configuration and in every combination of Product Configurations, except -only as specifically exempted by these Rules. - -For example, if a Product provides distinct Operating Modes to optimize -performance, then that Product must satisfy all applicable compatibility -requirements for a Product in each Product Configuration, and -combination of Product Configurations, of those Operating Modes. - -*{techID}1.1* If an Operating Mode controls a Resource necessary for the -basic execution of the Test Suite, testing may always use a Product -Configuration of that Operating Mode providing that Resource, even if -other Product Configurations do not provide that Resource. -Notwithstanding such exceptions, each Product must have at least one set -of Product Configurations of such Operating Modes that is able to pass -all the Conformance Tests. - -For example, a Product with an Operating Mode that controls a security -policy (i.e., Security Resource) which has one or more Product -Configurations that cause Conformance Tests to fail may be tested using -a Product Configuration that allows all Conformance Tests to pass. - -*{techID}1.2* A Product Configuration of an Operating Mode that causes the -Product to report only version, usage, or diagnostic information is -exempted from these compatibility rules. - -*{techID}1.3* An API Definition Product is exempt from all functional -testing requirements defined here, except the signature tests. - -*{techID}2* Some Conformance Tests may have properties that may be changed. -Properties that can be changed are identified in the configuration -interview. Properties that can be changed are identified in the JavaTest -Environment (.jte) files in the Test Suite -installation. Apart from changing such properties and other allowed -modifications described in this User's Guide (if any), no source or -binary code for a Conformance Test may be altered in any way without -prior written permission. Any such allowed alterations to the -Conformance Tests will be provided via the Jakarta EE Specification Project -website and apply to all vendor compatible implementations. - -*{techID}3* The testing tools supplied as part of the Test Suite or as -updated by the Maintenance Lead must be used to certify compliance. - -*{techID}4* The Exclude List associated with the Test Suite cannot be -modified. - -*{techID}5* The Maintenance Lead can define exceptions to these Rules. Such -exceptions would be made available as above, and will apply to all vendor implementations. - -*{techID}6* All hardware and software component additions, deletions, and -modifications to a Documented supporting hardware/software platform, -that are not part of the Product but required for the Product to satisfy -the compatibility requirements, must be Documented and available to -users of the Product. - -For example, if a patch to a particular version of a supporting -operating system is required for the Product to pass the Conformance -Tests, that patch must be Documented and available to users of the -Product. - -*{techID}7* The Product must contain the full set of public and protected -classes and interfaces for all the Libraries. Those classes and -interfaces must contain exactly the set of public and protected methods, -constructors, and fields defined by the Specifications for those -Libraries. No subsetting, supersetting, or modifications of the public -and protected API of the Libraries are allowed except only as -specifically exempted by these Rules. - -*{techID}7.1* If a Product includes Technologies in addition to the -Technology Under Test, then it must contain the full set of combined -public and protected classes and interfaces. The API of the Product -must contain the union of the included Technologies. No further -modifications to the APIs of the included Technologies are allowed. - -ifdef::subset-allowed[] -*{techID}7.2* The Product may contain a subset of the classes and -interfaces for the Libraries. -endif::subset-allowed[] - -*{techID}8* Except for tests specifically required by this TCK to be rebuilt -(if any), the binary Conformance Tests supplied as part of the Test -Suite or as updated by the Maintenance Lead must be used to certify -compliance. - -*{techID}9* The functional programmatic behavior of any binary class or -interface must be that defined by the Specifications. - -include::rules.inc[] - -[[CJAIIBDJ]][[test-appeals-process]] - -2.3 Test Appeals Process -~~~~~~~~~~~~~~~~~~~~~~~~ - -Jakarta has a well established process for managing challenges to its -TCKs. Any implementor may submit a challenge to one or more tests in the -{TechnologyShortName} TCK as it relates to their implementation. Implementor -means the entity as a whole in charge of producing the final certified release. -*Challenges filed should represent the consensus of that entity*. - -2.3.1 Valid Challenges -^^^^^^^^^^^^^^^^^^^^^^ -Any test case (e.g., test class, @Test method), test case configuration (e.g., deployment descriptor), test beans, annotations, and other resources considered part of the TCK may be challenged. - -The following scenarios are considered in scope for test challenges: - -* Claims that a test assertion conflicts with the specification. -* Claims that a test asserts requirements over and above that of the specification. -* Claims that an assertion of the specification is not sufficiently implementable. -* Claims that a test is not portable or depends on a particular implementation. - -2.3.2 Invalid Challenges -^^^^^^^^^^^^^^^^^^^^^^^^ -The following scenarios are considered out of scope for test challenges and will be immediately closed if filed: - -* Challenging an implementation’s claim of passing a test. Certification is an honor system and these issues must be raised directly with the implementation. -* Challenging the usefulness of a specification requirement. The challenge process cannot be used to bypass the specification process and raise in question the need or relevance of a specification requirement. -* Claims the TCK is inadequate or missing assertions required by the specification. See the Improvement section, which is outside the scope of test challenges. -* Challenges that do not represent a consensus of the implementing community will be closed until such time that the community does agree or agreement cannot be made. The test challenge process is not the place for implementations to initiate their own internal discussions. -* Challenges to tests that are already excluded for any reason. -* Challenges that an excluded test should not have been excluded and should be re-added should be opened as a new enhancement request - -Test challenges must be made in writing via the {TechnologyShortName} specification project issue tracker -as described in link:#CJAJEAEI[Section 2.3.3, "TCK Test Appeals Steps."] - -All tests found to be invalid will be placed on the Exclude List -for that version of the {TechnologyShortName} TCK. - - -[[CJAJEAEI]][[tck-test-appeals-steps]] - -2.3.3 TCK Test Appeals Steps -^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1. Challenges should be filed via the {TechnologyFullName} specification project’s issue tracker using the label `challenge` and include the following information: -* The relevant specification version and section number(s) -* The coordinates of the challenged test(s) -* The exact TCK and exclude list versions -* The implementation being tested, including name and company -* The full test name -* A full description of why the test is invalid and what the correct behavior is believed to be -* Any supporting material; debug logs, test output, test logs, run scripts, etc. - - - -2. Specification project evaluates the challenge. + -Challenges can be resolved by a specification project lead, or a project challenge triage team, after a consensus of the specification project committers is reached or attempts to gain consensus fails. -Specification projects may exercise lazy consensus, voting or any practice that follows the principles of Eclipse Foundation Development Process. -The expected timeframe for a response is two weeks or less. -If consensus cannot be reached by the specification project for a prolonged period of time, the default recommendation is to exclude the tests and address the dispute in a future revision of the specification. - -3. Accepted Challenges. + -A consensus that a test produces invalid results will result in the exclusion of that test from certification requirements, and an immediate update and release of an official distribution of the TCK including the new exclude list. The associated `challenge` issue must be closed with an `accepted` label to indicate it has been resolved. - -4. Rejected Challenges and Remedy. + -When a`challenge` issue is rejected, it must be closed with a label of `invalid` to indicate it has been rejected. -There appeal process for challenges rejected on technical terms is outlined in Escalation Appeal. -If, however, an implementer feels the TCK challenge process was not followed, an appeal issue should be filed with specification project’s TCK issue tracker using the label `challenge-appeal`. -A project lead should escalate the issue with the Jakarta EE Specification Committee via email (jakarta.ee-spec@eclipse.org). -The committee will evaluate the matter purely in terms of due process. -If the appeal is accepted, the original TCK challenge issue will be reopened and a label of `appealed-challenge` added, along with a discussion of the appeal decision, and the `challenge-appeal` issue with be closed. -If the appeal is rejected, the `challenge-appeal` issue should closed with a label of `invalid`. - -5. Escalation Appeal. + -If there is a concern that a TCK process issue has not been resolved satisfactorily, the -https://www.eclipse.org/projects/dev_process/#6_5_Grievance_Handling[Eclipse Development Process Grievance Handling] procedure should be followed to escalate the resolution. Note that this is not a mechanism to attempt to handle implementation specific issues. - - -[[CJAJECIE]][[specifications-for-technology]] - -2.4 Specifications for {TechnologyFullName} -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The {TechnologyFullName} specification is available from the specification -project web-site: {SpecificationURL}. - -[[CJABAHGI]][[libraries-for-technology]] - -2.5 Libraries for {TechnologyFullName} -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The following is a list of the packages comprising the required class -libraries for {TechnologyShortName} {TechnologyVersion}: - -include::packages.inc[] - -For the latest list of packages, also see: - -{SpecificationURL} diff --git a/user_guides/jsonb/src/main/jbake/content/rules.inc b/user_guides/jsonb/src/main/jbake/content/rules.inc deleted file mode 100644 index b5a250f697..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/rules.inc +++ /dev/null @@ -1,78 +0,0 @@ -/////////////////////////////////////////////////////////////////////// -NOTE TO WRITERS: -Most technologies will only need the compatibility rules in rules.adoc. -Some technologies will need additional rules. If they're needed, -remove the comment block delimiters below and update the rules as -appropriate. You may need to adjust the rule numbers to avoid gaps. - -The first comment block below is additional rules needed by JPA. - -The second comment block below is additional rules needed by -JSP and Servlet. (And EJB, if it had a standalone TCK.) - -The third comment block below is additional rules that apply -to any technology that defines deployment descriptors. - -The fourth comment block is special rules that apply only to JSP. - -NOTE: This set of examples is NOT complete, but should be. -/////////////////////////////////////////////////////////////////////// - -/////////////////////////////////////////////////////////////////////// -*{techID}10* The Runtime must report an error when processing a -Configuration Descriptor that does not conform to the Specifications. - -*{techID}11* An error must be reported when processing a configuration -descriptor that includes a Java Persistence QL expression that does not -conform to the Specifications. - -*{techID}12* The presence of an XML comment in a Configuration -Descriptor, when processed by the Runtime, must not cause the -functional programmatic behavior of the Runtime to vary from the -functional programmatic behavior of the Runtime in the absence of that -comment. -/////////////////////////////////////////////////////////////////////// - -/////////////////////////////////////////////////////////////////////// -*{techID}10* Each Container must make technically accessible all Java SE -Runtime interfaces and functionality, as defined by the Specifications, -to programs running in the Container, except only as specifically -exempted by these Rules. - -*{techID}10.1* Containers may impose security constraints, as defined by -the Specifications. -/////////////////////////////////////////////////////////////////////// - -/////////////////////////////////////////////////////////////////////// -*{techID}11* A Deployment Tool must report an error when processing a -Configuration Descriptor that does not conform to the Specifications. - -*{techID}12* The presence of an XML comment in a Configuration -Descriptor, when processed by a Deployment Tool, must not cause the -functional programmatic behavior of the Deployment Tool to vary from -the functional programmatic behavior of the Deployment Tool in the -absence of that comment. -/////////////////////////////////////////////////////////////////////// - -/////////////////////////////////////////////////////////////////////// -*{techID}11* A web Container must report an error, as defined by the -Specifications, when processing a JSP Page that does not conform to the -Specifications. - -*{techID}12* The presence of a Java language comment or Java language -directive in a JSP Page that specifies ”java” as the scripting -language, when processed by a web Container, must not cause the -functional programmatic behavior of that JSP Page to vary from the -functional programmatic behavior of that JSP Page in the absence of -that Java language comment or Java language directive. - -*{techID}13* The contents of any fixed template data (defined by the -Specifications) in a JSP Page, when processed by a web Container, must -not affect the functional programmatic behavior of that JSP Page, -except as defined by the Specifications. - -*{techID}14* The functional programmatic behavior of a JSP Page that -specifies ”java” as the scripting language must be equivalent to the -functional programmatic behavior of the JSP Page Implementation Class -constructed from that JSP Page. -/////////////////////////////////////////////////////////////////////// diff --git a/user_guides/jsonb/src/main/jbake/content/tck-packages.inc b/user_guides/jsonb/src/main/jbake/content/tck-packages.inc deleted file mode 100644 index 5ca50031cc..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/tck-packages.inc +++ /dev/null @@ -1,7 +0,0 @@ -** JDOM 1.1.3 - -** Apache Commons HTTP Client 3.1 - -** Apache Commons Logging 1.1.3 - -** Apache Commons Codec 1.9 diff --git a/user_guides/jsonb/src/main/jbake/content/title.adoc b/user_guides/jsonb/src/main/jbake/content/title.adoc deleted file mode 100644 index 232172d727..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/title.adoc +++ /dev/null @@ -1,42 +0,0 @@ -type=page -status=published -title=TCK User's Guide for Technology Implementors -next=preface.html -prev=toc.html -~~~~~~ -include::attributes.conf[] - -TCK User's Guide for {TechnologyFullName}, Release {TechnologyVersion} for Jakarta EE -===================================================================================== - -[[eclipse-foundation]] -Eclipse Foundation ------------------- - -Technology Compatibility Kit User's Guide for {TechnologyFullName} - -Release {TechnologyVersion} for Jakarta EE - -{ReleaseDate} - -[[sthref1]] - -''''' - -Technology Compatibility Kit User's Guide for {TechnologyFullName}, -Release {TechnologyVersion} for Jakarta EE - -Copyright © {CopyrightDates} Oracle and/or its affiliates. All rights reserved. - -This program and the accompanying materials are made available under -the terms of the Eclipse Public License v. 2.0, which is available at -http://www.eclipse.org/legal/epl-2.0. - -SPDX-License-Identifier: EPL-2.0 - -Oracle and Java are registered trademarks of Oracle and/or its -affiliates. Other names may be trademarks of their respective owners. - -include::title.inc[] - - diff --git a/user_guides/jsonb/src/main/jbake/content/title.inc b/user_guides/jsonb/src/main/jbake/content/title.inc deleted file mode 100644 index 25bf47e08d..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/title.inc +++ /dev/null @@ -1,11 +0,0 @@ -/////////////////////////////////////////////////////////////////////// -NOTE TO WRITERS: -This is included at the tail end of the Title page. -The following section should be customized for the technology. -This is provided to allow each technology to customize legacy acronym names -that are used in this TCK. -Be sure to customize LegacyAcronym in attributes.conf -Add additional lines as needed for acronyms found in your TCK user guide. -/////////////////////////////////////////////////////////////////////// - -References in this document to {LegacyAcronym} refer to the {TechnologyFullName} unless otherwise noted. diff --git a/user_guides/jsonb/src/main/jbake/content/using-examples.inc b/user_guides/jsonb/src/main/jbake/content/using-examples.inc deleted file mode 100644 index b47962f035..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/using-examples.inc +++ /dev/null @@ -1,53 +0,0 @@ -/////////////////////////////////////////////////////////////////////// -NOTE TO WRITERS: -These CLI examples can be customized as necessary. -/////////////////////////////////////////////////////////////////////// - -1. Change to any subdirectory under `/src/com/sun/ts/tests`. -2. Start JavaTest using the following command: -+ --- -[source,oac_no_warn] ----- -ant runclient ----- --- - -[[GCMCU]] - -Example 5-1 {TechnologyShortName} TCK Signature Tests - -To run the {TechnologyShortName} TCK signature tests, enter the -following commands: - -[source,subs="attributes"] ----- -cd {sigTestDirectoryExample} -ant runclient ----- - -[[GCMBV]] - - -Example 5-2 Single Test Directory - -To run a single test directory, enter the following commands: - -[source,subs="attributes"] ----- -cd {singleTestDirectoryExample} -ant runclient ----- - -[[GCMCA]] - - -Example 5-3 Subset of Test Directories - -To run a subset of test directories, enter the following commands: - -[source,subs="attributes"] ----- -cd {subsetTestDirectoryExample} -ant runclient ----- diff --git a/user_guides/jsonb/src/main/jbake/content/using.adoc b/user_guides/jsonb/src/main/jbake/content/using.adoc deleted file mode 100644 index b0a41c51e1..0000000000 --- a/user_guides/jsonb/src/main/jbake/content/using.adoc +++ /dev/null @@ -1,323 +0,0 @@ -type=page -status=published -title=Executing Tests -next=debug.html -prev=config.html -~~~~~~ -include::attributes.conf[] -Executing Tests -=============== - -[[GBFWO]] - - -[[executing-tests]] -5 Executing Tests ------------------ - -The {TechnologyShortName} TCK uses the JavaTest harness to execute the -tests in the test suite. For detailed instructions that explain how to -run and use JavaTest, see the JavaTest User's Guide and Reference in -the documentation bundle. - -This chapter includes the following topics: - -* link:#GBFUZ[Starting JavaTest] -* link:#GBFWM[Running a Subset of the Tests] -* link:#GCLRR[Running the TCK Against your selected CI] -* link:#GCLRZ[Running the TCK Against a Vendor's Implementation] -* link:#GBFVK[Test Reports] - - -[NOTE] -======================================================================= - -The instructions in this chapter assume that you have installed and -configured your test environment as described in -link:install.html#GBFTP[Chapter 3, "Installation,"] and -link:config.html#GBFVV[Chapter 4, "Setup and Configuration,"], -respectively. - -======================================================================= - -ifdef::rebuild[] -As explained in link:rebuild.html#GCLIZ[Appendix B, "Packaging the -Test Applications in Servlet-Compliant WAR -Files With VI-Specific Information,"] the {TechnologyShortName} TCK -introduces the concept of repackaging the TCK tests. -endif::rebuild[] - - -[[GBFUZ]][[starting-javatest]] - -5.1 Starting JavaTest -~~~~~~~~~~~~~~~~~~~~~ - -There are two general ways to run the {TechnologyShortName} TCK using -the JavaTest harness software: - -* Through the JavaTest GUI -* From the command line in your shell environment - - -[NOTE] -======================================================================= - -The `ant` command referenced in the following -two procedures and elsewhere in this guide is the Apache Ant -build tool, which will need to be downloaded separately. -The `build.xml` file in `/bin` contains the various Ant -targets for the {TechnologyShortName} TCK test suite. - -======================================================================= - - -[[GBFWH]][[to-start-javatest-in-gui-mode]] - -5.1.1 To Start JavaTest in GUI Mode -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Execute the following commands: - -[source,oac_no_warn] ----- -cd /bin -ant gui ----- - -[[GBFVW]][[to-start-javatest-in-command-line-mode]] - -5.1.2 To Start JavaTest in Command-Line Mode -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -include::using-examples.inc[] - -[[GBFWM]][[running-a-subset-of-the-tests]] - -5.2 Running a Subset of the Tests -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Use the following modes to run a subset of the tests: - -* link:#GBFVT[Section 5.2.1, "To Run a Subset of Tests in GUI Mode"] -* link:#GBFWK[Section 5.2.2, "To Run a Subset of Tests in Command-Line Mode"] -* link:#GBFVL[Section 5.2.3, "To Run a Subset of Tests in Batch Mode -Based on Prior Result Status"] - -[[GBFVT]][[to-run-a-subset-of-tests-in-gui-mode]] - -5.2.1 To Run a Subset of Tests in GUI Mode -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1. From the JavaTest main menu, click *Configure*, then click *Change -Configuration*, and then click *Tests to Run*. + -The tabbed Configuration Editor dialog box is displayed. -2. Click *Specify* from the option list on the left. -3. Select the tests you want to run from the displayed test tree, and -then click *Done*. + -You can select entire branches of the test tree, or use `Ctrl+Click` or -`Shift+Click` to select multiple tests or ranges of tests, respectively, -or select just a single test. -4. Click *Save File*. -5. Click *Run Tests*, and then click *Start* to run the tests you selected. + -Alternatively, you can `right-click` the test you want from the test tree -in the left section of the JavaTest main window, and choose *Execute -These Tests* from the menu. -6. Click *Report*, and then click *Create Report*. -7. Specify the directory in which the JavaTest test harness will write -the report, and then click *OK* + -A report is created, and you are asked whether you want to view it. -8. Click *Yes* to view the report. - -[[GBFWK]][[to-run-a-subset-of-tests-in-command-line-mode]] - -5.2.2 To Run a Subset of Tests in Command-Line Mode -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -1. Change to the directory containing the tests you want to run. -2. Start the test run by executing the following command: + -+ -[source] ----- -ant runclient ----- -+ -The tests in the directory and its subdirectories are run. - -[[GBFVL]][[to-run-a-subset-of-tests-in-batch-mode-based-on-prior-result-status]] - -5.2.3 To Run a Subset of Tests in Batch Mode Based on Prior Result Status -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -You can run certain tests in batch mode based on the test's prior run -status by specifying the `priorStatus` system property when invoking -`ant` - -Invoke `ant` with the `priorStatus` property. - -The accepted values for the `priorStatus` property are any combination -of the following: - -* `fail` -* `pass` -* `error` -* `notRun` - -For example, you could run all the {TechnologyShortName} tests with a -status of failed and error by invoking the following commands: - -[source,oac_no_warn] ----- -ant -DpriorStatus="fail,error" runclient ----- - -Note that multiple `priorStatus` values must be separated by commas. - -[[GCLRR]][[running-the-tck-against-the-ri]] - -5.3 Running the TCK Against another CI -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Some test scenarios are designed to ensure that the configuration and deployment of -all the prebuilt {TechnologyShortName} TCK tests against one Compatible -Implementation are successful operating with other compatible implementations, and that the TCK is ready for -compatibility testing against the Vendor and Compatible Implementations. - -1. Verify that you have followed the configuration instructions in -link:config.html#GBFVU[Section 4.1, "Configuring Your Environment to Run -the TCK Against the Compatible Implementation."] -2. If required, verify that you have completed the steps in -link:config.html#GCLIW[Section 4.3.2, "Deploying the Prebuilt Archives."] -3. Run the tests, as described in link:#GBFUZ[Section 5.1, "Starting -JavaTest,"] and, if desired, link:#GBFWM[Section 5.2, "Running a Subset -of the Tests."] - -[[GCLRZ]][[running-the-tck-against-a-vendors-implementation]] - -5.4 Running the TCK Against a Vendor's Implementation -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -This test scenario is one of the compatibility test phases that all -Vendors must pass. - -1. Verify that you have followed the configuration instructions in -link:config.html#GCLHU[Section 4.2, "Configuring Your Environment to -Repackage and Run the TCK Against the Vendor Implementation."] -2. If required, verify that you have completed the steps in -link:config.html#GCLIL[Section 4.3.3, "Deploying the -Test Applications Against the Vendor Implementation."] -3. Run the tests, as described in link:#GBFUZ[Section 5.1, "Starting -JavaTest,"] and, if desired, link:#GBFWM[Section 5.2, "Running a Subset -of the Tests."] - -[[GBFVK]][[test-reports]] - -5.5 Test Reports -~~~~~~~~~~~~~~~~ - -A set of report files is created for every test run. These report files -can be found in the report directory you specify. After a test run is -completed, the JavaTest harness writes HTML reports for the test run. -You can view these files in the JavaTest ReportBrowser when running in -GUI mode, or in the web browser of your choice outside the JavaTest -interface. - -To see all of the HTML report files, enter the URL of the `report.html` -file. This file is the root file that links to all of the other HTML -reports. - -The JavaTest harness also creates a `summary.txt` file in the report -directory that you can open in any text editor. The `summary.txt` file -contains a list of all tests that were run, their test results, and -their status messages. - -[[GBFWD]][[creating-test-reports]] - -5.5.1 Creating Test Reports -^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Use the following modes to create test reports: - -* link:#GBFVH[Section 5.5.1.1, "To Create a Test Report in GUI Mode"] -* link:#GBFVC[Section 5.5.1.2, "To Create a Test Report in Command-Line Mode"] - -[[GBFVH]][[to-create-a-test-report-in-gui-mode]] - -5.5.1.1 To Create a Test Report in GUI Mode -+++++++++++++++++++++++++++++++++++++++++++ - -1. From the JavaTest main menu, click *Report*, then click *Create Report*. + -You are prompted to specify a directory to use for your test reports. -2. Specify the directory you want to use for your reports, and then -click *OK*. + -Use the Filter list to specify whether you want to generate reports for -the current configuration, all tests, or a custom set of tests. + -You are asked whether you want to view report now. -3. Click *Yes* to display the new report in the JavaTest ReportBrowser. - -[[GBFVC]][[to-create-a-test-report-in-command-line-mode]] - -5.5.1.2 To Create a Test Report in Command-Line Mode -++++++++++++++++++++++++++++++++++++++++++++++++++++ - -1. Specify where you want to create the test report. -a. To specify the report directory from the command line at runtime, -use: -+ -[source] ----- -ant -Dreport.dir="report_dir" ----- -+ -Reports are written for the last test run to the directory you specify. -2. To specify the default report directory, set the `report.dir` -property in +{jteFileName}+. + -For example: -+ -[source] ----- -report.dir="/home/josephine/reports" ----- -+ -3. To disable reporting, set the `report.dir` property to `"none"`, -either on the command line or in +{jteFileName}+. + -For example: -+ -[source] ----- -ant -Dreport.dir="none" ----- -+ - -[[GBFVB]][[viewing-an-existing-test-report]] - -5.5.2 Viewing an Existing Test Report -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Use the following modes to view an existing test report: - -* link:#GBFVO[Section 5.5.2.1, "To View an Existing Report in GUI Mode"] -* link:#GBFWB[Section 5.5.2.2, "To View an Existing Report in -Command-Line Mode"] - -[[GBFVO]][[to-view-an-existing-report-in-gui-mode]] - -5.5.2.1 To View an Existing Report in GUI Mode -++++++++++++++++++++++++++++++++++++++++++++++ - -1. From the JavaTest main menu, click *Report*, then click *Open Report*. + -You are prompted to specify the directory containing the report you want -to open. -2. Select the report directory you want to open, and then click *Open*. + -The selected report set is opened in the JavaTest ReportBrowser. - -[[GBFWB]][[to-view-an-existing-report-in-command-line-mode]] - -5.5.2.2 To View an Existing Report in Command-Line Mode -+++++++++++++++++++++++++++++++++++++++++++++++++++++++ - -Use the Web browser of your choice to view the `report.html` file in the -report directory you specified from the command line or in +{jteFileName}+. - -include::using.inc[] - diff --git a/user_guides/jsonb/src/main/jbake/content/using.inc b/user_guides/jsonb/src/main/jbake/content/using.inc deleted file mode 100644 index e69de29bb2..0000000000 diff --git a/user_guides/jsonb/src/main/jbake/jbake.properties b/user_guides/jsonb/src/main/jbake/jbake.properties deleted file mode 100644 index 05c7056f0a..0000000000 --- a/user_guides/jsonb/src/main/jbake/jbake.properties +++ /dev/null @@ -1,24 +0,0 @@ -# -# Copyright (c) 2021 Oracle and/or its affiliates. All rights reserved. -# -# This program and the accompanying materials are made available under the -# terms of the Eclipse Public License v. 2.0, which is available at -# http://www.eclipse.org/legal/epl-2.0. -# -# This Source Code may also be made available under the following Secondary -# Licenses when the conditions for such availability set forth in the -# Eclipse Public License v. 2.0 are satisfied: GNU General Public License, -# version 2 with the GNU Classpath Exception, which is available at -# https://www.gnu.org/software/classpath/license.html. -# -# SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 -# - -site.host=http://jbake.org -render.tags=false -render.sitemap=false -render.archive=false -render.feed=false -render.index=false -asciidoctor.option.safe=0 -asciidoctor.attributes.export=true \ No newline at end of file diff --git a/user_guides/jsonb/src/main/jbake/templates/footer.ftl b/user_guides/jsonb/src/main/jbake/templates/footer.ftl deleted file mode 100644 index 746cbf1ccd..0000000000 --- a/user_guides/jsonb/src/main/jbake/templates/footer.ftl +++ /dev/null @@ -1,44 +0,0 @@ -<#-- a footer template fragment included in the page template --> -
- - - - - - - - - <#if content.prev??> - - - - <#if content.next??> - - - - - -
- - - Previous - - - - - Next - - - - - Contents - -
- - - Eclipse Foundation Logo  - Copyright © 2017, 2021 Oracle and/or its affiliates. All rights reserved. - - - - diff --git a/user_guides/jsonb/src/main/jbake/templates/header.ftl b/user_guides/jsonb/src/main/jbake/templates/header.ftl deleted file mode 100644 index 50b72ae8d0..0000000000 --- a/user_guides/jsonb/src/main/jbake/templates/header.ftl +++ /dev/null @@ -1,54 +0,0 @@ - -<#-- a header template fragment included in the page template --> - - - - <#if (content.title)??><#escape x as x?xml>${content.title}</#escape></#if> - - - - - - - - - -
- ${content.title}
-
-
- - - - - - - - - <#if content.prev??> - - - - <#if content.next??> - - - - - -
- - - Previous - - - - - Next - - - - - Contents - -
- diff --git a/user_guides/jsonb/src/main/jbake/templates/menu.ftl b/user_guides/jsonb/src/main/jbake/templates/menu.ftl deleted file mode 100644 index 888c03dcff..0000000000 --- a/user_guides/jsonb/src/main/jbake/templates/menu.ftl +++ /dev/null @@ -1 +0,0 @@ -<#-- a menu bar template fragment included in the page template --> \ No newline at end of file diff --git a/user_guides/jsonb/src/main/jbake/templates/page.ftl b/user_guides/jsonb/src/main/jbake/templates/page.ftl deleted file mode 100644 index eca51db35d..0000000000 --- a/user_guides/jsonb/src/main/jbake/templates/page.ftl +++ /dev/null @@ -1,8 +0,0 @@ -<#-- a top level page layout template --> - -<#include "header.ftl"> -<#include "menu.ftl"> - -${content.body} - -<#include "footer.ftl"> \ No newline at end of file diff --git a/user_guides/jsonb/src/theme/jakartaee-theme.yml b/user_guides/jsonb/src/theme/jakartaee-theme.yml deleted file mode 100644 index 6092a2f5c9..0000000000 --- a/user_guides/jsonb/src/theme/jakartaee-theme.yml +++ /dev/null @@ -1,299 +0,0 @@ -# -# Following is the asciidoctor-pdf default theme [1], with small -# customizations, mostly for header and footer, marked "EE". -# -# [1] https://github.com/asciidoctor/asciidoctor-pdf/blob/master/data/themes/default-theme.yml -# -font: - catalog: - # Noto Serif supports Latin, Latin-1 Supplement, Latin Extended-A, Greek, Cyrillic, Vietnamese & an assortment of symbols - Noto Serif: - normal: notoserif-regular-subset.ttf - bold: notoserif-bold-subset.ttf - italic: notoserif-italic-subset.ttf - bold_italic: notoserif-bold_italic-subset.ttf - # M+ 1mn supports ASCII and the circled numbers used for conums - M+ 1mn: - normal: mplus1mn-regular-ascii-conums.ttf - bold: mplus1mn-bold-ascii.ttf - italic: mplus1mn-italic-ascii.ttf - bold_italic: mplus1mn-bold_italic-ascii.ttf - # M+ 1p supports Latin, Latin-1 Supplement, Latin Extended, Greek, Cyrillic, Vietnamese, Japanese & an assortment of symbols - # It also provides arrows for ->, <-, => and <= replacements in case these glyphs are missing from font - M+ 1p Fallback: - normal: mplus1p-regular-fallback.ttf - bold: mplus1p-regular-fallback.ttf - italic: mplus1p-regular-fallback.ttf - bold_italic: mplus1p-regular-fallback.ttf - fallbacks: - - M+ 1p Fallback -page: - background_color: ffffff - layout: portrait - margin: [0.5in, 0.67in, 0.67in, 0.67in] - # margin_inner and margin_outer keys are used for recto/verso print margins when media=prepress - margin_inner: 0.75in - margin_outer: 0.59in - #size: A4 # EE - size: Letter # EE -base: - align: justify - # color as hex string (leading # is optional) - font_color: 333333 - # color as RGB array - #font_color: [51, 51, 51] - # color as CMYK array (approximated) - #font_color: [0, 0, 0, 0.92] - #font_color: [0, 0, 0, 92%] - font_family: Noto Serif - # choose one of these font_size/line_height_length combinations - #font_size: 14 - #line_height_length: 20 - #font_size: 11.25 - #line_height_length: 18 - #font_size: 11.2 - #line_height_length: 16 - font_size: 10.5 - #line_height_length: 15 - # correct line height for Noto Serif metrics - line_height_length: 12 - #font_size: 11.25 - #line_height_length: 18 - line_height: $base_line_height_length / $base_font_size - font_size_large: round($base_font_size * 1.25) - font_size_small: round($base_font_size * 0.85) - font_size_min: $base_font_size * 0.75 - font_style: normal - border_color: eeeeee - border_radius: 4 - border_width: 0.5 -# FIXME vertical_rhythm is weird; we should think in terms of ems -#vertical_rhythm: $base_line_height_length * 2 / 3 -# correct line height for Noto Serif metrics (comes with built-in line height) -vertical_rhythm: $base_line_height_length -horizontal_rhythm: $base_line_height_length -# QUESTION should vertical_spacing be block_spacing instead? -vertical_spacing: $vertical_rhythm -link: - font_color: 428bca -# literal is currently used for inline monospaced in prose and table cells -literal: - font_color: b12146 - font_family: M+ 1mn -menu_caret_content: " \u203a " -heading: - align: left - #font_color: 181818 - font_color: $base_font_color - font_family: $base_font_family - font_style: bold - # h1 is used for part titles (book doctype) or the doctitle (article doctype) - #h1_font_size: floor($base_font_size * 2.6) # EE - h1_font_size: floor($base_font_size * 2.5) # EE, squeeze title onto one line - # h2 is used for chapter titles (book doctype only) - h2_font_size: floor($base_font_size * 2.15) - h3_font_size: round($base_font_size * 1.7) - h4_font_size: $base_font_size_large - h5_font_size: $base_font_size - h6_font_size: $base_font_size_small - #line_height: 1.4 - # correct line height for Noto Serif metrics (comes with built-in line height) - line_height: 1 - margin_top: $vertical_rhythm * 0.4 - margin_bottom: $vertical_rhythm * 0.9 -title_page: - align: right - logo: - top: 10% - title: - top: 55% - font_size: $heading_h1_font_size - font_color: 999999 - line_height: 0.9 - subtitle: - font_size: $heading_h3_font_size - font_style: bold_italic - line_height: 1 - authors: - margin_top: $base_font_size * 1.25 - font_size: $base_font_size_large - font_color: 181818 - revision: - margin_top: $base_font_size * 1.25 -block: - margin_top: 0 - margin_bottom: $vertical_rhythm -caption: - align: left - font_size: $base_font_size * 0.95 - font_style: italic - # FIXME perhaps set line_height instead of / in addition to margins? - margin_inside: $vertical_rhythm / 3 - #margin_inside: $vertical_rhythm / 4 - margin_outside: 0 -lead: - font_size: $base_font_size_large - line_height: 1.4 -abstract: - font_color: 5c6266 - font_size: $lead_font_size - line_height: $lead_line_height - font_style: italic - first_line_font_style: bold - title: - align: center - font_color: $heading_font_color - font_family: $heading_font_family - font_size: $heading_h4_font_size - font_style: $heading_font_style -admonition: - column_rule_color: $base_border_color - column_rule_width: $base_border_width - padding: [0, $horizontal_rhythm, 0, $horizontal_rhythm] - #icon: - # tip: - # name: fa-lightbulb-o - # stroke_color: 111111 - # size: 24 - label: - text_transform: uppercase - font_style: bold -blockquote: - font_color: $base_font_color - font_size: $base_font_size_large - border_color: $base_border_color - border_width: 5 - # FIXME disable negative padding bottom once margin collapsing is implemented - padding: [0, $horizontal_rhythm, $block_margin_bottom * -0.75, $horizontal_rhythm + $blockquote_border_width / 2] - cite_font_size: $base_font_size_small - cite_font_color: 999999 -# code is used for source blocks (perhaps change to source or listing?) -code: - font_color: $base_font_color - font_family: $literal_font_family - font_size: ceil($base_font_size) - padding: $code_font_size - line_height: 1.25 - # line_gap is an experimental property to control how a background color is applied to an inline block element - line_gap: 3.8 - background_color: f5f5f5 - border_color: cccccc - border_radius: $base_border_radius - border_width: 0.75 -conum: - font_family: M+ 1mn - font_color: $literal_font_color - font_size: $base_font_size - line_height: 4 / 3 -example: - border_color: $base_border_color - border_radius: $base_border_radius - border_width: 0.75 - background_color: ffffff - # FIXME reenable padding bottom once margin collapsing is implemented - padding: [$vertical_rhythm, $horizontal_rhythm, 0, $horizontal_rhythm] -image: - align: left -prose: - margin_top: $block_margin_top - margin_bottom: $block_margin_bottom -sidebar: - background_color: eeeeee - border_color: e1e1e1 - border_radius: $base_border_radius - border_width: $base_border_width - # FIXME reenable padding bottom once margin collapsing is implemented - padding: [$vertical_rhythm, $vertical_rhythm * 1.25, 0, $vertical_rhythm * 1.25] - title: - align: center - font_color: $heading_font_color - font_family: $heading_font_family - font_size: $heading_h4_font_size - font_style: $heading_font_style -thematic_break: - border_color: $base_border_color - border_style: solid - border_width: $base_border_width - margin_top: $vertical_rhythm * 0.5 - margin_bottom: $vertical_rhythm * 1.5 -description_list: - term_font_style: bold - term_spacing: $vertical_rhythm / 4 - description_indent: $horizontal_rhythm * 1.25 -outline_list: - indent: $horizontal_rhythm * 1.5 - #marker_font_color: 404040 - # NOTE outline_list_item_spacing applies to list items that do not have complex content - item_spacing: $vertical_rhythm / 2 -table: - background_color: $page_background_color - #head_background_color: - #head_font_color: $base_font_color - head_font_style: bold - #body_background_color: - body_stripe_background_color: f9f9f9 - foot_background_color: f0f0f0 - border_color: dddddd - border_width: $base_border_width - cell_padding: 3 -toc: - indent: $horizontal_rhythm - line_height: 1.4 - dot_leader: - #content: ". " - font_color: a9a9a9 - #levels: 2 3 -# NOTE in addition to footer, header is also supported -footer: - font_size: $base_font_size_small - # NOTE if background_color is set, background and border will span width of page - #border_color: dddddd # EE - #border_width: 0.25 # EE - height: $base_line_height_length * 2.5 - line_height: 1 - padding: [$base_line_height_length / 2, 1, 0, 1] - vertical_align: top - #image_vertical_align: or - # additional attributes for content: - # * {page-count} - # * {page-number} - # * {document-title} - # * {document-subtitle} - # * {chapter-title} - # * {section-title} - # * {section-or-chapter-title} - recto: - #columns: "<50% =0% >50%" - right: - #content: '{page-number}' # EE - #content: '{section-or-chapter-title} | {page-number}' - #content: '{document-title} | {page-number}' - content: '{document-title}{nbsp}{nbsp}{nbsp} *{page-number}*' # EE - #center: - # content: '{page-number}' - left: # EE - content: '{status}' # EE - verso: - #columns: $footer_recto_columns - left: - #content: $footer_recto_right_content # EE - #content: '{page-number} | {chapter-title}' - content: '*{page-number}* {nbsp}{nbsp}{nbsp}{document-title}' # EE - #center: - # content: '{page-number}' - right: # EE - content: '{status}' # EE -header: # EE - font_size: $base_font_size_small # EE - border_color: dddddd # EE - border_width: 0.25 # EE - height: $base_line_height_length * 2.5 # EE - line_height: 1 # EE - padding: [$base_line_height_length / 2, 1, 0, 1] # EE - vertical_align: top # EE - recto: # EE - right: # EE - content: '{section-or-chapter-title}' # EE - verso: # EE - left: # EE - content: '{section-or-chapter-title}' # EE