DJ>> Does this
DJ>> implementation result in each JBoss jta transaction getting its own copy of
DJ>> any entity it accesses?
AL> Here you caught me... it occurs it's not so great.
AL> Using "Standard CMP 2.x EntityBean" container entities are shared
AL> between transactions. So, if some tx changes some field, another tx
AL> will see it.
AL> Using "Instance Per Transaction 2.x EntityBean" doesn't solve it
AL> either.
I believe it is fixed now. So, in "Instance Per Transaction 2.x
EntityBean" container configuration each tx deals with its own copy of
the entity.
This is the configuration:
<container-configurations>
<container-configuration extends="Instance Per Transaction CMP 2.x EntityBean">
<container-name>optimistic container</container-name>
<locking-policy>org.jboss.ejb.plugins.lock.JDBCOptimisticLock</locking-policy>
<!-- overriding:
<locking-policy>org.jboss.ejb.plugins.lock.NoLock</locking-policy> -->
</container-configuration>
</container-configurations>
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
