Blueprint Developer Manual / Using Plugins

loading table of contents...

Blueprint Developer Manual / Version 2406.1

Table Of Contents

Using Plugins

To use your plugins, you have to provide the paths to the directories containing plugins for the application with the Spring property plugins.directories.

If you put a zipped plugin in there, it will be automatically extracted on the first start of the application and the extracted directory is used afterwards. See Section 4.3, “Build and Run the Applications” for how to configure and run CoreMedia Java applications.

Normally, if a plugin could not be started, an ERROR is logged and the application continues without the respective plugin. With the property plugins.required-plugins it is possible to abort the application start if one of the listed plugins is missing or could not be started.

Plugin Manager Properties

`plugins.directories`
Type	`List<String>`
Description	The directories from where plugins are loaded.
`plugins.directory`
Type	`String`
Description	The directory from where plugins are loaded.
Deprecation	This property has been deprecated and will be removed in a future version. Use `directories` instead. Reason: Introduction of new list-valued property 'directories'
`plugins.required-plugins`
Type	`List<String>`
Description	A list of ids for plugins that are required. If one of these plugins is missing or could not be started, the application startup will be aborted. This property is only effective when 'plugins.directories' is set.

Table 4.1. Plugin Manager Properties

Search Results

Table Of Contents