ShiftOne Java Object Cache Adaptors

Allows a ShiftOne Cache to be used with a java.util.Map interface. This is a good way to limit an application's exposure to a "proprietary" caching interface.

Map Cache

Allows a java.util.Map to be used with the ShiftOne Cache interface. OSCache policies implement the Map interface, so this also effectively allows an OSCache policy to be used with the ShiftOne interface.

This is an easy way to create a cache that has no max size and no expiration (usually not the best idea - this is what I call a memory leak).

Hibernate Cache Provider

Allows the Hibernate Persistence Service to be configured to use any ShiftOne configured cache. In your hibernate.properties file, set the property hibernate.cache.provider_class to org.shiftone.cache.adaptor.HibernateCacheProvider.

Oro Cache Factory

Oro Cache's don't support node expiration, or even removal, but they are super fast. Not supporting node removal allowed the authors of the Oro caches to keep nodes in an array rather than a linked list (the way most caches do).

If your application doesn't need these features (which ShiftOne caches have) then the Oro Cache's may be a good choice. This factory allows four different Oro policies to be configured.

Swarm Cache

This allows a Swarm ObjectCache to be used with the ShiftOne Cache interface.

EHCache Cache

This allows an "Easy Hibernate" to be used with the ShiftOne Cache interface.

JCS Cache

This allows a JCS "CacheAccess" to be used with the ShiftOne Cache interface.