In another blog post we explained how you can use a new feature of Mule 3.3 to cache data in your Mule flows. Here we look at how to configure Mule to use EHCache to handle the caching part, rather than storing the data in the default InMemoryObjectStore.
Let’s get going. First let’s start by saying that there are millions of different ways to do this… We’ve taken the route of configuring everything through Spring. So just because you configured your EHCache differently, does not mean it’s wrong or ours is better. We prefer this way since Mule integrates very nicely with Spring. Now we have settled that, let’s make a list of what we need to do:
- Define cache manager
- Define cache factory bean
- Create a custom object store
- Define a Mule caching strategy
The first job is to define a cache manager and cache factory bean. Spring provides two very handy classes for this, specific for EHCache, EhCacheManagerFactoryBean and EhCacheFactoryBean. The cache manager just needs to be defined. However on the cache factory bean, you can configure all EHCache details. Such as; time to live, time to idle, when to overflow on disk, the eviction policy, and much more. For more information, you can check the API here or the EHCache website. Also from the cache factory bean, you need to refer back to the cache manager. An example is shown in the following gist:
Once the cache and the cache manager are configured, we need to define a custom object store that uses EHCache to store and retrieve the data. This is very easy to do, we just need to create a new class that implements the standard Mule’s ObjectStore interface, and use EHCache to do the operations. A working custom EHCache object store is shown in the following gist:
As you can clearly see, this object store encapsulates an Ehcache instance. This should be set before we start using this object store. As you can imagine, we will do this through Spring.
The next step is to configure a caching strategy which uses our brand new EHCache object store.
The caching strategy using our custom object store, and in the object store, we are using Spring to inject the cache defined earlier in this blog post.
The rest in Mule can be exactly the same as in the other blog post we explained before.
So here we have shown you how we can use EHCache as the caching engine for the cache scopes provided by Mule 3.3. A reason why you would do this is that with EHCache, you have a very good and proven caching product with a ton of settings that you can exploit and tune for your application.
As a side note, if you have issues with EHCache classloading in Mule, place the EHCache jars inside $MULE_HOME/lib/user rather than in your application.