Declarative caching services are enabled by Spring AOP.
Wanghy-Cache provides two advises:
org.wanghy.cache.interceptor.caching.CachingInterceptor
.
org.wanghy.cache.interceptor.flush.CacheFlushInterceptor
.Non-invasive framework. Applications using Wanghy-Cache do not have to extend particular classes or implement particular interfaces.
Caching services can be defined completely in the Spring
configuration file. Optionally, caching services can be enabled
using source-level metadata, providing a similar programming model
to .NET ServicedComponents
.
Wanghy-Cache automatically generates the key of the
entries stored in the cache by combining the hash codes of
the advised method and its arguments. Custom key generators can be
created by implementing the interface
org.wanghy.cache.keyCacheKeyGenerator
.
Instead of imposing the use of a particular cache implementation, Wanghy-Cache lets you choose a cache provider that better suites the needs of your project. The supported cache providers are:
Because Wanghy-Cache is based on interfaces, rather than classes, it is easy to extend in order to add support for other cache providers.
Comprehensively Test Coverage. See the Clover test report.
For more information, see the Getting Started Guide, Change Report, Road Map, and the JavaDocs.
Caching services can be used to improve application performance. A very common example is the caching of data retrieved from a database. Even though ORM frameworks such as iBATIS and Hibernate already provide built-in caching, Wanghy-Cache can be useful when: