Hi,
I'm trying to debug/fix Hibernate messages like
"org.hibernate.NonUniqueObjectException: a different object with the same
identifier value was already associated with the session: "... and I find the
default exception logging in AbstractSaveEventListener#performSave not
sufficient. I've ad
I started down the path of changing the Type interface to have the
majority of methods accept a SessionFactoryImplementor. That is
something I would like to avoid if possible. Why? Well, this ended up
affecting the vast majority of the entire codebase; which in turn meant
increasing the footprin
Hehe. That obviously will not work ;)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 20, 2006 9:13 AM
To: Steve Ebersole
Cc: hibernate-devel@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [Hibernate] Connection Handling in Isolater
Hello
Hello Steve,
thanks for the quick reply. Since I didn't notice you've moved to SVN I've
checked the "latest" version from CVS (via the web CVS View) ;-)
Rgds
Holger
Steve Ebersole wrote:
>Yep. This has already been fixed for almost two months now in SVN ;)
>
>-Original Message-
>From:
Yep. This has already been fixed for almost two months now in SVN ;)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, July 20, 2006 8:35 AM
To: hibernate-devel@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Subject: [Hibernat
I think this is fixed already, have you checked the latest version?
[EMAIL PROTECTED] wrote:
> Hi all,
>
> I think org.hibernate.engine.transaction.Isolater is not handling connections
> properly:
>
> The method JdbcDelegate is currently implemented as follows:
>
> public static class JdbcD
Hi all,
I think org.hibernate.engine.transaction.Isolater is not handling connections
properly:
The method JdbcDelegate is currently implemented as follows:
public static class JdbcDelegate implements Delegate {
...
public void delegateWork(IsolatedWork w
