Oleg Nitz <on <at> ukr.net> writes: > I am trying to support "long transactions" in OTM. I didn't keep them in mind > before, but now I realized that original Raghu design contains even a special > package - swizzling - which is a way of doing long transactions. > I.e. otmconn.makePersisntent() should work similar to broker.store(): > if exists then update, if doesn't exist then create. Of course, automatic > update of all changes and update via makePersisntent() are mutually > exclusive: only the object which was read inside transaction (say, via > getObjectByIdentity()) *is in transaction*. The object passed to > makePersisntent() is not included in the transaction (unless it is new), > it is just swizzled with transactional object (its fields values are copied to > the transactional object).
Just curious: What does this mean for my latest issue report? Is it an issue in OJB OTM or do I have to modify my code partly? And did you come across the swizzle thing before or after patching the other issues :) Not that I need it immediately, I have some else work to do on my project, but of course updating objects is somewhat important to me :) Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
