I just verified this works on the latest version of JBossCache (CVS head), which I'm going to release this week (JBossCache 1.1).
I'm going to backport this to JBoss 3.2.x, but for now you should be able to just take JBossCache 1.1 and use it with 3.2.x out of the box.
thanks for your quick response. I had one more question regarding the atomicity of the put(...) call. Can I assume put on a JGroups replicated object would have the same semantics as a local collection with respect to concurrency, i.e. is it guaranteed that in the event of a concurrent put by two different JVMs the return value will reflect the previous value in synchronized order? I assume this is the case and I do not need to use transactions?
No, this is not guaranteed; you need TXs for this (at least across VMs, locally we sync on the data on access)