Olivier Cailloux

> so we'll see what happens Has anything happened? What about Gson?

Indeed a suitable workaround, which I currently use. But this request is about using an annotation to avoid having to register adapters globally, which can be impossible (in case two...

Relatedly (not sure it should be the same issue?), I’d love to be able to specify (by annotation) mutliple adapters on a field, and that these adapters be all used...

I was thinking about something like the following. ``` @JsonbTypeAdapters({AdapterA.class, AdapterB.class}) Map aMap; ``` or even the following, where the type B uses internally some type C that json needs...

If I provide an adapter between `K` and `String` I’d like that a `Map` becomes treated as if it was a `Map`. Can this be added to the spec as...

I don’t think it’s being pedantic, this issue seems of importance for predictability of the resulting json (which is crucial to about any application I guess). I’d like an annotation...

Is there a programmatic equivalent?

Seems better to me to have a more specific kind of exception in this case. User might want to catch JsonbException and act specifically on it, but not all kinds...

> forcing a jsonbexception just enforces the cause to be processed What do you mean? `JsonbException` does extend `RuntimeException`, right?

I am a bit lost in this conversation. Are you arguing for rejecting my PR? Or for modifying it? In the second case, which modification exactly so you suggest? In...