Hi!
Dan OConnor wrote:
> 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)...
You are indeed correct, and this specific fix is something I've been
meaning to do but haven't gotten around to (partly because noone is yet
working on an optimistic cache). Add it to BugZilla please.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
