[JBoss JIRA] Created: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
9:18 p.m.
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: http://jira.jboss.com/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
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
9:28 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
[ http://jira.jboss.com/jira/browse/JBCACHE-841?page=all ]
Elias Ross updated JBCACHE-841:
-------------------------------
Attachment: OrderedNode.java
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: http://jira.jboss.com/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
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
4:21 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
[ http://jira.jboss.com/jira/browse/JBCACHE-841?page=all ]
Manik Surtani updated JBCACHE-841:
----------------------------------
Fix Version/s: 3.0.0
Affects: [Documentation (Ref Guide, User Guide, etc.),
Compatibility/Configuration]
Complexity: Medium
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: http://jira.jboss.com/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
Fix For: 3.0.0
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
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
9:54 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
[ http://jira.jboss.com/jira/browse/JBCACHE-841?page=comments#action_12417661 ]
Manik Surtani commented on JBCACHE-841:
---------------------------------------
Leaning towards an approach where you can specify if a node contains ordered data or
ordered children. By default this is false. Can be a cfg option to enable this cache
wide.
Node.isDataOrdered(); // tests if the data map is ordered
Node.isChildrenOrdered(); // tests if the child map is ordered
Node.setDataOrdered(boolean b); // locks the map, and then copies out the existing data
map into a new ordered map structure
Node.setChildrenOrdered(boolean b); // similar to above
SortedNode sn = Node.getSortedNode(); // retrieves a sub-interface of Node that has added
methods. Throws an exception if the node doesn't have sorted data or children.
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: http://jira.jboss.com/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
Fix For: 3.0.0
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
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
10:41 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
[ http://jira.jboss.com/jira/browse/JBCACHE-841?page=comments#action_12417667 ]
Elias Ross commented on JBCACHE-841:
------------------------------------
The initial use case was supporting such collections as SortedMap in POJO cache. SortedMap
implementations typically allow for ordering to be done in two ways: By using natural
ordering of the elements, e.g. Strings ordered lowercase first; or through a Comparator
instance. Although I'm thinking that this "setting" could be transient (not
persisted or replicated), for POJO Cache it probably needs to be stored someplace. POJO
Cache can probably take care of setting it in a related Node.
But in general, users would naturally expect the Node ordering property to be made
persistent and replicated. I'm thinking that JBoss Cache would need a separate data
map that's for meta-data like this.
Initially, it might be easiest to simply have ordering defined by Region and only support
natural ordering.
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: http://jira.jboss.com/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
Fix For: 3.0.0
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
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
10:50 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
[ http://jira.jboss.com/jira/browse/JBCACHE-841?page=comments#action_12417670 ]
Manik Surtani commented on JBCACHE-841:
---------------------------------------
Good point about making this replicated/persisted. We already encode some information
this way; a generic way to do this for all such flags would be good. A MetaData object,
for example, that could be encoded in the node's data map under an internal key or
something like that.
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: http://jira.jboss.com/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assigned To: Manik Surtani
Fix For: 3.0.0
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
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
3:55 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
[
https://jira.jboss.org/jira/browse/JBCACHE-841?page=com.atlassian.jira.pl...
]
Manik Surtani commented on JBCACHE-841:
---------------------------------------
also see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=140184
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: https://jira.jboss.org/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assignee: Manik Surtani
Fix For: 3.0.0.GA
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:25 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
[
https://jira.jboss.org/jira/browse/JBCACHE-841?page=com.atlassian.jira.pl...
]
Manik Surtani updated JBCACHE-841:
----------------------------------
Fix Version/s: 3.0.0.BETA1
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: https://jira.jboss.org/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assignee: Manik Surtani
Fix For: 3.0.0.BETA1, 3.0.0.GA
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:39 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys
[
https://jira.jboss.org/jira/browse/JBCACHE-841?page=com.atlassian.jira.pl...
]
Manik Surtani updated JBCACHE-841:
----------------------------------
Fix Version/s: 3.1.0
(was: 3.0.0.GA)
(was: 3.0.0.BETA1)
No way this is going to go into 3.0.0 unless it is a filthy hack. :-)
Be able to set the internal ordering of child nodes and data keys
-----------------------------------------------------------------
Key: JBCACHE-841
URL: https://jira.jboss.org/jira/browse/JBCACHE-841
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Elias Ross
Assignee: Manik Surtani
Fix For: 3.1.0
Attachments: OrderedNode.java
I believe that this issue is required to resolve JBCACHE-166 satisfactorily.
But it would also be a useful (and easily added) feature for JBossCache 2.0.
The attached .java file explains two additional methods to add.
The internal implementation would likely need to rely on the JDK1.6
java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change
to other code that rely on iteration to work on concurrently modified sets.
As JDK 1.6 is new, this might require use of
http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support
from the jbossretro to change these JDK1.6 classes to use the backport for 1.5.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5735
days inactive
6371
days old
8 comments
3 participants
participants (3)
-
Elias Ross (JIRA) -
Elias Ross (JIRA) -
Manik Surtani (JIRA)