Details
Description
After update coalescing is executed the elements are put into a HashSet which doesn't necessarily preserves the order in which updates were created.
Activity
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee | Mircea Toma [ mircea.toma ] |
Ken Fyten
made changes -
Fix Version/s | 1.8 [ 10161 ] |
Ken Fyten
made changes -
Fix Version/s | 1.7.3 [ 10162 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #18243 | Wed Jan 28 14:51:36 MST 2009 | mircea.toma | |
Files Changed | ||||
MODIFY
/icefaces/branches/icefaces-1.7/icefaces/core/src/com/icesoft/faces/webapp/command/UpdateElements.java
|
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #18236 | Tue Jan 27 16:32:58 MST 2009 | mircea.toma | |
Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/core/src/com/icesoft/faces/webapp/command/UpdateElements.java
|
Mircea Toma
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [50070000007Bagr] | |
Fix Version/s | 1.8DR#3 [ 10143 ] | |
Assignee | Mircea Toma [ mircea.toma ] |
Mircea Toma
created issue -
Yes, you are right. I thought about implementing the algorithm you mention above. There were a few things that stopped from doing it that way:
a) It can potentially introduce a lot of DOM traversals when coalescing over a larger set of elements.
b) Occurrences of having newer element updates that include older element updates is quite small.
c) Code becomes more complex thus more difficult to maintain.
d) The added increased traffic due to older included updates is relatively small.