主要記錄關鍵和有坑的地方html
前提:java
一、SpringBoot+shiro已經集成完畢,若是沒有集成,先查閱以前的Springboot2.0 集成shiro權限管理redis
二、redis已經安裝完成spring
三、redis客戶端使用Lettuce,這也是sprinboot2.0後默認的,與jedis的區別,自行百度apache
四、json使用springboot默認的json
1、依賴緩存
<dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-cache</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-data-redis</artifactId> </dependency>
//在用使用shiro的狀況下集成redis,能夠帶這個依賴,shiro-redis已經實現了shiro的redis緩存和session管理
//若是shiro和redis集成可是不交互,能夠不引入,能夠自定義 <dependency> <groupId>org.crazycake</groupId> <artifactId>shiro-redis</artifactId> <version>3.1.0</version> </dependency>
鏈接池:springboot
<!--鏈接池,redis依賴--> <dependency> <groupId>org.apache.commons</groupId> <artifactId>commons-pool2</artifactId> </dependency>
必須註銷:session
<!--與reids緩存衝突-->
<!--<dependency>-->
<!--<groupId>org.springframework.boot</groupId>-->
<!--<artifactId>spring-boot-devtools</artifactId>-->
<!--<optional>true</optional>-->
<!--</dependency>-->
2、Application.ymlapp
spring:
...省略
cache:
redis:
time-to-live: 60s
type: redis
redis:
host: 127.0.0.1
port: 6379
password: 123456@abc.com
timeout: 10000
lettuce:
pool:
max-idle: 10
max-active: 10
min-idle: 5
max-wait: 10000
database: 0
3、redis配置類
@Configuration @EnableCaching //開啓Springboot緩存,重要!!! public class RedisConfig extends CachingConfigurerSupport { @Resource private LettuceConnectionFactory lettuceConnectionFactory; private Duration timeToLive = Duration.ofSeconds(60); @Bean //在沒有指定緩存Key的狀況下,key生成策略 public KeyGenerator keyGenerator() { return new KeyGenerator() { @Override public Object generate(Object target, Method method, Object... params) { StringBuffer sb = new StringBuffer(); sb.append(target.getClass().getName()); sb.append(method.getName()); for (Object obj : params) { sb.append(obj.toString()); } return sb.toString(); } }; } // 緩存管理器 使用Lettuce,和jedis有很大不一樣 @Bean public CacheManager cacheManager() {
//關鍵點,spring cache的註解使用的序列化都從這來,沒有這個配置的話使用的jdk本身的序列化,實際上不影響使用,只是打印出來不適合人眼識別 RedisCacheConfiguration config = RedisCacheConfiguration.defaultCacheConfig() .serializeKeysWith(RedisSerializationContext.SerializationPair.fromSerializer(keySerializer()))//key序列化方式 .serializeValuesWith(RedisSerializationContext.SerializationPair.fromSerializer(valueSerializer()))//value序列化方式 .disableCachingNullValues()
.entryTtl(timeToLive);//緩存過時時間 RedisCacheManager.RedisCacheManagerBuilder builder = RedisCacheManager.RedisCacheManagerBuilder .fromConnectionFactory(lettuceConnectionFactory) .cacheDefaults(config) .transactionAware(); return builder.build(); } /** * RedisTemplate配置 在單獨使用redisTemplate的時候 從新定義序列化方式 */ @Bean public RedisTemplate<String, Object> redisTemplate(LettuceConnectionFactory lettuceConnectionFactory) { // 設置序列化 Jackson2JsonRedisSerializer<Object> jackson2JsonRedisSerializer = new Jackson2JsonRedisSerializer<Object>( Object.class); ObjectMapper om = new ObjectMapper(); om.setVisibility(PropertyAccessor.ALL, JsonAutoDetect.Visibility.ANY); om.enableDefaultTyping(ObjectMapper.DefaultTyping.NON_FINAL); jackson2JsonRedisSerializer.setObjectMapper(om); // 配置redisTemplate RedisTemplate<String, Object> redisTemplate = new RedisTemplate<String, Object>(); redisTemplate.setConnectionFactory(lettuceConnectionFactory); RedisSerializer<?> stringSerializer = new StringRedisSerializer(); redisTemplate.setKeySerializer(stringSerializer);// key序列化 redisTemplate.setValueSerializer(jackson2JsonRedisSerializer);// value序列化 redisTemplate.setHashKeySerializer(stringSerializer);// Hash key序列化 redisTemplate.setHashValueSerializer(jackson2JsonRedisSerializer);// Hash value序列化 redisTemplate.afterPropertiesSet(); return redisTemplate; } private RedisSerializer<String> keySerializer() { return new StringRedisSerializer(); } private RedisSerializer<Object> valueSerializer() { // 設置序列化 Jackson2JsonRedisSerializer<Object> jackson2JsonRedisSerializer = new Jackson2JsonRedisSerializer<Object>( Object.class); ObjectMapper om = new ObjectMapper(); om.setVisibility(PropertyAccessor.ALL, JsonAutoDetect.Visibility.ANY); om.enableDefaultTyping(ObjectMapper.DefaultTyping.NON_FINAL); jackson2JsonRedisSerializer.setObjectMapper(om); return jackson2JsonRedisSerializer; //或者使用GenericJackson2JsonRedisSerializer //return new GenericJackson2JsonRedisSerializer(); } }
在自定義序列化過程,GenericJackson2JsonRedisSerializer和Jackson2JsonRedisSerializer大部分時候表現沒有區別,實際上若是對象中有LinkedHashMap時候,後者會出錯,這個之前坑了我好久,自我懷疑了好久。
建議使用GenericJackson2JsonRedisSerializer來序列化。
GenericJackson2JsonRedisSerializer和Jackson2JsonRedisSerializer都有一個問題,沒法反序列化接口的動態代理類,緣由應該是動態代理類沒有缺省構造函數,對JPA的自定義結果集支持很差,對Page分頁支持很差。
4、在service上使用緩存,具體Springboot的Cache註解百度上不少。
@CacheConfig(cacheNames = "user") public interface UserService { @Cacheable(key = "'userName'.concat(#userName)") User findByUserName(String userName); }
5、必須修改Shiro的AuthorizingRealm,這裏也是最坑的地方
public class MyShiroRealm extends AuthorizingRealm { @Resource @Lazy //就是這裏,必須延時加載,根本緣由是bean實例化的順序上,shiro的bean必需要先實例化,不然@Cacheable註解無效,理論上能夠用@Order控制順序 private UserService userService; //權限信息,包括角色以及權限 @Override protected AuthorizationInfo doGetAuthorizationInfo(PrincipalCollection principals) { 略 } /*主要是用來進行身份認證的,也就是說驗證用戶輸入的帳號和密碼是否正確。*/ @Override protected AuthenticationInfo doGetAuthenticationInfo(AuthenticationToken token) throws AuthenticationException { 略 } }
6、實體中若是有java8time,諸如LocalDateTime,redis緩存反序列化的時候會失敗,必須在實體中指定json序列化和反序列化的類@JsonDeserialize和@JsonSerialize
@JsonDeserialize(using = LocalDateTimeDeserializer.class) @JsonSerialize(using = LocalDateTimeSerializer.class) @DateTimeFormat(pattern = "yyyy-MM-dd HH:mm:ss") //格式化前臺頁面收到的json時間格式,不指定的話會變成缺省的"yyyy-MM-dd'T'HH:mm:ss" @JsonFormat(pattern = "yyyy-MM-dd HH:mm:ss") private LocalDateTime createTime;//建立時間 @JsonDeserialize(using = LocalDateDeserializer.class) @JsonSerialize(using = LocalDateSerializer.class) @DateTimeFormat(pattern = "yyyy-MM-dd") @JsonFormat(pattern = "yyyy-MM-dd") private LocalDate expiredDate;//過時日期
暫時就是這些關鍵點和關鍵坑,記錄,否則確定忘記。