Tatu Saloranta

Yeah, use of `EXTERNAL_PROPERTY` is not really supported with "POJO-as-Array" because that will introduce a new main-level property. Ideally an `InvalidDefinitionException` would be thrown, I think (unless of course we...

@jamesmudd Yes, at least currently this is unsupported. I am not 100% sure it couldn't be solved, fwtw, but the whole `As.EXTERNAL_PROPERTY` is rather tricky to support even without as-array...

To be honest, I think that trying to actually implement support for such type identifier handling would be quite difficult. So although defining annotation setup to describe intent would be...

@drekbour WDYT? Although in general it is difficult to determined viability of deserializing into given type (Jackson really knows by trying to figure it out), being `abstract` would be reliable...

It seems to me code itself is wrong, you should not read with A value2 = MAPPER.readValue(string2, Inter.A.class); since the base type is `Inter.class` -- why would you give concrete...

Ok, so the biggest hurdle here comes from Enum implementation (by JDK) -- Value `Inter.A.A2` is (I think) an instance of a sub-class of `Inter.A` as opposed to `Inter.A.A1` which...

Actually, having said all of that; maybe the problem is reverse: sub-class of Enum `A` for value `A2` (an inner class `Inter$A$1` should NOT be used, but rather it should...

@nlisker Right, just writing out aloud possible ways to tackle the issue (and what the issue actually is) :)

@nlisker Turns out `ClassNamedIdResolver` had the fix and just needed to be added to all 4 other resolvers. Fix going in via #4780, for 2.18 (next release 2.18.2).

I think there is unfortunately ambiguity wrt XML with default settings, for this case. But enabling `ToXmlGenerator.Feature.WRITE_NULLS_AS_XSI_NIL` should help preserve `null` as `null` -- this settings is disabled by default...