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
Currently it is assumed that injectable property may also be deserializable. But often this is not true, and injectable property really should ONLY come from injection, and it is not desireable that it could be overridden. If so, there should be a way to indicate this.
There are actually some failing cases that would be easiest to solve by such property, both wrt injection-via-constructor + objectId (see #639), and for "injectable type not deserializable".
The text was updated successfully, but these errors were encountered:
cowtowncoder
changed the title
(2.9) Allow denoting @JacksonInject entry to be "inject-only" (no deserialization)
Allow denoting @JacksonInject entry to be "inject-only" (no deserialization)
Oct 6, 2016
Currently it is assumed that injectable property may also be deserializable. But often this is not true, and injectable property really should ONLY come from injection, and it is not desireable that it could be overridden. If so, there should be a way to indicate this.
There are actually some failing cases that would be easiest to solve by such property, both wrt injection-via-constructor + objectId (see #639), and for "injectable type not deserializable".
The text was updated successfully, but these errors were encountered: