Why does ContextFactory duplicate the by-classloader indexing of DefaultSingletonService?

[David Jencks <da...@yahoo.com>]

ContextFactory maintains its own map of classloader to ContextService instance, but if it doesn't find one it gets it from the singleton service which is already by default indexed by classloader.  Is there some point to maintaining the two maps?

Since indexing by classloader doesn't work in many possible ee environments (details later), and the singleton service can be replaced by one that does, I'd prefer it if the extra map in ContextFactory could be removed.

thanks
david jencks