Spring 3.1.M1 @Cacheable Doesn’t Evict – A Workaround

Spring 3.1 introduces a new feature to allow methods to be cached and evicted thus allowing resource heavy methods to be avoided where possible. Caching is enabled via the new @Cacheable and @CacheEvict annotations. For full details of Spring caching have a look at Costin Leau’s blog post.

One example of caching would be, for example, database activity. We can apply the @Cacheable annotation to a find operation and then apply the @CacheEvict to an update / delete operation.  In this sense, caching would work much like a second level cache in Hibernate or JPA.

To enable caching on a find method, the method needs to be annotated with the @Cacheable annotation identifying which cache to use.  Spring allows multiple caches to be defined each of which can be backed by a different caching abstraction.

@Cacheable("items")
public Item find(long itemId) {
    Item item = entityManager.find(Item.class, itemId);
    return item;
}

When it is time to invoke the find method, Spring checks in the specified cache to see if the results of the operation have already been cached and if the results can be therefore be returned from cache instead of invoking the method. Spring uses the method arguments as the key, so in this case the itemId parameter.

To evict an entry from the cache when an object is updated in the database, the @CacheEvict annotation can be used.  Again, this annotation takes a parameter identifying which cache to use.

@CacheEvict(value = "items", key = "#item.id")
public void updateItem(Item item) {
    entityManager.merge(item);
}

You can see in this sample code, that Spring Expression Language has been used to define the key for items in the cache.  This is necessary as a long is not being used as the key as in the previous example so cache entries would not be found.

This all looks pretty straightforward, but unfortunately due to bug SPR-8015 it does not work.

To quote the bug report:

“… it's not working because the DefaultKeyGenerator simply hashes the given parameters as is. In case no key attribute is configured (just like in the above example) the parameters will be handed in as single-element-Object[] causing a different hash to be created than if the single object would be handed to the key generator directly”

@Cacheable(value = "items", key = "#itemId")
public Item find(long itemId) {
    Item item = entityManager.find(Item.class, itemId);
    return item;
}

From http://www.davidsalter.co.uk/1/post/2011/05/spring-31m1-cacheable-doesnt-evict-a-workaround.html