`@JacksonInject` causes deserialization failure (unresolved forward reference)

[cowwoc]

Jackson 2.4.4 is able to successfully deserialize forward references, but it fails to do so if the constructor contains a @JacksonInject parameter.

[cowwoc]

Testcase: https://gist.github.com/cowwoc/743d2839bc7297a47516

Inlined ObjectIdWithInjectable639Test.java:

---

class ObjectIdWithInjectable639Test extends DatabindTestUtil {
    // for [databind#639]
    @JsonIdentityInfo(generator = ObjectIdGenerators.IntSequenceGenerator.class)
    public static final class Parent2 {
        @JsonProperty
        public Child2 child;

        @JsonCreator
        public Parent2(@JacksonInject("context") String context) {
        }
    }

    @JsonIdentityInfo(generator = ObjectIdGenerators.IntSequenceGenerator.class)
    public static final class Child2 {
        @JsonProperty
        private final Parent2 parent;

        @JsonCreator
        public Child2(@JsonProperty("parent") Parent2 parent) {
            this.parent = parent;
        }
    }

    @Test
    void objectIdWithInjectable() throws Exception {
        ObjectMapper mapper = new ObjectMapper()
                .setInjectableValues(new InjectableValues.Std().
                        addValue("context", "Stuff"));
        Parent2 parent2 = new Parent2("foo");
        Child2 child2 = new Child2(parent2);
        parent2.child = child2;

        String json2 = mapper.writeValueAsString(parent2);
        parent2 = mapper.readValue(json2, Parent2.class);
        assertNotNull(parent2);
        assertNotNull(parent2.child);
    }
}

[cowtowncoder]

Actually I think this is different, and bit trickier. Problem is that there is an actual cycle from deserializer perspective, since parent2 may not be constructed before all JSON for it (and its descendants) are consumed; but its child child2 needs parent reference passed via constructor. So the solution here would be to remove @JsonCreator on child2 with non-creator alternative.

Except that in theory, since parent2 only needs injectable value, perhaps implementing #1268 would allow this to be handled even without removing of @JsonCreator.

[cowtowncoder]

So, the json output here is something like:

{"@id":1,"child":{"@id":2,"parent":1}}

and the reason this can not be resolved at this point is only partially due to @JacksonInject. The underlying problem is that neither Parent2 nor Child2 may be constructed before all data is available, as both have @JsonCreator annotated constructor.
Now, in theory Jackson could notice that the only parameter for Parent2 is injectable and create it immediately -- however, before #1381 is implemented, there is no way to indicate that something is purely injectable, that is, something that only comes via injection and not data. With #1268 it should be possible to define this, and with that, this problem would be solvable theoretically.