JsonParser.getTokenLocation() doesn't update after field names. about jackson-core HOT 7 CLOSED

Ah. Yes, this must be a regression due to an earlier rewrite that combines parsing of field names with minimal tokenization of the following value. This was done for performance reasons, but did not consider effects for token location handling.

from jackson-core.

(and by earlier, I mean something like 1.7 or 1.8 -- quite a while ago).

from jackson-core.

It gets worse when the values are not the first in an object. For example:

{
  "book" : [ {
    "year" : 1999,
    "title" : "Title",
    "author" : "Author"
  }]
}

In this case for title, the getTokenLocation() and the getCurrentLocation() select both for the FIELD_NAME and the string value the following text:

                        ,
    "author"

Please recognize no value is selected this time, and the previous , is also selected. Similar behaviour for the author.
(This is with version: 2.4.3.)

from jackson-core.

Is this with byte- or char-backed source? Or both.

from jackson-core.

@cowtowncoder I have just tested with the byte-backed source: new JsonFactory().createParser(json.getBytes("UTF-8")). Just tested with the char-based backend and it seems to work the same way.

from jackson-core.

@aborg0 Makes sense, but just wanted to verify.

from jackson-core.

Please see my attached pull request for a fix.

from jackson-core.