Andrew Guibert

Updating this issue to cover JSON-B annotations in general so it also encompasses `@JsonbCreator` as requested by this Yasson issue; https://github.com/eclipse-ee4j/yasson/issues/326

I like this suggestion, perhaps there is an opportunity for CDI integration here? If we were to apply some sort of bean-defining annotation on a JSON-B adapter, then JSON-B could...

adding a link to this relevant issue also: https://github.com/eclipse-ee4j/jsonb-api/issues/112

Proposed API addition: ```java public class JsonbConfig { public static final String ALLOW_UNKNOWN_PROPERTIES = "jsonb.allow-unknown-properties"; /** * Property used to specify whether unknown properties should be skipped or * rejected...

by fallback setter do you mean something like [Jackson's `@JsonAnyGetter/Setter`](https://www.baeldung.com/jackson-annotations)? If so, I agree we should consider that feature for the next version of JSON-B, but it should be tracked...

@rmannibucau Recently came across this use case again and I agree with your original stance that we should consider both issues together. What do you think about the following: -...

For the name, how about `@JsonbExtras` or `@JsonbExtraProperties`? I think it's fine to have a few options on what to bind to like Map and JsonObject, but it needs to...

> About JsonValue the point is that we (as impl) own the creation of this instance so we can bind it directly in the form we want, it is just...

I think this is a good feature and we should consider it for the next version of the spec. Additionally, CDI already has the knowledge to know which impl classes...

> models are likely nlt cdi beans Good point, usually the app directly creates model objects (or uses JSON-B to create them) as POJOs. How about an explicit mapping through...