Description Rüdiger Herrmann 2011-04-29 14:21:29 EDT

The current SessionStoreImpl has several issues:
* checks that prevent null-arguments being passed in are missing for these methods: getAttribute(), removeAttribute(), setAttribute()
* getAttributeNames() should operate on a safe copy, instead it operates directly on the internal data structure which may lead to ConcurrentModificationExceptions
* access to the attributes field is not always synchronized (i.e. createAttributeNameEnumeration)
* fields that represent internal state (i.e. bound, aboutUnbound) are not accessed in a thread-safe way
* the SessionStoreEvent should be a good citizen among the event state classes and inherit from EventObject
* handling exceptions that occur in valueBound and valueUnbound should be handled in the same way. Currently, they are not handled at all or handled differently