@JsonTypeInfo always required for JsonTypeInfo.Id.NAME even if globally configured

[franjavi]

Using 2.8.5, if we set a global configuration for the type resolver like:

TypeResolverBuilder<?> typeResolverBuilder = new ObjectMapper.DefaultTypeResolverBuilder(ObjectMapper.DefaultTyping.OBJECT_AND_NON_CONCRETE);
typeResolverBuilder.init(JsonTypeInfo.Id.NAME, null);
typeResolverBuilder.inclusion(JsonTypeInfo.As.PROPERTY);
typeResolverBuilder.typeProperty("__class");
mapper.setDefaultTyping(typeResolverBuilder);

The @JsonTypeInfo annotation still required. (WORKS)

@JsonTypeInfo(property = "__class", use = JsonTypeInfo.Id.NAME, include = JsonTypeInfo.As.PROPERTY)
@JsonSubTypes({
        @JsonSubTypes.Type(value=A.class, name="classA"),
        @JsonSubTypes.Type(value=B.class, name="classB")
})
public abstract class Base {
}

(DOES NOT WORK)

@JsonSubTypes({
        @JsonSubTypes.Type(value=A.class, name="classA"),
        @JsonSubTypes.Type(value=B.class, name="classB")
})
public abstract class Base {
}

Is this behavior intended? In my opinion @JsonTypeInfo is redundant here, where can be different type configurations by mistake of the developer.

[cowtowncoder]

I think I'd need a full reproducible test case to see what happens. This issue actually belongs under jackson-databind (annotations package only defines annotations, but none of functionality that uses them), but for now that's ok.

[cowtowncoder]

FWTW from symptoms it would seem like problem was that default typing was simply not applied. It would also seem like you could simplify your code a bit by calling

mapper.enableDefaultTypingAsProperty(DefaultTyping.OBJECT_AND_NON_CONCRETE, "__class");

instead of explicitly configuring ``TypeResolverBuilder.

[franjavi]

I tried again, but that won't work for JsonTypeInfo.Id.NAME. I attach a small test that checks it. testJackson.zip

[cowtowncoder]

@franjavi I did not mean it should fix it, just that it'd be simpler way to do it. I'll see if test case sheds some light on why typing is not applied.