Duplicate object prevention policy

[Jan Röhrich]

Hello list,

imagine the following case: A method supports the lookup of objects
using a name -> object mapping. The objects are stored in a map but can
easily be newly created instead of performing a real lookup. Shall we
perform this real lookup even if the newly created object is equal to
the original object in terms of Object.equals().

Concrete?: Have a look at
java.awt.datatransfer.SystemFlavorMap#decodeDataFlavor(). This is only
one appearance of this problem (out of many many).

Jan

signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil