Chapter 1. General Information

1.1.

What is JBoss Cache?

JBoss Cache is a replicated and transactional cache. It is replicated since multiple JBoss Cache instances can be distributed (either within the same JVM or across several JVMs whether they reside on the same machine or on different machines on a network) and data is replicated across the whole group. It is transactional because a user can configure a JTA compliant transaction manager and make the cache operation transactional. Note that the cache can also be run without any replication; this is the local mode.

Currently, JBoss Cache consists of two components: a generic cache (implemented internally as org.jboss.cache.TreeCache ) and a POJO cache (implemented internally as org.jboss.cache.aop.PojoCache ). TreeCache is a tree-structured cache that provides replication and transaction context, while PojoCache extends the functionality of TreeCache but behaves as a true object cache providing transparent and finer-grained object mapping into internal cache.

1.2.

Who are the JBoss Cache developers?

JBossCache has been developed by Bela Ban, Ben Wang, Harald Gliebe, Manik Surtani and Brian Stansberry. Manik is the lead on JBoss Cache and Ben is the lead on PojoCache.

1.3.

What is the license for JBoss Cache?

JBoss Cache is licensed under LGPL .

1.4.

Where can I download JBoss Cache?

The JBoss Cache product download page has prebuilt binaries as well as source distributions. You can also grab snapshots from the JBoss CVS repository (see this wiki page ) - the module name is JBossCache

1.5.

How do I build JBoss Cache from CVS sources?

To build, do sh build.sh jar . This will produce jboss-cache.jar in the dist/lib directory. Or if you want to build the standalone package, do sh build.sh dist this will produce dist/jboss-cache-dist.zip Note that you will need to use JDK 5.0 to build the distribution. You can still use the binaries you build with J2SE 1.4.x though.

1.6.

Which JVMs are supported by JBoss Cache?

JBoss Cache has been tested and supported on J2SE 1.4.x and JDK 5.0. On jboss-3.2 CVS tree, it also compiles on JDK1.3, but there is no official support for this version and using this is not recommended.

1.7.

From JBoss Cache 1.3.0 onwards, there is a new directory lib-50 , what is it?

From JBoss Cache 1.3.0 onwards, we support the use of Java 5 annotations, used by PojoCache. As a result, there are jboss-aop-jdk50.jar and jboss-cache-jdk50.jar that are needed to work with the Java 5 annotations. You will need to replace jboss-aop.jar and jboss-cache.jar in the lib directory with the -jdk50 versions if you intend to use PojoCache, Java 5 and annotations.

1.8.

How do I know the version of JBoss Cache that I am using?

Since release 1.2, you can check the jar version by running: java -jar jboss-cache.jar org.jboss.cache.Version .

1.9.

Can I run JBoss Cache outside of JBoss Application Server?

Of course! JBoss Cache comes in two flavors:

  • Integrated with JBoss Application Server as an MBean service.

  • Standalone, that can run in any Java EE server such as BEA WebLogic or IBM Websphere. Of course, it can also run in a standalone Java process (i.e., outside Java EE context).

1.10.

Where can I report bugs or problems?

Please report any bugs or problems to JBoss Cache User Forum .