DATACMNS-716 - Allow collection executions with wrapper types as return values. #130
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
June 17, 2015 16:59
…rn values. Prepare issue branch.
…rn values. Temporarily use Spring 4.2.0 to get support for CompletableFuture + async from spring-core.
…rn values. We now support CollectionExecutions in query derivation in combination with Wrapper types like (Future, Optional, CompletableFuture, ListenableFuture) that wrap a collection, e.g. Future<List<User>>. Previously we used the “raw” return type which tricked our detection for Collection / Page / Slice executions. Original pull request: #130.
thomasdarimont
force-pushed
the
issue/DATACMNS-716
branch
from
a66998e to
c157f01
Compare
thomasdarimont
pushed a commit
that referenced
this pull request
Jun 17, 2015
…rn values. We now support collection executions in query derivation in combination with wrapper types like (Future, Optional, CompletableFuture, ListenableFuture) that wrap a collection, e.g. Future<List<User>>. Previously we used the "raw" return type which tricked our detection for Collection / Page / Slice executions. Original pull request: #130.
thomasdarimont
pushed a commit
that referenced
this pull request
Jun 17, 2015
…rn values. We now support collection executions in query derivation in combination with wrapper types like (Future, Optional) that wrap a collection, e.g. Future<List<User>>. Previously we used the "raw" return type which tricked our detection for Collection / Page / Slice executions. Original pull request: #130.
thomasdarimont
pushed a commit
that referenced
this pull request
Jun 17, 2015
…rn values. We now support collection executions in query derivation in combination with wrapper types like (Future, Optional) that wrap a collection, e.g. Future<List<User>>. Previously we used the "raw" return type which tricked our detection for Collection / Page / Slice executions. Original pull request: #130.
thomasdarimont
pushed a commit
that referenced
this pull request
Jun 22, 2015
…rn values. We now support collection executions in query derivation in combination with wrapper types like (Future, Optional) that wrap a collection, e.g. Future<List<User>>. Previously we used the "raw" return type which tricked our detection for Collection / Page / Slice executions. Original pull request: #130.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We now support CollectionExecutions in query derivation in combination with Wrapper types like (Future, Optional, CompletableFuture, ListenableFuture) that wrap a collection, e.g. Future<List>.
Previously we used the “raw” return type which tricked our detection for Collection / Page / Slice executions.