Sharing Uncommitted Persistent Objects

JADE detects if the sharing of uncommitted persistent objects changes across processes and raises the appropriate exceptions should this occur. JADE enforces the starting, performing, and finalizing of persistent transactions on a single node (that is, a client or a server node). All of the update operations of the transaction must occur in the same node that started the transaction.

JADE does not attempt to synchronize the client cache and server cache when accessed by the same process. As a rule, you should not rely on changes made to persistent objects or a non-committed transaction being visible to server methods executed during that interval. (For details about object editions, see "Using Object Editions" under "Unlocking Objects", in Chapter 6. See also "Overview", in that chapter.)