Shulou(Shulou.com)06/02 Report--

This article introduces the reason why @ Cacheable does not work and how to solve the problem of bean unserialization. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

Why @ Cacheable doesn't work: bean is not serialized

In SpringMVC, the return value of serviceImpl method is cached in redis, and @ Cacheable is found invalid.

The returned Blogger custom entity class does not implement the serialization interface

Unable to save to redis. Just implements the Serializable interface!

@ Cacheable annotated cache does not work

The key points for the use of @ Cacheable annotated cache: the correct annotated cache configuration. The annotated object is hean managed by spring, and the caller is another object. In some cases, annotated caching doesn't work: the same bean internal method call, subclass calls to methods with cached annotations in the parent class, and so on. The latter does not work because the cache aspect must be proxied to be valid, so you can use CacheManager manually to get the cache effect.

The right way to use annotated caching

Important point: @ Cacheable (value= "must use a cache name already defined by ehcache.xml, otherwise an exception will be thrown")

@ Componentpublic class CacheBean {@ Cacheable (value= "passwordRetryCache", key= "# key") public String map (String key) {System.out.println ("get value for key:" + key); return "value:" + key;} public String map2 (String key) {return map (key);} @ RunWith (SpringJUnit4ClassRunner.class) @ ContextConfiguration (locations = {"classpath:cache.xml"}) public class CacheTester {@ Autowired CacheManager cacheManager @ Autowired CacheBean cacheBean; @ Test public void cacheManager () {System.out.println (cacheManager);} @ Test public void cacheAnnotation () {cacheBean.map ("a"); System.out.println (cacheManager.getCacheNames ());}}

Output:

Get value for key: a

[authorizationCache, authenticationCache, shiro-activeSessionCache, passwordRetryCache]

Slightly modified to allow ehcache to automatically add cache space based on default configuration. Custom MyEhCacheCacheManager is provided here.

In another modification, no cache is cached when the defined cache space is not found, or all caches are turned off. The trap cache can be closed by removing the cacheManagers configuration.

Calling similar or parent methods has no caching effect: you can choose to use CacheManager manually.

RunWith (SpringJUnit4ClassRunner.class) @ ContextConfiguration (locations = {"classpath:cache.xml"}) public class CacheTester {@ Test public void cacheAnnotation () {this.map ("a"); this.map ("a");} @ Cacheable (value= "passwordRetryCache", key= "# key") public String map (String key) {System.out.println ("get value for key:" + key); return "value:" + key;}}

Or another way: it is possible to manually use a proxy to call similar methods.

Public class CacheBean {@ Autowired ApplicationContext applicationContext; @ Cacheable (value= "passwordRetryCache", key= "# key") public String map (String key) {/ / method cannot be private, otherwise there will be no cache effect System.out.println ("get value for key:" + key); return "value:" + key;} public String map2 (String key) {CacheBean proxy = applicationContext.getBean (CacheBean.class); return proxy.map (key) / / here you can use proxy to call map to cache, but if you call map directly, there is no cache}} the reason why @ Cacheable does not work and how to solve the problem of bean non-serialization is shared here. I hope the above content can be helpful to you and you can learn more. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.