Date: 2004-12-06T02:33:38
   Editor: JeanFrancoisPoilpret <[EMAIL PROTECTED]>
   Wiki: Jakarta HiveMind Wiki
   Page: HibernateSupport
   URL: http://wiki.apache.org/jakarta-hivemind/HibernateSupport

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -99,3 +99,6 @@
  6. Provide full access to Hibernate "Session" power (no limited interface of 
it): one idea is to leveredge Hibernate knowledge of users base. This means, 
for instance, that in my DAO implementation classes I shall get access to a 
service (injected by Hivemind) that implements Session interface. I think using 
a "HibernateTemplate" as in Spring is not as good as it seems, because it can 
"hide" some useful Hibernate possibilities.
  7. Allow configuration fo which exceptions must rollback transactions (Nice 
to have?): I find this idea interesting, but it should not be mandatory, I mean 
this could make the configuration hard to read and maintain. I think there 
should be acceptable defaults if we do not provide any config for it.
  8. Possibility to map checked HibernateException into RT exceptions (Nice to 
have, maybe out of scope): Actually, I am the one who initiated such a request. 
But having it means creating a "Hibernate Template" like in Spring, which means 
selecting a subset of Hibernate methods, possibly removing some not so often 
used -but still useful- capabilities. After thinking again about that problem, 
I had an idea of a more generic way to handle the problem of checked Vs. 
unchecked exceptions. But this is not related to the hibernate integration in 
Hivemind (although developers might use it in this context). Since I just 
started with this idea I will expose it later in a separate thread.
+
+Jean-Francois Poilpet:
+Finally, almost all the points above have been reached in 
[http://hivetranse.sourceforge.net HiveTranse] Open Source project, which is a 
generic transaction framework for HiveMind, which currently supports JDBC and 
Hibernate, and is planned to support JTA in the near future.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to