caching - Spring 3.1 @Cacheable - method still executed - Stack Overflow
In proxy mode (which is the default), only external method calls coming in through the proxy are intercepted. This means that self-invocation, in effect, a method within the target object calling another method of the target object, will not lead to an actual caching at runtime even if the invoked method is marked with @Cacheable - considering using the aspectj mode in this case.
and
Method visibility and @Cacheable/@CachePut/@CacheEvict
When using proxies, you should apply the @Cache* annotations only to methods with public visibility.
- You self-invoke someMethod in the same target object.
- Your @Cacheable method is not public.
Read full article from caching - Spring 3.1 @Cacheable - method still executed - Stack Overflow
No comments:
Post a Comment