[jBoss-Dev] Instance cache and commit option c

[Dan OConnor]

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