Allow any variable name on ognl expression when specify single value object as parameter object #1487
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes gh-1486 (Related with #1237)
I've allowed to access a parameter object(value object) using any variable name on OGNL expression such as same with bind variable name.
In this change, it allow specify as follow:
NOTE:
In version 3.5.0,
#{category}
(in bind variable) is valid butcategory != null
(in OGNL expression) is invalid.