You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot construct instance of `com.fasterxml.jackson.dataformat.yaml.failing.ObjectId63Test$StringHolder` (although at least one Creator exists): no String-argument constructor/factory method to deserialize from String value ('foo1')
at [Source: (StringReader); line: 3, column: 6] (through reference chain: com.fasterxml.jackson.dataformat.yaml.failing.ObjectId63Test$ScratchModel["boo"])
...
The text was updated successfully, but these errors were encountered:
It's odd this does not work, considering there is a basic test for native object ids (anchors), references working. Need to figure out what is the difference...
Ok, interesting. It looks like aggressive clearing of anchor value in YAMLParser.nextToken() causes the problem somehow.
I think what basically happens is that there are 2 potential YAML locations -- before logical start of Object, and for the first key/value pair -- that sort of conflict in that only second will be retained. So need to figure out how to retain first value.
So, although there are cases where Anchor/Reference pairs work via Jackson
@JsonIdentityInfo
, looks like even simple cases sometimes fail.For example
fails with
The text was updated successfully, but these errors were encountered: