Blueprint Developer Manual / Version 2401
Table Of Contents
Each plugin has its own Spring application context. However, in order to
implement your feature, you might need some services from the application, for example
the CapConnection.
The applications of CoreMedia Content Cloud expose dedicated sets of beans for usage in plugins, which are provided as Spring
configuration classes that you can import in your plugin's configuration class.
These configuration classes are annotated with com.coremedia.cms.common.plugins.plugin_base.BeansForPlugins.
Other plugins can also provide such configuration classes. To access them, you have to add these plugins as dependencies.
Beans for Plugins Reference
The following BeansForPlugins are currently available:
CommonBeansForPluginsConfiguration Available in all apps with extension points. Dependency:
<dependency> <groupId>com.coremedia.cms</groupId> <artifactId>common.beans-for-plugins-container</artifactId> <scope>provided</scope> </dependency>
CommerceBeansForPluginsConfiguration Provides access to commerce beans. Available in plugins for commerce-enabled apps. Dependency:
<dependency> <groupId>com.coremedia.blueprint.base</groupId> <artifactId>middle.bpbase-lc-beans-for-plugins-container</artifactId> <scope>provided</scope> </dependency>
HeadlessBlueprintBaseBeansForPluginsConfiguration Provides access to Headless Server beans. Available in
headless-serverplugins. Dependency:<dependency> <groupId>com.coremedia.blueprint.base</groupId> <artifactId>bpbase-headless-server-core</artifactId> <scope>provided</scope> </dependency>
FeedbackHubBeansForPluginsConfiguration Provides access to Feedback Hub beans. Available in
studio-serverplugins. Dependency:<dependency> <groupId>com.coremedia.cms</groupId> <artifactId>feedback-hub-api</artifactId> <scope>provided</scope> </dependency>
The API documentation of the BeansForPlugins classes shows the
actual beans they provide.
