December 2006 - jboss-jira - Jboss List Archives

Buy impotence drugs with us much cheaper

by Sonny Greenwood

little about the substance of it. And this is one cause why so the Lord: well may this be a mystery to the natural, for it is a flesh, bone of his bone; they talk, they walk with him, as a spirit.� Hence it happens, that so many, even of the most communion, when the Lord's love flows in upon your souls, his daily practice to �keep under his body, and bring it into disciple of Christ, to make always, even unto the 3end of the practice, he is guided more by the world, than by the word of delivers believers from the guilt of it: Christ is their Savior, to all elect sinners � they are made to know themselves, so Savior, when we will not endeavor sincerely to approve Sonny Greenwood

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-544) Remove AbstractNode superclass

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-544?page=all ] Manik Surtani closed JBCACHE-544. --------------------------------- Resolution: Won't Fix > Remove AbstractNode superclass > ------------------------------ > > Key: JBCACHE-544 > URL: http://jira.jboss.com/jira/browse/JBCACHE-544 > 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.GA > > > If AbstractNode is not used anywhere, it's basically more code to maintain. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-546) Move lock related operations to a separate utility, such as NodeLock

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-546?page=all ] Manik Surtani updated JBCACHE-546: ---------------------------------- Fix Version/s: 2.0.0.ALPHA2 Description: 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. was: 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. > 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.GA, 2.0.0.ALPHA2 > > > 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-545) Consider removing TreeCache, parent, and name

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-545?page=all ] Manik Surtani updated JBCACHE-545: ---------------------------------- Fix Version/s: 2.0.0.ALPHA2 > Consider removing TreeCache, parent, and name > --------------------------------------------- > > Key: JBCACHE-545 > URL: http://jira.jboss.com/jira/browse/JBCACHE-545 > 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.GA, 2.0.0.ALPHA2 > > > "name" is redundant with respect to Fqn, which contains the name already > parent can be obtained in O(log(n)) time with a TreeCache instance > TreeCache can be passed in from the user to methods that require it -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-547) Remove TreeNode and DataNode interfaces

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-547?page=all ] Manik Surtani updated JBCACHE-547: ---------------------------------- Fix Version/s: 2.0.0.ALPHA2 Description: Possibly both of them to a single, small interface, but keep the method count in the conservative 5-10 method range. (was: Possibly both of them to a single, small interface, but keep the method count in the conservative 5-10 method range.) > Remove TreeNode and DataNode interfaces > --------------------------------------- > > Key: JBCACHE-547 > URL: http://jira.jboss.com/jira/browse/JBCACHE-547 > 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.GA, 2.0.0.ALPHA2 > > > Possibly both of them to a single, small interface, but keep the method count in the conservative 5-10 method range. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-541) Create one true Node class; that's lean and mean and stuff

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-541?page=all ] Manik Surtani updated JBCACHE-541: ---------------------------------- Fix Version/s: 2.0.0.ALPHA2 Description: There are TreeNode, AbstractNode, DataNode and Node as basically Node types. I'm thinking as a simplification in design, that a single Node.java class that's concrete and has a fairly comprehensive but non-bloated method set. This will save on memory and reduce confusion. Also, having interfaces for data classes is fairly difficult, as you end up having so many data accessor methods that it is hard to maintain. The end result would be something like: public class Node { private Fqn fqn; // name is Fqn.getLast() private Map attributes; private Map children; private Lock lock; } Note: No parent, no reference to TreeCache (clients can supply it if they want, no need for every node to have a reference), external locking is done on the Lock, internal locking is done on "this". For all the locking that needs done, create a NodeLock utility class that has these methods, including ten versions of printLocks. :-) I'll create a list of tasks, some possibly now without breaking compatibility, some for later (like post 2.0?) was: There are TreeNode, AbstractNode, DataNode and Node as basically Node types. I'm thinking as a simplification in design, that a single Node.java class that's concrete and has a fairly comprehensive but non-bloated method set. This will save on memory and reduce confusion. Also, having interfaces for data classes is fairly difficult, as you end up having so many data accessor methods that it is hard to maintain. The end result would be something like: public class Node { private Fqn fqn; // name is Fqn.getLast() private Map attributes; private Map children; private Lock lock; } Note: No parent, no reference to TreeCache (clients can supply it if they want, no need for every node to have a reference), external locking is done on the Lock, internal locking is done on "this". For all the locking that needs done, create a NodeLock utility class that has these methods, including ten versions of printLocks. :-) I'll create a list of tasks, some possibly now without breaking compatibility, some for later (like post 2.0?) All a part of the Node/Cache object model refactoring > Create one true Node class; that's lean and mean and stuff > ---------------------------------------------------------- > > Key: JBCACHE-541 > URL: http://jira.jboss.com/jira/browse/JBCACHE-541 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > Assigned To: Manik Surtani > Fix For: 2.0.0.GA, 2.0.0.ALPHA2 > > > There are TreeNode, AbstractNode, DataNode and Node as basically Node types. > I'm thinking as a simplification in design, that a single Node.java class that's concrete and has a fairly comprehensive but non-bloated method set. This will save on memory and reduce confusion. Also, having interfaces for data classes is fairly difficult, as you end up having so many data accessor methods that it is hard to maintain. > The end result would be something like: > public class Node > { > private Fqn fqn; // name is Fqn.getLast() > private Map attributes; > private Map children; > private Lock lock; > } > Note: No parent, no reference to TreeCache (clients can supply it if they want, no need for every node to have a reference), external locking is done on the Lock, internal locking is done on "this". > For all the locking that needs done, create a NodeLock utility class that has these methods, including ten versions of printLocks. :-) > I'll create a list of tasks, some possibly now without breaking compatibility, some for later (like post 2.0?) -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-542) Fix initialization of Node.IdentityLock to actually lazy create

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-542?page=all ] Manik Surtani updated JBCACHE-542: ---------------------------------- Fix Version/s: 2.0.0.ALPHA2 > Fix initialization of Node.IdentityLock to actually lazy create > --------------------------------------------------------------- > > Key: JBCACHE-542 > URL: http://jira.jboss.com/jira/browse/JBCACHE-542 > 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.GA, 2.0.0.ALPHA2 > > > Although the JavaDoc says it's lazily created, it's created every time -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-543) Consider synchronized(this) instead of a separate lock

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-543?page=all ] Manik Surtani updated JBCACHE-543: ---------------------------------- Fix Version/s: 2.0.0.ALPHA2 > Consider synchronized(this) instead of a separate lock > ------------------------------------------------------ > > Key: JBCACHE-543 > URL: http://jira.jboss.com/jira/browse/JBCACHE-543 > 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.GA, 2.0.0.ALPHA2 > > > This will save one object per node, not a big deal but something. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-595) Merge API interfaces

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-595?page=all ] Manik Surtani updated JBCACHE-595: ---------------------------------- Fix Version/s: 2.0.0.ALPHA2 > Merge API interfaces > -------------------- > > Key: JBCACHE-595 > URL: http://jira.jboss.com/jira/browse/JBCACHE-595 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.SP1 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Blocker > Fix For: 2.0.0.GA, 2.0.0.ALPHA2 > > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > * Merge TreeCacheListener, EnhancedTreeCacheListener, add an API to pass in data > * Merge CacheLoader + ExtendedCacheLoader -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-859) Known failures in 2.0.0.Alpha1 need cleaning up

by Manik Surtani (JIRA)

Known failures in 2.0.0.Alpha1 need cleaning up ----------------------------------------------- Key: JBCACHE-859 URL: http://jira.jboss.com/jira/browse/JBCACHE-859 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.ALPHA2 These include: org.jboss.cache.buddyreplication.BuddyAssignmentStateTransferTest org.jboss.cache.eviction.ConcurrentEvictionTest org.jboss.cache.eviction.MRUAlgorithmTest org.jboss.cache.loader.deadlock.ConcurrentCreationDeadlockTest -- 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

17 years, 10 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006