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 Toke
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 jackson-user+unsubscr...@googlegroups.com.
To post to