Bela,
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 pu
[Version of JBoss cache shipped with 3.2.5]
Trying to use TreeCache.put(...) and retrieve the return value to check the previous
value. This works all nicely with local cache, but when switched to synchronized
replicated, this method always returns null:
tree.put("/a/b/c", "name", "Ben");
Obje
