[
http://jira.jboss.com/jira/browse/JBCACHE-546?page=all ]
Manik Surtani closed JBCACHE-546.
---------------------------------
Resolution: Won't Fix
There aren't that many methods now, as this has been trimmed quite a bit. A separate
class will only make things more confusing since locks are acquired on a per-node basis.
Move lock related operations to a separate utility, such as NodeLock
--------------------------------------------------------------------
Key: JBCACHE-546
URL:
http://jira.jboss.com/jira/browse/JBCACHE-546
Project: JBoss Cache
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Affects Versions: 1.3.0.GA
Reporter: Elias Ross
Assigned To: Manik Surtani
Fix For: 2.0.0.ALPHA2, 2.0.0.GA
This is to reduce the amount of methods in Node to keep them fairly succinct.
The lock in a Node itself could be package-protected so that interactions must happen
through this class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira