From 5eb3695967a0fa58bc6f1494308b06888a8cdcd1 Mon Sep 17 00:00:00 2001
From: Rob Winch <rwinch@gopivotal.com>
Date: Wed, 7 Jan 2015 14:39:26 -0600
Subject: [PATCH] Fix Javadoc formatting for RedisOperationsSessionRepository

---
 .../RedisOperationsSessionRepository.java     | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/spring-session/src/main/java/org/springframework/session/data/redis/RedisOperationsSessionRepository.java b/spring-session/src/main/java/org/springframework/session/data/redis/RedisOperationsSessionRepository.java
index 1e30452..14737f6 100644
--- a/spring-session/src/main/java/org/springframework/session/data/redis/RedisOperationsSessionRepository.java
+++ b/spring-session/src/main/java/org/springframework/session/data/redis/RedisOperationsSessionRepository.java
@@ -71,7 +71,7 @@ import org.springframework.util.Assert;
  * command</a>. An example of how each session is stored can be seen below.
  * </p>
  *
- * {@code HMSET spring:session:sessions:<session-id> creationTime 1404360000000 maxInactiveInterval 1800 lastAccessedTime 1404360000000 sessionAttr:<attrName> someAttrValue sessionAttr2:<attrName> someAttrValue2}
+ * <pre>HMSET spring:session:sessions:&lt;session-id&gt; creationTime 1404360000000 maxInactiveInterval 1800 lastAccessedTime 1404360000000 sessionAttr:&lt;attrName&gt; someAttrValue sessionAttr2:&lt;attrName&gt; someAttrValue2</pre>
  *
  * <p>
  * An expiration is associated to each session using the <a
@@ -80,7 +80,7 @@ import org.springframework.util.Assert;
  * . For example:
  * </p>
  *
- * {@code EXPIRE spring:session:sessions:<session-id> 1800}
+ * <pre>EXPIRE spring:session:sessions:&lt;session-id&gt; 1800</pre>
  *
  * <p>
  * The {@link RedisSession} keeps track of the properties that have changed and
@@ -90,19 +90,19 @@ import org.springframework.util.Assert;
  * would be executed upon saving:
  * </p>
  *
- * {@code
- *     HMSET spring:session:sessions:<session-id> sessionAttr2:<attrName> newValue
- *     EXPIRE spring:session:sessions:<session-id> 1800
- * }
+ * <pre>
+ *     HMSET spring:session:sessions:&lt;session-id&gt; sessionAttr2:&lt;attrName&gt; newValue
+ *     EXPIRE spring:session:sessions:&lt;session-id&gt; 1800
+ * </pre>
  *
  * Each session expiration is also tracked to the nearest minute. This allows a
  * background task to cleanup expired sessions in a deterministic fashion. For
  * example:
  *
- * {@code
- *     SADD spring:session:expirations:<expire-rounded-up-to-nearest-minute> <session-id>
- *     EXPIRE spring:session:expirations:<expire-rounded-up-to-nearest-minute> 1800
- * }
+ * <pre>
+ *     SADD spring:session:expirations:&lt;expire-rounded-up-to-nearest-minute&gt; &lt;session-id&gt;
+ *     EXPIRE spring:session:expirations:&lt;expire-rounded-up-to-nearest-minute&gt; 1800
+ * </pre>
  *
  * <p>
  * The background task will then use these mappings to explicitly request each key.