Closed
Description
(And removing in next major release.)
Pros:
- we anyway have now
<T> Set<T> getSecondaryResources(Class<T> expectedType);
which return all the resource from all the related event sources of that type. - We should move users to use just one event source per type, since it's more efficient.
- The event sources and resource cached are now tightly coupled, but this is not necessarily a good thing, might event change in the future. So ideally this interface should not know about the event sources and their names (what we might not even need then in the future)
- We could remove the quite complex code related to this logic:
Const:
- this still might be useful to distinguish or make it easier to find a cached resource.