A simple self-refreshing cache framework for Java
Simple... yes, ordinary I don't think so! Check [How It Works].
It's the central module of the framework.
It's in charge of analyzing the code inside of a @CacheAwareFactory method, caching its result and deciding when and why expire this cache for reflect recent changes on them.
It's requires three kind on component for work:
A core-handler based on a Spring AoP aspect.
It's intercepts all bean's methods annotated with @CacheAwareFactory and performs the caching with and an around-kind aspect.
A core-handler based on a Google Guice module.
It's intercepts all bean's methods annotated with @CacheAwareFactory and performs the caching with and around-kind interception.
A Hibernate persistence-provider, based on a Hibernate's interceptor and a PersistenceProvider implementation.
Notifies the core when a entity's state changes, causing all cached results where that entity took part to be invalidated.
Resolves Hibernate's proxies and transient entities, getting the most recent from the underlying database
A TopLink persistence-provider, based on a TopLink's session customizer and a PersistenceProvider implementation.
Notifies the core when a entity's state changes, causing all cached results where that entity took part to be invalidated.
Resolves TopLink's values holders (proxies) and transient entities, getting the most recent from the underlying database
A EclipseLink persistence-provider, based on a EclipseLink's session customizer and a PersistenceProvider implementation.
Notifies the core when a entity's state changes, causing all cached results where that entity took part to be invalidated.
Resolves EclipseLink's values holders (proxies) and transient entities, getting the most recent from the underlying database
This module lets you use the Ehcache framework as a CacheProvider for the core
This module lets you use your Memcached servers (if you have any) as a CacheProvider for the core