Jackson JSON Processor

TextNode.getValueAsLong() does not properly parse Long values, unless a default value is provided

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.7.4
  • Fix Version/s: 1.7.8, 1.8.3, 1.9
  • Component/s: JSON tree (JsonNode)
  • Labels:
    None
  • Testcase included:
    yes
  • Number of attachments :
    1

Description

TextNode.getValueAsLong() is not properly parsing long values from nodes. For example, with JSON such as the following:

{ "id" : "127353264013893" }

node.getValueAsLong() returns 0. However, if you pass a default value to the node, such as node.getValueAsLong(-1), then it correctly returns 127353264013893.

See attached testCase for demonstration.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tatu Saloranta added a comment -

Fixed – was a cut'n paste problem, calling integer parsing code.

Show
Tatu Saloranta added a comment - Fixed – was a cut'n paste problem, calling integer parsing code.
Hide
Permalink
Tatu Saloranta added a comment -

(note: unfortunately I just released 1.8.2, so this did not quite make it in, but fix is in 1.8 branch as well as trunk)

Show
Tatu Saloranta added a comment - (note: unfortunately I just released 1.8.2, so this did not quite make it in, but fix is in 1.8 branch as well as trunk)
Hide
Permalink
Christopher Hunt added a comment -

Just to clarify and save others the time - this is fixed in 1.9.7 - nothing prior on the 1.9 branch.

Show
Christopher Hunt added a comment - Just to clarify and save others the time - this is fixed in 1.9.7 - nothing prior on the 1.9 branch.
Hide
Permalink
Tatu Saloranta added a comment -

Good catch, thank you for pointing this out.

Odd... there must have been another underlying problem – 1.9.7 does indeed have further fixes, but something was fixed with versions included. Probably fix here was one affecting range, but not to the other issue (not using default value).

Show
Tatu Saloranta added a comment - Good catch, thank you for pointing this out. Odd... there must have been another underlying problem – 1.9.7 does indeed have further fixes, but something was fixed with versions included. Probably fix here was one affecting range, but not to the other issue (not using default value).

People

  • Assignee:
    Tatu Saloranta
    Reporter:
    Chris Pruett
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: