hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta HiveMind Wiki] Updated: HibernateSupport
Date Tue, 05 Oct 2004 15:06:08 GMT
   Date: 2004-10-05T08:06:08
   Editor: JamesCarman <>
   Wiki: Jakarta HiveMind Wiki
   Page: HibernateSupport

   no comment

Change Log:

@@ -82,6 +82,7 @@
 This makes me better understand the way it has been implemented in Spring: one Template class
that combines all Session API + other common API from other classes, but it seems to me that
it reduces the possibilities of Hibernate for the developer.
 -- James Carman
 Maybe we should start up a new page to discuss a generic transaction framework for HiveMind.
 We should come up with a set of common transaction services which can be implemented in different
"flavors" (i.e. HiveMind, JTA, JDBC, JDO, etc.).  This framework would include the transaction
interceptor which would allow for configuration of transaction requirements (requires new,
required, a la EJB) and for rollback exception types (aside from the default, which includes
only runtime exceptions).  Any thoughts?
 = Requirements =

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message