Are there alternatives to HiveTranse when using HiveMind?
It first depends on your needs. If you just need JDBC, and you do not mind managing Connections (open, commit, rollback) in your DAO code, then you can perfectly use a pooled DataSource (like jakarta commons-dbcp), declare it as a HiveMind service (this is what HiveTranse suggests for JDBC support), and inject it in your DAO, and, in each DAO method, use the DataSource to get a new Connection, use that Connection and commit it or roll it back. If you just need Hibernate, and you do not mind about automatic transaction management (through declarative transaction demarcation like in EJB), you can choose one of some partial solutions suggested on HiveMind WIKI. But those solutions look more like attempts to integrate Hibernate and do not always provide extended configuration capabilities, or sometimes support only one SessionFactory. Generally those solutions also suffer a lack of documentation. Among these solutions, one is particularly worth a look (and a try): it was developed by Marcu
