Thomas, Thanks for the clarification on JTA and Unit of Work. I was looking for a Java standard for the transaction mechanism. Since you mention JDO has a Unit of Work concept and it is a Java standard I decided to look at its Unit of Work API. It is the PersistenceManager interface. I'm not sure if I could use this as my "abstract transaction mechanism" since it may contain operations that are not found in other O/R persistence frameworks such as OJB or TopLink. I'll have to research these other popular Unit of Work APIs to determine this.
-Jerome -----Original Message----- From: Thomas Mahler [mailto:thma@;apache.org] Sent: Thursday, November 14, 2002 1:32 AM To: OJB Users List Subject: Re: Patterns/Architecture info for OJB apps? Hi Jerome, Jerome Jacobsen wrote: > Thanks very much. I will look into the book and SODA. > > However, I'm confused about the need for "an abtract transaction mechanism". > Isn't JTA just that? Good O/R tools provide object level transactions (aka Unit of work). Jdo and ODMG Transactions are examples for this concept. This concept is also covered in Fowlers book... A Unit of work provides methods to register objects to it and to mark them for insert, update or delete. Neither JDO nor ODMG Transaction are JTA transactions. JTA is only used to integrates with app server managed datasources. But this is quite a different conceptual level. cheers, Thomas -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
