Skip to content

Only call getEffectiveDefaults when needed#128

Merged
kallestenflo merged 1 commit intojson-path:masterfrom
trajano:getEffectiveDefaults-when-necessary
Sep 29, 2015
Merged

Only call getEffectiveDefaults when needed#128
kallestenflo merged 1 commit intojson-path:masterfrom
trajano:getEffectiveDefaults-when-necessary

Conversation

@trajano
Copy link
Copy Markdown
Contributor

@trajano trajano commented Sep 24, 2015

The call to getEffectiveDefaults will make json-smart dependency
required for processing. By removing the call when not needed
json-smart can be safely excluded.

In addition the logger was removed since it was not being used.

The call to `getEffectiveDefaults` will make `json-smart` dependency
required for processing.  By removing the call when not needed
`json-smart` can be safely excluded.

In addition the logger was removed since it was not being used.
@ThorbenLindhauer
Copy link
Copy Markdown

Hi,

The merged commit only partially solves the problem. There are code lines that internally create a new configuration object (see https://github.com/jayway/JsonPath/blob/json-path-2.1.0/json-path/src/main/java/com/jayway/jsonpath/internal/filter/ValueNode.java#L778) but only copy the provided json provider, not the mapping provider. In consequence, the code proposed in this fix and on current master still calls #getEffectiveDefaults since mappingProvider is null.

Cheers,
Thorben

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants