THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- ClassLoader Isolation
- Module Code visibility
- Library and Framework usage freedom
- Usage of different versions of code and libraries in the JVM at the same time
- Simplified modular experience w.r.t modular code deployment maintenance
draw.io Diagram
draw.io Diagram | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The bootstrapping implementation is "simple". At this time, all that the LifecycleService will do is
The deployment of custom code, like gfsh deploy jar, will be handled by the ModuleService. The ModuleService will load the deployed jar into its own ClassLoader with a dependency on the Apache Geode system. That way the deployed custom code will still have access to the Apache Geode's public API's, but without being exposed to its libraries.
...