You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/04/16 08:43:43 UTC
[jira] Created: (DIRRMS-20) Add a ThreadLocal to carry the current transaction
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRRMS-20
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRRMS-20
Summary: Add a ThreadLocal to carry the current transaction
Type: Task
Status: Open
Priority: Major
Project: Directory RMS
Components:
Berkeley JE
Assignee: Alex Karasulu
Reporter: Alex Karasulu
Created: Thu, 15 Apr 2004 11:41 PM
Updated: Thu, 15 Apr 2004 11:41 PM
Description:
We want JE to operate using transactions but we want to make sure this is done without chewing up our interfaces making them more specific to the JE implementation. The best way to go about doing this is to setup the transaction for every high level RMS-JE operation and add it to a ThreadLocal before starting the opertation. This way the transaction is propagated down to all operations. So we need to make sure these operations pick up the transaction from the ThreadLocal rather than using null.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (DIRRMS-20) Add a ThreadLocal to carry the current transaction
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Alex Karasulu
Date: Wed, 28 Apr 2004 10:45 AM
The was added then was removed because it did work for passing the Application to the binding when the list() operations were used. A factory is needed so we made the binding depend on an Application factory. The binding is also passed into the JeRoleDAO as a constructor argument.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DIRRMS-20
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DIRRMS-20
Summary: Add a ThreadLocal to carry the current transaction
Type: Task
Status: Closed
Priority: Major
Resolution: FIXED
Project: Directory RMS
Components:
Berkeley JE
Assignee: Alex Karasulu
Reporter: Alex Karasulu
Created: Thu, 15 Apr 2004 11:41 PM
Updated: Wed, 28 Apr 2004 10:45 AM
Description:
We want JE to operate using transactions but we want to make sure this is done without chewing up our interfaces making them more specific to the JE implementation. The best way to go about doing this is to setup the transaction for every high level RMS-JE operation and add it to a ThreadLocal before starting the opertation. This way the transaction is propagated down to all operations. So we need to make sure these operations pick up the transaction from the ThreadLocal rather than using null.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira