[GEODE-8067] ClassLoader Isolation

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Abandoned
• Component/s: client/server
• Labels: pull-request-available
• Assignee: Udo Kohlmeyer
• Reporter: Udo Kohlmeyer
• Created: 04/May/20 20:49
• Updated: 12/Jan/21 23:05
• Resolved: 12/Jan/21 23:05

Description

This is the root jira for the first pass implementation for ClassLoader Isolation

Issue Links

• links to: GitHub Pull Request #5356
• links to: GitHub Pull Request #5357
• links to: GitHub Pull Request #5660

Sub-Tasks

• Move services related to classloader-isolation to geode-common-services.: Closed
• Create ModuleService Interface: Closed
• Create BootstrappingService Interface: Resolved
• Create ManagementService Interface: Resolved
• Create JBoss-Modules ModuleService Implementation - loadModule: Resolved
• Implement loadService on JBossModuleService: Resolved
• Implement unloadModule in JBossModuleService: Resolved
• Create BootStrappingService Implementation: Resolved
• Create JBoss Module to load jar with manifest and classpath: Resolved
• Gradle configuration to create manifests for all Geode jars: Closed
• Integrate ModuleService into Geode: Resolved
• Add ability to reconfigure Log4j when going from App ClassLoader to JBoss: Resolved
• Change the module collection in BootStrappingServiceImpl to have unique module entries: Resolved