Hi guys,
I have run into a related issue. I am using a thrid party library which
creates transactions, commits and also performs rollbacks internally. When
ever a transaction is rolledback in the third party library I later see a
hibernate exception in the log file:
org.hibernate.TransactionE
ok, Howard, I added the bug to JIRA.
Regards.
Howard Lewis Ship wrote:
>
> Before making changes, I'm checking on the Hibernate user forum.
>
> http://forum.hibernate.org/viewtopic.php?p=2387715#2387715
>
> Please still add the bug to JIRA.
>
> On Wed, Jun 11, 2008 at 9:53 AM, Howard Lewis
Before making changes, I'm checking on the Hibernate user forum.
http://forum.hibernate.org/viewtopic.php?p=2387715#2387715
Please still add the bug to JIRA.
On Wed, Jun 11, 2008 at 9:53 AM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> Thanks for the heads up.
>
> Looking at the Hibernate sour
Thanks for the heads up.
Looking at the Hibernate source, I can see that this is true, when you
commit() a transaction, the Session's connection to the transaction
(via the JDBCContext) is lost. It seems like, at least for the JDBC
case, the Transaction object should only have begin() invoked onc
