All Classes and Interfaces
Class
Description
A single instance is shared between the root host
ApplicationContext (declared in
OsgiSpringConfiguration) and every plugin's curated parent context (PluginApiParentContext
registers the exact same object as a singleton there), mirroring PluginExtensionRegistryImpl's
sharing pattern.Thrown by
PluginManifest.from(Bundle) when a bundle declares itself a Spring plugin
(it has an X-Plugin-Context header) but its manifest is malformed.Discovers Spring plugin bundles via the
PluginManifest contract, builds their child
context via PluginContextFactory, and guarantees deterministic teardown on
removedBundle - including plain bundle.stop() with no uninstall, which fires
synchronously on the calling thread with a fully usable bundle classloader for uninstall,
stop, and framework shutdown alike.Purges the enumerable set of JDK/Spring caches that would otherwise pin a departing plugin's
classloader - a hand-rolled list, after rejecting
ClassLoaderLeakPreventor (stale since 2016, and its API assumes a
ServletContextEvent rather than an arbitrary ClassLoader).A production safety net, independent of the CI-only leak-gate test suite: after
teardown(com.xebialabs.xlrelease.osgi.impl.PluginRuntime) completes, watches whether a plugin's classloader actually
becomes collectible within a bounded delay, and logs at ERROR - with the plugin's
symbolic name and install/teardown timestamps - only once it is sure.Thrown by
PluginContextFactory.build(org.osgi.framework.Bundle, com.xebialabs.xlrelease.osgi.impl.PluginManifest, org.springframework.context.support.GenericApplicationContext) when construction fails after the child
ApplicationContext was created - carries the partially-built PluginRuntime so
the caller can route cleanup through the same PluginTeardown used for normal removal,
rather than PluginContextFactory closing it internally.Builds a plugin's child
AnnotationConfigApplicationContext from a PluginManifest
+ Bundle, parented to the curated PluginApiParentContext.A single instance is shared between the root host
ApplicationContext (declared in
OsgiSpringConfiguration) and every plugin's curated parent context (PluginApiParentContext
registers the exact same object as a singleton there) - not two copies, one shared reference,
so a plugin-side registration is immediately visible to host-side queries.Push counterpart to
PluginExtensionRegistryImpl.extensions(Class): a host component that wants to maintain
externally-visible derived state (e.g.OSGi-service feeder for
PluginExtensionRegistryImpl: a bundle that contributes a
Declarative Services component (rather than a Spring plugin context, see
PluginContextFactory) implementing one of HostExtensionPointCatalog's
interfaces is discovered here and registered into the same registry, under the same
Bundle-SymbolicName key, as any Spring-plugin-context extension.The manifest-header contract a bundle must satisfy to be recognized as a "Spring plugin" by
the host:
Everything the host needs to reference a running plugin instance: the OSGi bundle it came
from, its parsed manifest, and its child Spring context.
The single, strictly-ordered, fully idempotent teardown procedure used by every plugin removal
path - this is the load-bearing safety mechanism of the entire OSGi plugin platform.