Now that Optimistic locking is done, we need to do some work to fully capitalize on it so that people can use it with Commit 'A' and avoid transactional locking.
XXXXXXXXXXXXXXXX Bill Burke Chief Architect JBoss Group, LLC XXXXXXXXXXXXXXXX > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Alex > Loubyansky > Sent: Monday, January 06, 2003 8:37 AM > To: Muntean Horia > Subject: Re[2]: [JBoss-user] Optimistic locking ported to JBoss-3.2 > > > Hello Muntean, > > Monday, January 06, 2003, 4:43:25 PM, you wrote: > MH> Does it make any sense using commit-option A with "Instance Per > MH> Transaction" container (a.k.a optimistic lock policy)? > > A small note: Instance Per Transaction doesn't mean an optimistic > locking policy will be used. The default locking policy for Instance > Per Transaction is NoLock. > > MH> I mean - when the second tx reaches an already enlisted > entity bean (in > MH> the first tx) I guess the bean data is read from the DB > anyway (and not > MH> from the cache). Is this correct? > > Yes, this is correct. And hence, AFAIK, there is no sense in using > optimistic locking with optimistic locking. > > alex > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
