We now pick up result size limiting constraints from the query method name. This allows usage of `findTopN` and `findFirst` keywords.
Original pull request: #22.
We now make sure that cached SpelCriteria's use the appropriate EvaluationContext containing parameters from the request instead of using the EvaluationContext of the cached query.
Original Pull Request: #20
We now distinguish between operating systems when choosing a SecureRandom algorithm. Additionally we check the availability of the implementations and choose the first one available.
Original pull request: #21.
We introduced an explicit CachingKeyValuePartTreeQuery and allow setting the gernal repository query stategy via QueryCreatorType.
By default queries will not be cached.
Original pull request: #18.
We now allow using Spring's meta-annotation programming model. Own meta-annotations can be composed using @KeySpace and @AliasFor annotation.
Example for a custom meta-annotation corresponding to @KeySpace("sessions") when it's used with @SessionsKeyspace class MyEntity {…}:
@Persistent
@Retention(RetentionPolicy.RUNTIME)
@Target({ ElementType.TYPE })
@KeySpace
public @interface SessionsKeyspace {
@AliasFor(annotation = KeySpace.class, attribute = "value")
String name() default "sessions";
}
Original pull request: #19.
We now expose a dedicated method for implementors to use to create the repository factory instance based on the configuration of the factory.
Added unit tests to make sure the factory bean fails fast if it's configured improperly.
Original Pull Request: #17
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.
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.
