-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Allow specifying @JacksonInject
does not fail when there's no corresponding value
#3072
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
+1 |
giulong
added a commit
to giulong/jackson-databind
that referenced
this issue
May 3, 2025
…uring deserializer construction
giulong
added a commit
to giulong/jackson-databind
that referenced
this issue
May 9, 2025
giulong
added a commit
to giulong/jackson-databind
that referenced
this issue
May 9, 2025
…ect-spike feat(FasterXML#3072): moving JacksonInject annotation introspection during des…
giulong
added a commit
to giulong/jackson-databind
that referenced
this issue
May 9, 2025
@JacksonInject
does not fail when there's no corresponding value
cowtowncoder
added a commit
that referenced
this issue
May 10, 2025
This has been implemened via #5131, to be included in 2.20.0 release (which is still months away). |
cowtowncoder
added a commit
that referenced
this issue
May 11, 2025
cowtowncoder
added a commit
that referenced
this issue
May 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When something is annotated with
@JacksonInject
, if theObjectMapper
doesn't have injectable values set, it will fail withCaused by: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: No 'injectableValues' configured, cannot inject value with id [<name of injectable value>]
. And there's a different error if the value doesn't exist on the injectable values object.I'd like to be able to annotation things with
@JacksonInject
like so:Additionally, there could also be a
DeserializationFeature
called something likeFAIL_ON_UNKNOWN_INJECT_VALUE
that defaults to true.The text was updated successfully, but these errors were encountered: