It is probably a good idea to get a connection from Hibernate Session but
there is one question remains: Will transaction demarcation work in this
case?
Jean-Francois Poilpret wrote:
Hello Aleksej,
No, unfortunately, with current HiveTranse version, you cannot have both
Hibernate and JDBC. This might (not 100% sure yet) change in next 0.7.0
version (but this is not for the very short term).
Why don't you get the JDBC Connection from an Hibernate Session. Wouldn't it
work for your situation? In addition, that would solve the problem of
sharing the DataSource between JDBC and Hibernate.
Hope this can help.
Cheers
Jean-Francois
-----Original Message-----
From: Aleksej [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 20, 2006 3:48 PM
To: hivemind-user@jakarta.apache.org
Subject: Hivetranse: Is it possible to use Hivetranse with JDBC connections
and hibernate at one time?
Using Hivetranse for Hibernate everything workds fine, but when
I dropped in hivetranse.jdbc.jar into classpath I got following exception:
Error at
jar:file:/E:/apache/tomcat1/webapps/enadmin/WEB-INF/lib/hivetranse.jdbc.jar!
/META-INF/hivemodule.xml,
line 13, column 34: Module hivetranse.jdbc has contributed a instance
builder to service point hivetranse.core.TransactionService, which
conflicts with an existing contribution by module hivetranse.hibernate3.
The duplicate contribution has been ignored.
Currently I have this Hivetranse jars in my classpath:
hivetranse.core.jar, hivetranse.exceptions.jar,
hivetranse.hibernate3.jar,hiveutils.jar, hivetranse.jdbc.jar.
IN general, I want to prevent Hibernate3 Sessions and normal JDBC
Connections to use the the same
one DataSource, accessed by JNDI name. For both I want to apply a
Transaction Demarcation interceptor.
Is it possible at all?
