Skip to content

DATAKV-115 - Make derived finder execution thread-safe. #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

christophstrobl
Copy link
Member

We now make sure separate SpelExpression and EvaluationContext for each and every derived finder execution to assert the context cannot be accidentally overridden.

We now make sure seprate SpelExpression and EvaluationContext for each and every derived finder execution to assert the expression context cannot be accidentally overridden.
odrotbohm pushed a commit that referenced this pull request Feb 9, 2016
We now make sure separate SpelExpression and EvaluationContext for each and every derived finder execution to assert the expression context cannot be accidentally overridden.

Original pull request: #16.
odrotbohm added a commit that referenced this pull request Feb 9, 2016
Introduced dedicated constructor on SpelCriteria to default the EvaluationContext to StandardEvaluationContext. Switched to ternary if in KeyValuePartTreeQuery for both application of Pageable and Sort. Tweaked unit test to actually compile in Eclipse.

Original pull request: #16.
@odrotbohm odrotbohm closed this Feb 9, 2016
@odrotbohm odrotbohm deleted the issue/DATAKV-115 branch February 9, 2016 14:54
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.

2 participants