Hi, Winson Quock wrote: > Hello, > > This is a general question that applies to OJB, JDO, ODMG or other object > persistence systems. > > If my objects which are stored into persistence storage also implement > Serializable interface, then I could pass them to a remote servers via RMI. > But I have a few problems I must deal with: (for this discussion I assume all > participating servers are engaged in the same distributed transaction.) > > 1. If my object is clean and not modified, I may still have to pass all the > data over to the remote server rather than the persistence id or the primary > keys. > > 2. Yet I cannot just pass the persistence id because my local copy is modified > and I want to pass the updated values over. > > 3. If both the local and remote servers modify the objects, the modifications > are neither synchronized nor communicated.
IMHO these are two transactions, not one! > We have two different copies of > the same objects in the same transaction. I think OJB's locking mechanism and > the new OTM only work at transaction-level but there is no way to ensure > intra-transaction distributed object consistence. > This scenario is not handled by OJB. You might: 1. use two transaction to isolate the operation of the two servers 2. implement your own distributed transaction manager cheers, Thomas > How should I address these problems? > > Thanks. > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
