Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
webconsole-3.1.2
-
None
Description
Currently if one wants to develop a configuration printer, the developed component has to import/implement the configuration printer interface. This ties the bundle to the web console bundle - which makes it more complicated to implement such extensions than it should be.
For plugins we already have the dynamic registration without requiring to implement a web console specific interface by searching for servlet services with specific properties.
We could implement something similar for configuration printers:
We search for all services having at least these properties:
- felix.webconsole.label
- felix.webconsole.title
- felix.webconsole.configprinter.modes
If any service has these three properties and has a method printConfiguration(PrintWriter) or printConfiguration(PrintWriter, String (=mode)), this service is added as a configuration printer. This method is searched by reflection.