DATAKV-129 - Allow usage of @AliasFor with @KeySpace. #19
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
prepare issue branch.
mp911de
force-pushed
the
issue/DATAKV-129
branch
from
b3ae373 to
b03b3ef
Compare
mp911de
pushed a commit
that referenced
this pull request
Mar 10, 2016
Undo quick hacks from previous commit and add test explicitly testing keyspace resolution. Original pull request: #19.
mp911de
added a commit
that referenced
this pull request
Mar 10, 2016
Updated license header. Original pull request: #19.
mp911de
force-pushed
the
issue/DATAKV-129
branch
from
b03b3ef to
07d1722
Compare
mp911de
pushed a commit
that referenced
this pull request
Mar 10, 2016
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 with @keyspace("sessions"): @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.
mp911de
added a commit
that referenced
this pull request
Mar 10, 2016
Updated license header. Original pull request: #19.
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.
Updated license header. Original pull request: #19.
mp911de
force-pushed
the
issue/DATAKV-129
branch
from
07d1722 to
7e603b5
Compare
mp911de
pushed a commit
that referenced
this pull request
Mar 10, 2016
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.
mp911de
added a commit
that referenced
this pull request
Mar 10, 2016
Updated license header. Original pull request: #19.
|
Merged with b40c8c1. |
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.
No description provided.