Since JSON-P 1.0 and likely also JSON-B 1.0 won't be available in a
"modular" form, even if an implementing product from a JAX-RS point would
only have to implement 2 or 3 of the API elements, they still need to
include the entire javax.json-api. Which is however not so terribly big
(20kb)
The only JSRs that are even more modular to my knowledge are JSR 361 and
363 where the spec explicitly declares OPTIONALITY, so one may find a JAR
that contains just these mandatory elements, not the rest of the API.
Getting them down to just a few kb, obviously for SE/EE this probably won't
matter as much here;-)
Werner
On Wed, Jul 1, 2015 at 11:15 AM, <users-request_at_jax-rs-spec.java.net> wrote:
> Table of contents:
>
> 1. [jax-rs-spec users] Support for JSONB - "Markus KARG" <
> markus_at_headcrashing.eu>
> 2. [jax-rs-spec users] Re: Support for JSONB - Santiago Pericasgeertsen <
> santiago.pericasgeertsen_at_oracle.com>
> 3. [jax-rs-spec users] Re: Support for JSONB - "Markus KARG" <
> markus_at_headcrashing.eu>
>
>
>
> ---------- Forwarded message ----------
> From: Markus KARG <markus_at_headcrashing.eu>
> To: <jsr370-experts_at_jax-rs-spec.java.net>
> Cc:
> Date: Tue, 30 Jun 2015 17:56:33 +0200
> Subject: [jax-rs-spec users] Support for JSONB
>
> 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
>
>
> ---------- Forwarded message ----------
> From: Santiago Pericasgeertsen <santiago.pericasgeertsen_at_oracle.com>
> To: jsr370-experts_at_jax-rs-spec.java.net
> Cc:
> Date: Tue, 30 Jun 2015 12:50:51 -0400
> Subject: [jax-rs-spec users] Re: Support for JSONB
> Markus,
>
> 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 <markus_at_headcrashing.eu>
> 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
>
>
>
> ---------- Forwarded message ----------
> From: Markus KARG <markus_at_headcrashing.eu>
> To: <jsr370-experts_at_jax-rs-spec.java.net>
> Cc:
> Date: Tue, 30 Jun 2015 19:50:31 +0200
> Subject: [jax-rs-spec users] Re: Support for JSONB
> 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 [mailto:santiago.pericasgeertsen_at_oracle.com
> ]
> Sent: Dienstag, 30. Juni 2015 18:51
> To: jsr370-experts_at_jax-rs-spec.java.net
> Subject: Re: [jax-rs-spec users] Support for JSONB
>
> Markus,
>
> 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 <markus_at_headcrashing.eu>
> 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
>
>
>
> End of digest for list users_at_jax-rs-spec.java.net - Wed, 01 Jul 2015
>
>