almost forgot...
ok if Object id is
new OptimisticKey(id, tx);
then the cache implementation doesn't need to be aware of anything and the
interface is the same :)))
dum da daa dei do do!!
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Dan OConnor
|Sent: Wednesday, November 15, 2000 1:40 PM
|To: jBoss Developer
|Subject: [jBoss-Dev] Instance cache and commit option c
|
|
|Hi guys,
|
|This might be a stupid question, but I'll ask anyway. It seems that
|the InstanceCache interface, which gets EnterpriseContexts based
|on the primary key of the bean, forestalls the possibility of using
|Commit Option C and deferring concurrency control to the
|database. Wouldn't you need to add the current transaction to
|interface methods such as:
|
| public EnterpriseContext get(Object id)
| throws RemoteException, NoSuchObjectException;
|
|Otherwise how could you have two instances of the same object
|existing concurrently in different transactions? With this interface,
|it seems as if concurrency control would always be done by the
|container. Maybe this is handled implicitly (or more likely I'm
|missing something)...
|
|-Dan
|
|
