You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like support would be perfect fit.
Please consider map library's annotations (at least JsonProperty and JsonCreator) to jakarta.json.bind:jakarta.json.bind-api.
We would definitely go for it if you'd support more generic annotations to avoid provider locking. There is a spec which is exactly a nice way to make application code library/framework agnostic.
We have code with JSR-367 annotations (or without them at all for Jackson, since Jackson can do that) and now we explore new possibilities. Often library authors make library specific annotations for whatever reason. There are nice more "generic" annotations like jakarta.annotation:jakarta.annotation-api, org.glassfish.hk2.external:jakarta.inject and JSON-B in this case.. why not to use them or at least provide support..?
Please consider this possibility.
The text was updated successfully, but these errors were encountered:
Seems like support would be perfect fit.
Please consider map library's annotations (at least
JsonProperty
andJsonCreator
) tojakarta.json.bind:jakarta.json.bind-api
.We would definitely go for it if you'd support more generic annotations to avoid provider locking. There is a spec which is exactly a nice way to make application code library/framework agnostic.
We have code with JSR-367 annotations (or without them at all for Jackson, since Jackson can do that) and now we explore new possibilities. Often library authors make library specific annotations for whatever reason. There are nice more "generic" annotations like
jakarta.annotation:jakarta.annotation-api
,org.glassfish.hk2.external:jakarta.inject
and JSON-B in this case.. why not to use them or at least provide support..?Please consider this possibility.
The text was updated successfully, but these errors were encountered: