Skip to content
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

Memoize Annotations Added #3

Closed
wants to merge 53 commits into from
Closed
Changes from 1 commit
Commits
Show all changes
53 commits
Select commit Hold shift + click to select a range
7b0c411
attempting to add Memoize ast transformation... not quite working yet.
ctoestreich Dec 30, 2011
39c73bc
attempting to add Memoize ast transformation... not quite working yet.
ctoestreich Dec 31, 2011
993605b
making some progress... just need to solve the issue with getting var…
ctoestreich Jan 12, 2012
f7aff29
making some progress... just need to solve the issue with getting var…
ctoestreich Jan 12, 2012
33a7946
trying a bunch of things to get the variableScope to work....
ctoestreich Jan 12, 2012
d9f6a54
looked at using the VariableScopeVisitor to no avail. still produces…
ctoestreich Jan 13, 2012
bcb18d7
I think it is working finally...
ctoestreich Jan 13, 2012
86ad25c
adding spock and integration specs for testing simple and complex str…
ctoestreich Jan 13, 2012
00c3fe6
adding spock and integration specs for testing simple and complex str…
ctoestreich Jan 13, 2012
bfbaa33
adding ability to use closure or params also added expire to usable p…
ctoestreich Jan 14, 2012
c07d513
appending the method name to the key automatically
ctoestreich Jan 14, 2012
a3b6e51
fixing key generation string
ctoestreich Jan 14, 2012
701cc04
fixing key generation string
ctoestreich Jan 14, 2012
f405e1c
removing the method name from cache key
ctoestreich Jan 17, 2012
4c7acca
moving some folders and adding codenarc and coverage and tests to mai…
ctoestreich Jan 17, 2012
709aaf8
adding AST tests to the mainline code and adding ignore for files in …
ctoestreich Jan 17, 2012
a5c66d5
adding AST tests to the mainline code and adding ignore for files in …
ctoestreich Jan 17, 2012
8282130
missed adding AST when I moved :)
ctoestreich Jan 17, 2012
e035485
still having trouble parsing the gstrings
ctoestreich Jan 17, 2012
59838cc
still having trouble parsing the gstrings
ctoestreich Jan 17, 2012
c9fa260
finally got the gstrings to work and added list and has support. hav…
ctoestreich Jan 18, 2012
cc51b44
added remaining ASTs
ctoestreich Jan 19, 2012
52fe31f
doing a bunch of cleanup and adding detection and auto injection of t…
ctoestreich Jan 23, 2012
882bf9e
starting to update documentation, doing a bunch of cleanup and adding…
ctoestreich Jan 23, 2012
5130aa4
updating documentation
ctoestreich Jan 23, 2012
48358df
updating documentation
ctoestreich Jan 23, 2012
f8fef5a
updating documentation
ctoestreich Jan 23, 2012
6ad5f7c
updating documentation
ctoestreich Jan 23, 2012
fe5eef5
updating documentation
ctoestreich Jan 30, 2012
2f8b498
updating documentation
ctoestreich Jan 30, 2012
00309fc
updating documentation
ctoestreich Jan 30, 2012
a29a3ea
updating documentation
ctoestreich Jan 30, 2012
bf481da
updating documentation
ctoestreich Jan 30, 2012
a0d147c
adding domain and service for test and adding the files in plugin exc…
ctoestreich Jan 30, 2012
159c9a3
codenarc cleanup a bit of the service code
ctoestreich Jan 30, 2012
3de6f9d
codenarc cleanup
ctoestreich Jan 30, 2012
43247ba
codenarc cleanup
ctoestreich Jan 30, 2012
01242f5
codenarc report naming
ctoestreich Jan 30, 2012
a987081
codenarc report naming
ctoestreich Jan 30, 2012
ff9515c
codenarc cleanup
ctoestreich Jan 30, 2012
1e8a928
codenarc cleanup
ctoestreich Jan 30, 2012
405c8b9
fixing build for default project
ctoestreich Jan 30, 2012
50bdef7
fixing build for default project
ctoestreich Jan 30, 2012
4d4f0bf
fixing build for default project
ctoestreich Jan 30, 2012
020deb2
codenarc cleanup
ctoestreich Jan 30, 2012
05c08d9
codenarc cleanup
ctoestreich Jan 30, 2012
649f603
codenarc cleanup
ctoestreich Jan 30, 2012
b23a6e2
codenarc cleanup
ctoestreich Jan 30, 2012
f11c7fa
codenarc cleanup
ctoestreich Jan 30, 2012
32aea5f
codenarc cleanup
ctoestreich Jan 30, 2012
bec3497
codenarc cleanup
ctoestreich Jan 30, 2012
a306006
codenarc cleanup
ctoestreich Jan 30, 2012
46f8625
removal of tomcat/hibernate from application.properties.
ctoestreich Feb 1, 2012
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
updating documentation
  • Loading branch information
ctoestreich committed Jan 30, 2012
commit fe5eef539edc7ce68d0b71116b5dcca8a58ed560
34 changes: 17 additions & 17 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -250,8 +250,8 @@ The user should be aware that any annotated method will be completely wrapped in

The @Memoize annotation is to be used when dealing with objects that are stored in Redis as strings. This annotation takes the following parameters:

value - A closure in the following format
key - A unique key for the data cache
value - A closure in the following format. (key OR value required)
key - A unique key for the data cache. (key OR value required)
expire - Expire time in ms. Will default to never so only pass a value like 3600 if you want value to expire.

*You can either specify a closure OR a key and expire. When using the closure style key `@Memoize({"#{text}"})` you may not pass a key or expire to the annotation as the closure will be evaluated directly and used as the key value. This is due to a limitation on how Java deals with closure annotation parameters.*
Expand Down Expand Up @@ -285,11 +285,11 @@ Here is an example of usage:

### @MemoizeDomainObject ###

TODO: Fill me in
The @MemoizeDomainObject annotation is to be used when dealing with domain objects that are to have their id's stored in Redis. See the documentation on Domain Object Memoization above for more details. This annotation takes the following parameters:

key - A unique key for the data cache
key - A unique key for the data cache. (required)
expire - Expire time in ms. Will default to never so only pass a value like 3600 if you want value to expire.
clazz - The class of the object to be memoizing.
clazz - The class of the object to be memoizing. (required)

Here is an example of usage:

Expand All @@ -301,11 +301,11 @@ Here is an example of usage:

### @MemoizeDomainList ###

TODO: Fill me in
The @MemoizeDomainList annotation is to be used when dealing with lists of domain objects that are to have their id's stored in Redis. See the documentation on Domain List Memoization above for more details. This annotation takes the following parameters:

key - A unique key for the data cache
key - A unique key for the data cache. (required)
expire - Expire time in ms. Will default to never so only pass a value like 3600 if you want value to expire.
clazz - The class of the object to be memoizing.
clazz - The class of the object to be memizing. (required)

Here is an example of usage:

Expand All @@ -319,10 +319,10 @@ Here is an example of usage:

### @MemoizeList ###

TODO: Fill me in
The @MemoizeList annotation is to be used when dealing with list type objects. This annotation takes the following parameters:

value - A closure in the following format
key - A unique key for the data cache
value - A closure in the following format. (key OR value required)
key - A unique key for the data cache. (key OR value required)
expire - Expire time in ms. Will default to never so only pass a value like 3600 if you want value to expire.

*You can either specify a closure OR a key and expire. When using the closure style key `@Memoize({"#{text}"})` you may not pass a key or expire to the annotation as the closure will be evaluated directly and used as the key value. This is due to a limitation on how Java deals with closure annotation parameters.*
Expand All @@ -337,11 +337,11 @@ Here is an example of usage:

### @MemoizeScore ###

TODO: Fill me in
The @MemoizeScore annotation is to be used when dealing with scores in hashes. This annotation takes the following parameters:

key - A unique key for the data cache
key - A unique key for the data cache. (required)
expire - Expire time in ms. Will default to never so only pass a value like 3600 if you want value to expire.
member - The hash property to store.
member - The hash property to store. (required)

Here is an example of usage:

Expand All @@ -352,10 +352,10 @@ Here is an example of usage:

### @MemoizeHash ###

TODO: Fill me in
The @MemoizeHash annotation is to be used when dealing with maps/hash type objects. This annotation takes the following parameters:

value - A closure in the following format
key - A unique key for the data cache
value - A closure in the following format. (key OR value required)
key - A unique key for the data cache. (key OR value required)
expire - Expire time in ms. Will default to never so only pass a value like 3600 if you want value to expire.

*You can either specify a closure OR a key and expire. When using the closure style key `@Memoize({"#{text}"})` you may not pass a key or expire to the annotation as the closure will be evaluated directly and used as the key value. This is due to a limitation on how Java deals with closure annotation parameters.*
Expand Down