Memory data store is not order preserving
-----------------------------------------
Key: GEOT-1258
URL: http://jira.codehaus.org/browse/GEOT-1258
Project: GeoTools
Issue Type: Bug
Components: core main
Affects Versions: 2.3.1
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 2.3.2, 2.4.M2
A Geoserver user noted the inline feature rendering order is not predictable.
This is because inline features are put into a memory data store, and the
latter is not order preserving, because uses a HashMap instead of a
LinkedHashMap. I'm also wondering if a map is really needed, it ensures no two
features have the same id, but it seems a little overkill (its memory
requirements are far higher than a plain arraylist).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
