Hi, We're currently reviewing O/R mapping tools. Since the JDO and OTM implementations are not yet fully functional, and ODMG doesn't provide us with the necessary flexibility, we are primarily interested in the Persistence Broker API. I took a look and have some questions: - Does PB has JTA support, and if so how (I saw a combination of OTM/ODMG/PB classes that put together may provide this functionality - but it's just a guess)? - Does PB supports distributed transactions? Can we not perform DB commit? - We want to be able to catch OptimisticLock exceptions in our code before commiting. Can we flush all changes to the DB WITHOUT committing (and thus trigger OptimisticLock exceptions)? - Is the cache transcational (does it discard all changes made to objects in a rolled-back transaction)? - Can we do read-optimistic locking to avoid stale reads (i.e. doing a null UPDATE just to make sure the version hasn't changed)? - Can we map the same fields to different objects (and how does the cache behave if it's possible)? - Can we map an object using several mappings and switch them at runtime (i.e. moving an object from one table to another when its state changes)? - How all these subjects affect the cache?
Any help would be appreciated. Regards, Tal -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
