Changing the name of a collection item corrupts the collection cache

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Add a named item to a collection
2. Change the name of the item added
3. Remove the item

What is the expected output? What do you see instead?

Expect item to be removed
Instead item remains by reference of old name

Please use labels and text to provide additional information.

This behavior is a result of the implementation which favors performance
over this kind of accuracy.  The presumption is that you wouldn't need to
change the names of items in a collection, but this becomes a problem when
some of the functionality of the framework requires that names be edited. 
This is generally limited to the names of objects not within collections,
but nevertheless increases the risk of names being edited from within
collections.

To access objects by name without the caching, the entire collection array
will need to be traversed rather than depending on a hash look up (the cache).

Original issue reported on code.google.com by senocu...@gmail.com on 10 Feb 2010 at 9:19

[GoogleCodeExporter]

Original comment by senocu...@gmail.com on 10 Feb 2010 at 9:24

• Changed state: New

[GoogleCodeExporter]

Original comment by senocu...@gmail.com on 17 Feb 2010 at 5:01

• Changed state: Started