Class PluginManifest
java.lang.Object
com.xebialabs.xlrelease.osgi.spring.PluginManifest
The manifest-header contract a bundle must satisfy to be recognized as a "Spring plugin" by
the host:
Bundle-SymbolicName: com.example.myplugin X-Plugin-Context: com.example.myplugin.MyPluginConfiguration X-Plugin-Prefix: my-plugin # reserved for a future HTTP layer; omit in v1
Identity for host-side keying is always Bundle-SymbolicName, never the prefix - the
prefix exists only to namespace URLs and has no reason to exist before an HTTP layer introduces
them. It is therefore Optional here and its absence is not an error in v1.
-
Field Details
-
CONTEXT_HEADER
- See Also:
-
PREFIX_HEADER
- See Also:
-
-
Method Details
-
pluginContextClassName
-
prefix
-
from
- Returns:
Optional.empty()ifbundlehas noX-Plugin-Contextheader - it is not a Spring plugin, zero cost, matchingBundleTracker.addingBundle's contract of returningnullto skip tracking.- Throws:
InvalidPluginManifestException- ifX-Plugin-Contextis present but blank, or its class cannot be loaded from the bundle's own classloader, or ifX-Plugin-Prefixis present but does not match the required pattern. A missing prefix is never an error in v1.
-