Deprecating vs completely specifying JsonAdapter

[mkarg]

The JSON-B specification lacks several details about the use of JsonAdapter. As a result, the existing implementations behave differently. As a consequence, existing applications need to apply workarounds to work on all implementations unchanged.

There are two proposals currently how to fix that in a future version of the specification:

• @mkarg proposes to completely specify JsonAdapter, so both implementations behave the same.
  The effect would be that all existing applications can either keep the existing workarounds or remove them, at their exclusive discretion.
• @rmannibucau proposes to deprecate and eventually drop JsonAdapter.

To get broad input from the community, everybody (users and vendors) are invited to discuss the pros and cons of these proposals.

To come to a final decision, committers are invited to vote for / agains these proposals.

[mkarg]

@m0mus @rmannibacau I like to invite you into this discussion about the future of JsonbAdapter.

[mkarg]

To start the discussion, I like to forward some opinions I collected when discussing with other users:

• There should never be a need to change existing, running applications, even when switching to a new major release of a spec. Deprecation will enforce changing running applications.
• @struberg forwarded a ruleset of the Jakarta EE WG which (literally) forbids both, deprecation and removal, AFAIK even for new major releases. Maybe Mark could be so kind to post the link here? Thanks.
• Adapters are very simple and intuitive to use, while Serializers are much more complex and enforces the need to understand JSON-P. In fact, people like JSON-B over JSON-P because JSON-P is rather "hard core" to understand.
• Adapters are working just fine for most cases at the time of writing, besides some edge corner bugs in Yasson (in fact, it looks like there are just two smaller issues to fix in Yasson to make it work as the application programmer intuitiveley expects it, even in most complex cases). I expect the amount of work to specify and fix the edge cases to be smaller than the work for everybody to replace adapters by serializers.

[rmannibucau]

Without rephrasing what I already wrote Id like to emphasis that this statement is wrong or should be perceived as such to kot biase this topic thinking:

Adapters are very simple and intuitive to use, while Serializers are much more complex and enforces the need to understand JSON-P

Technically this is true of adapters too and serializer context makes it intuitive (jsonb api like) and simple.

Also note we can make a deserializer+serializer an api (codec like) if it makes it easier but it avoids to duplicate the concept hiding thz limitation in the api.

[mkarg]

Let's agree to disagree. I already explained the reason why application programmers (me included) perceive adapters to be intuitive and simple, but do not perceive serializers to be. All arguments are said and will not change just because you personally feel different about it. We need to find more arguments instead of saying an argument told by a user would be "wrong". It is his perception, and there is nothing "wrong" about his perception, wether we share it or not.

BTW, here is the link to the Jakarta EE docs mentioned by Mark Struberg: https://jakartaee.github.io/jakartaee-platform/CompatibilityRequirements. Let me quote two items from the contained FAQ:

Q2. Is it permissible to remove an existing interface from an existing specification?
No, because this would violate rules 2 and 3 above. Note that it is also not permissible to mark it as deprecated.

Q4. Is it permissible to remove an existing method from an existing interface?
No, because this would violates rules 2 and 3 above.

Note that Jakarta EE officially is not applying SemVer, but there is an undecided request to do so in future: jakartaee/platform#449.

[rmannibucau]

Not saying perception is wrong, just it is not factual and mainly due to a wrong knowledge we can easily fix so we should give this point much weight in the deprecation path since user will win, at least with a simpler and lighter api to learn (note not a single user understand adapters today).

[mkarg]

" (note not a single user understand adapters today)"

I personally know of application programmers that pretty well understand and successfully use adapters, hence I cannot see how you come to this general statement?

[rmannibucau]

Do they understand they are limited to jsonp types as of today in jsonb spec state and therefore are just serializers with a return type instead of a callback?
All users i talked too, including some vendor implementors thought it was a pre-serialization mapping (this process being undefined or vendor specific with > 1 adapters matching)...so api is often overevaluated by users, when you understand it is just a jsonp top layer it becomes useless but almost nobody get to that point to my knowledge.

[mkarg]

Do they understand they are limited to jsonp types as of today in jsonb spec state...?

Actually today's spec does not limit adapters to JSON-P types. As you know, Yasson does support mapping to non-JSON-P types (proven today in #337, and you confirmed recently that it is not unambiguously told in the adapter spec that adapters are for JSON-P types, not for JSON-B types). Hence there is a difference what you want adapters to be understood like, and what de-facto adapters are doing in Yasson - which is intuitive and understood by the users I talked to. And while Jakarta EE does not have the idea of "reference implementations" anymore, people still accept Yasson's behavior as authoritative (besides bugs); BTW The Yasson Readme even (incorrectly) supports this wrong perception, by saying, it would be an "official reference implementation"...:

I understand your point, but note that others have a different angle of view.

[rmannibucau]

Yasson has not compliant features as johnzon has...but if you respect the spec you are limited to jsonp, this was clarified in multiple tickets as the rest not being defined so clearly unsupported by the spec (vendors are always doing at least the spec).
Yasson is kot authoritative but the ri, spec is the pdf, javadoc and api, period, this is what jakarta mention as authoritative.
So still, if perception can be discussed, facts remain the same and perception does not help much.
Once again we can fix any misdoc/comm.

[mkarg]

I think we understood and respect each other's experience and collected feedback, so it is time to hear what others think how to proceed. Let's hear what the Yasson committers say, and let's collect some feedback from the broad community. It makes not much sense to decide just on the base of your and mine original claims, just as it makes not much sense to claim that it would be irrelevant what application programmed perceived (aka "misunderstood"). In the end, it is the application programmers who we do this spec for, not us.

Update: I invited people on Twitter to join our discussion.

[rmannibucau]

Agree on that statement, just highlighted that perception is sometimes wrong due to past experience or bad doc so not a real decision key.

[mkarg]

IMHO decision key for any API should be user expectations. The problem is that most people's expectations are tightly coupled to some kind of extrapolation of their perception of that past. This is why I came up with "perception". We cannot erase perception to get actually unbiased opinions. Hence we need a very good replacement to convince people to give up their biased opinion.

[rmannibucau]

Reasoning like that you will end up with guava like bundles, really hope we dont think like that, just lead to mess and error prone api. From my window it looks an empty argument and a bad way to try to defend something technically not accurate.
I strongly think people can learn and are not dumb to just copy stackoverflow (or we dont care cause they wouldnt understand any solution right?) so, once again, not something to take into account for any decision for the future if we care where we go.

[mkarg]

No comment from me on how dumb or lazy people are / are not, but we should take into consideration that talking from a business angle, replacing APIs means modifying existing applications eventually, which is costs, possibly high costs.

Edit: BTW, I do not defend something technically accurate. I plea for making it accurate, but not by replacing it.