Re: [jakartaee-platform-dev] [External] : Re: Simplifying the platform b

[Romain Manni-Bucau <rmannibucau@xxxxxxxxx>]

Think it is key to keep both split since mapping is a high level use case not always used and in EE you have several specs often "rejecting" it by design (thinking to jbatch).

In a cloud erea, being able to trim down its stack is key.

To complete that, jaxb is often built on a parser/streamer (like sax for some impl like sxc) so it is very similar.

The community are not 1-1 too so I don't see why it should be split as of today except the risk to make it tightly coupled which would defeat the JSONB spec by itself IMHO.

Romain Manni-Bucau
@rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book

Le mar. 1 mars 2022 à 18:51, Lukas Jungmann <lukas.jungmann@xxxxxxxxxx> a écrit :

On 3/1/22 6:13 PM, arjan tijms wrote:
> Hi,
> ...Or "Why does Jakarta EE have two JSON
> frameworks, my favorite platform simply has JSON, and it works".

ability to parse the source is one use-case, ability to bind parsed
result to Java object(s) is different use-case; do we want the "binder"
to be required to implement or stick to one implementation of the parser
OR do we want to allow "binder" implementations to work with arbitrary
parser as long as such parser implements defined APIs - jsonp in this
case? It's very similar to JAXP/JAXB

thanks,
--lukas

>
> Kind regards,
> Arjan
>
>
>
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!ZyB2cJsAUpCNpsBU5GxxBMGNyUL7z5pgoGH_-1rw3f8CjzRlmtBOWIvooYsgsLvRBuw$

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev