Page History

...

Use Cases

Scenario 1:  Apache Geode starts with no ClassLoaderService Implementation explicitly defined

Expected behavior: Apache Geode will use the DefaultClassLoaderService as the ClassLoaderService

Scenario 2: Apache Geode starts with custom ClassLoaderService implementation

Expected behavior:  Apache Geode will use custom ClassLoaderService implementation for all ClassLoader service functionality

Changes and Additions to Public Interfaces

This addition requires that in some cases new public constructors and new public methods for various components / modules within Geode to be added. The existing constructors and methods will be kept and delegated to the configured or defaulted ClassLoaderService implementation. 

In many cases, component will be constructed with the ClassLoaderService as a field in order to avoid having to unnecessarily add it to existing function / service calls.

Performance Impact

No anticipated performance impact.

Backwards Compatibility and Upgrade Path

No expected backward compatibility impact. As this is an addition to the code base, all existing public constructors, interfaces and service methods will be kept and delegated to the correct constructor and service call.

Prior Art

What would be the alternatives to the proposed solution? What would happen if we don’t solve the problem? Why should this proposal be preferred?

...