Quick answer: sounds like a Jackson bug. Longer answer: maintaining accurate read context hierarchy gets complicated since it needs to "stitch" together contexts from original context (physical parser, originally), and then context for TreeTraversingParser (for JsonNode) or its equivalent for TokenBuffer (when re-reading buffered content).
I think there has been a report before for `jackson-core` (or `jackson-databind`), but I can not locate one now on issue tracker. -+ Tatu +- On Wed, Aug 22, 2018 at 4:11 AM Paolo Bazzi <[email protected]> wrote: > > Additional info: verified with latest Jackson 2.9.6 version > > -- > You received this message because you are subscribed to the Google Groups > "jackson-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "jackson-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
