Based on my reading of the Blue whitepaper and some of the comments on these forums, it appears that selective invalidation of cached entity beans across a cluster of EJB servers is not currently supported - that you can set an expiration time for a cached entity, but if you change one "copy" of an entity in one VM within a cluster, it doesn't automagically propogate and invalidate the other "copies" of the entity.
(It appears that this capability will be in 4.0)
Is my assessment true, or is this cross-VM invalidation capability available today in 3.0.4?
Thanks,
John
