diff --git a/docs/src/reference/docbook/introduction/getting-started.xml b/docs/src/reference/docbook/introduction/getting-started.xml
index 291b1af41..8384f623d 100644
--- a/docs/src/reference/docbook/introduction/getting-started.xml
+++ b/docs/src/reference/docbook/introduction/getting-started.xml
@@ -10,7 +10,7 @@
First Steps
- As explained in , Spring Data Redis (SDR) provides integration
+ As explained in , Spring Data Redis (SDR) provides integration
between Spring framework and the Redis key value store. Thus, it is important to become acquainted with both of these
frameworks (storages or environments depending on how you want to name them). Throughout the SDR documentation,
each section provides links to resources relevant however, it is best to become familiar with these topics beforehand.
@@ -39,36 +39,12 @@
Trying Out The Samples
- Unfortunately the SDKV project is very young and there are no samples available yet. However we are working on them and plan to make them available
- as soon as possible. In the meantime however, one can use our test suite as a code example (assuming the documentation is not enough) - we provide extensive
- integration tests for our code base.
-
-
+ One can find various samples for key value stores in the dedicated example repo, at
+ http://github.com/SpringSource/spring-data-keyvalue-examples. For Spring Redis,
+ of interest is the retwisj sample, a Twitter-clone built on top of Redis which can be run locally or be deployed into the cloud. See its
+ documentation, the following blog
+ entry or the
+ live instance for more information.
diff --git a/docs/src/reference/docbook/reference/redis.xml b/docs/src/reference/docbook/reference/redis.xml
index f21e19c73..ae3166a8e 100644
--- a/docs/src/reference/docbook/reference/redis.xml
+++ b/docs/src/reference/docbook/reference/redis.xml
@@ -34,7 +34,8 @@
explains the abstraction builds on top of the low-level Connection API to handle the
infrastructural concerns and object conversion.
Support Classes - that offer reusable components (built on the aforementioned abstractions) such as
- java.util.Collection backed by Redis as documented in
+ java.util.Collection or Spring 3.1 cache implementation backed by
+ Redis as documented in
For most tasks, the high-level abstractions and support services are the best choice. Note that at any point, one can move between layers - for example, it's very
@@ -404,6 +405,28 @@
As shown in the example above, the consuming code is decoupled from the actual storage implementation - in fact there is no indication that Redis is used underneath. This makes moving from
development to production environments transparent and highly increases testability (the Redis implementation can just as well be replaced with an in-memory one).
+
+
+ Support for Spring Cache Abstraction
+
+ Spring Redis provides an implementation for Spring 3.1 cache abstraction
+ through the org.springframework.data.redis.cache package. To use Redis as a backing implementation, simply add RedisCacheManager to your configuration:
+
+
+
+
+
+
+
+]]>
+
+
+
+