Renderer Component Module
Renderer Component plugins allow you to add additional processors when converting wiki markup to HTML.
- For more information about plugins in general, read Confluence Plugin Guide.
- To learn how to install and configure plugins (including macros), read Installing a Plugin.
- For an introduction to writing your own plugins, read Writing Confluence Plugins
This document concerns plugging renderer components into Confluence. The implementation of renderer components themselves is not documented.
Renderer component plugins were added to Confluence to make certain development tasks easier inside Atlassian. They are documented here for Atlassian developers, and for the sake of completeness, but we do not recommend customers add their own plugins to this area. The wiki markup rendering process is quite fragile, and simple changes can have wide-reaching effects.
In other words, you're on your own here.
Defining a Renderer Component Plugin
Here's a sample atlassian-plugin.xml fragment:
- The key is the required plugin module key, which must be unique within the plugin.
- The name is the required display name for the plugin.
- The class is the required class name for the renderer component implementation.
- The weight number is required, and determines the order in which renderer component plugins are run over the wiki markup. Components are run from lowest to highest weights
Implementing a Renderer Component Plugin
The class referred to by the module descriptor must implement one of the following interfaces:
This allows you to provide either a component directly, or a factory that can be used to instantiate more complex components. If you are using a factory, you can provide arbitrary parameters that will be passed to the factory when the component is instantiated:
These parameters will be passed into the factory's instantiate method as a Map<String, String>.