Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@hi...)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-501
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-501
Summary: ODMG: Lifecycle of Database class in Implementation Singleton
Type: Bug
Status: Open
Priority: Major
Project: Hibernate2
Assignee: Gavin King
Reporter: Oliver Gries
Created: Wed, 26 Nov 2003 12:21 AM
Updated: Wed, 26 Nov 2003 9:57 AM
Description:
I'm sorry for posting this again, but it's a bit annoying after every new hibernate relase to add this 2 fixes manually.
Bug (1)
Here is the short solution of this problem allreay posted within Hibernate 1.2.5 (HBI-5).
Solution in Implementation class:
******************************
newTransaction() must not use the local variable database for creating a transaction but the db instance assoc. with the current thread, which gets returned by the currentTransaction() method.
public org.odmg.Transaction newTransaction() {
try {
// old
return new Transaction(database);
// new
return new Transaction(currentDatabase());
}
catch (ODMGException ode) {
throw new ODMGRuntimeException( ode.getMessage() );
}
}
Bug (2)
Allready posted as HB-85. Solution is very easy !!! ;-))
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
