[jax-rs-spec users] Re: Support for JSONB

From: Markus KARG <>
Date: Tue, 30 Jun 2015 19:50:31 +0200

Do I understand your answer correctly that not only the entity providers have to be included, but also the JSON-P / JSONB implementation itself which is used by that entity providers? So, does Jersey-on-JavaSE bundle JSON-P / JSONB?

Won't this create a problem in case a JAX-RS implementation runs in a context where JSON-P / JSONB is already found on the classpath, like Java EE?

-----Original Message-----
From: Santiago Pericasgeertsen []
Sent: Dienstag, 30. Juni 2015 18:51
Subject: Re: [jax-rs-spec users] Support for JSONB


 It should be similar to JSONP. This is what the spec says now:

10.2.6 Java API for JSON Processing
In a product that supports the Java API for JSON Processing (JSON-P), implementations MUST support entity providers for the following types: JsonStructure, JsonObject and JsonArray. …
— Santiago 
> On Jun 30, 2015, at 11:56 AM, Markus KARG <> wrote:
> Experts,
> on our agenda is support for JSONB, which is a mandatory API of the Java EE umbrella. Hence, in a Java EE environment, JSONB API will be found on the classpath already, and "we" (JAX-RS) can simply use it on that platform. But what happens on Java SE? Must JAX-RS provide JSONB API co-bundled, or can we rely on an application vendor to provide JSONB API on the classpath?
> -Markus