Do you have specific questions?
The article above gives a pretty good overview of the basic cache and locking choices you would use in various situations.
As for the cache coordination point of view, the key thing to remember is that you can never really have an application that never has stale data. As I'm sure you know, as soon as you read any data from the database, it is potentially stale.
The cache coordination feature simply reduces the likelyhood that data is stale by sharing cache data between applications. It can be will broadcast a list of objects that have been changed and can be configured to either invalidate them in other caches or actually bring the changes over to those caches.
[Message sent by forum member 'tware' (tware)]
http://forums.java.net/jive/thread.jspa?messageID=236825