Markus KARG

> The Server the implementation is hooked in does not need to provide the information. For instance, I can see Grizzly and Jetty does so, whereas in Netty I cannot...

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

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...

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...

>" (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...

>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...

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...

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...

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...

+1 for making that dokument perfectly bullet-proof by the Platform team, but *for the time being* we are on the safe side if we take the FAQ's pretty unambiguous answer...