Transaction isolation is the mechanism that makes updates that have not yet been committed invisible to other JADE sessions. Instead, these JADE sessions view the most-recently committed editions of the JADE objects; that is, the way they were without the uncommitted updates.
While a JADE object is being updated, two copies can exist in the JADE object cache: one with and one without the updates. The copy with the updates is visible only to the updating JADE session. Other JADE sessions access the other copy, which does not include the updates.
When a transaction is committed, any older copies of objects in the cache are removed.
JADE automatically provides transaction isolation for JADE objects.