Hi all, I have some changes to the Map and Set serializers that I think are worth using. Firstly I have added to the map serialiser the ability to use non-string data as the keys. This does not break compatibility with existing code, but on non string keys, will convert them to JSON using the serialiser. I find it useful, as it allows for callable references to be keys.
The SetSerializer I have changed to use different keys. Previously it only allowed the keys to be strings. I alter this to use the hashcode() method as the key when the table is a hashtable, or merely a counter otherwise. This allows sets to be iterated through much more simply and, in the case of ordered sets, allows them to work properly. They are both attached and have been working for me for a while. If anyone has some suggestions or reasons why I shouldn't add it, please let me know! Cheers, Will
SetSerializer.java.patch
Description: Binary data
MapSerializer.java.patch
Description: Binary data
_______________________________________________ Jabsorb-dev mailing list [email protected] http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev
