JBoss MicroKernel Core
Small memory footprint - extend behaviour is optionally pluggable.
Backward compatibility with current JMX kernel.
Primary responsibilty is to be the glue between POJOs.
Uses Unified Interceptors to implement any container.
Bootstrap - a helper class for bootstrapping the kernel.
Controller - managed lifecycle/state machine and dependencies.
Registry - holds deployed POJO information.
Configurator - instantiates and glues POJOs together including any container.
Deployer - holds deployment aspects and applies them.
Bus - allows detyped/detaching between POJOs.
Repository - holds metadata about POJOs.
Profile - holds which POJOs are available and whether they should be started.
Provides a simple mechanism to activate the kernel.
The controller is responsible for making sure the POJOs are instantiated, configured and started according to profile, dependencies and system/subsystem/service/subservice configuration/lifecycle.
POJO/Service configurations are added/removed in the controller which then takes over.
Stores information about the deployed POJOs.
Instantiates and configures the POJOs, adding any container.
Holds deployment aspects and applies them when asked to deploy.
Uses the registry to provide detyped/detached invocations, similar to the JMX MBeanServer.
Holds metadata about POJOs, both deployed and available but not deployed.
Defines which Systems, Subsystems, POJOs are deployed and which services are started automatically
or available for manual start.