Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.1.0.RC1
-
Fix Version/s: 4.3
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Tomcat 8, all browsers
Description
When using the showcase ace:tree > selection demo it was noticed that selected values were not always returned in the same order, depending on the server that the app was deployed on. For example the order was the same on tomcat 8 and glassfish 4, but different with wildfly 10.
As per Ken "The underlying data structure being used to store the selected items does not guarantee the order they are returned in. In order to improve this for automation purposes, we should use a different structure that does guarantee the order. "
As per Ken "The underlying data structure being used to store the selected items does not guarantee the order they are returned in. In order to improve this for automation purposes, we should use a different structure that does guarantee the order. "
Activity
Liana Munroe
created issue -
Liana Munroe
made changes -
Field | Original Value | New Value |
---|---|---|
Description |
When using the showcase ace:tree > selection demo it was noticed that selected values were not always returned in the same order, depending on the server that the app was deployed on. For example the order was the same on tomcat 8 and glassfish 4, but different with wildfly
As per Ken "The underlying data structure being used to store the selected items does not guarantee the order they are returned in. In order to improve this for automation purposes, we should use a different structure that does guarantee the order. " |
When using the showcase ace:tree > selection demo it was noticed that selected values were not always returned in the same order, depending on the server that the app was deployed on. For example the order was the same on tomcat 8 and glassfish 4, but different with wildfly 10.
As per Ken "The underlying data structure being used to store the selected items does not guarantee the order they are returned in. In order to improve this for automation purposes, we should use a different structure that does guarantee the order. " |
Ken Fyten
made changes -
Fix Version/s | 4.2 [ 12870 ] |
Ken Fyten
made changes -
Assignee | Arturo Zambrano [ artzambrano ] |
Ken Fyten
made changes -
Fix Version/s | 4.3 [ 13096 ] | |
Fix Version/s | 4.2 [ 12870 ] |
Arturo Zambrano
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #52002 | Tue Oct 10 13:54:54 MDT 2017 | art.zambrano | |
Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/ace/component/src/org/icefaces/ace/model/tree/NodeStateMap.java
|
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
r52002: changed underlying data structure in NodeStateMap from HashMap to LinkedHashMap, which is an implementation of the Map interface with predictable iteration order