https://bz.apache.org/bugzilla/show_bug.cgi?id=65681
Felix Schumacher <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Keywords| |FixedInTrunk --- Comment #10 from Felix Schumacher <[email protected]> --- @Philippe, could you test next build from trunk, or nightly and report back, if it fixes your problem? commit b06f9def2a5c7007a6ee804487fc259c0fbd747b AuthorDate: Sat Nov 13 15:46:37 2021 +0100 Use default values for null values when extracting with JSONPostProcessor When we extract a null value for a given expression, we now replace that null with the given default value for the expression. That leads to slight change of the meaning of a missing value. Consider the JSON structure: {"context": null} and the JSON Path: "$.context" The new implementation will replace the `null` with the default value, while the old would have stringified it to the empty string. Cleanup of parameter handling of default values. We should use the default value for the current handled expression and not pass all default values for all expression. That leads to confusion, only. (Well, I was confused) Bugzilla Id: 65681 --- .../extractor/json/jsonpath/JSONManager.java | 2 +- .../extractor/json/jsonpath/JSONPostProcessor.java | 51 +++++++++++----------- .../jmeter/extractor/TestJSONPostProcessor.java | 25 ++++++++--- xdocs/changes.xml | 1 + 4 files changed, 45 insertions(+), 34 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
