You
can use it with cache-invalidation. Consult the docs.
Cache-invalidation isn't transactional though so shouldn't be used with critical
data. Bela and Harald are implementing a distributed cache for
JB4.
Go on
a bean by bean strategy. If the bean is read-only, than commit-A in
cluster is fine. If the bean is read-mostly and non-critical,
cache-invalidation is fine.
Bill
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 11:58 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Commit Option A & clusters
Hi all,
Does commit option A currently have any meaning in the context of a clustered JBoss instance (since there's no distributed locking and presumably the preload cache is not distributed)?
Dave
