...

The goal of the Web Console is to support as big a range of Web Browsers as possible. As it stands now, Firefox (versions 2 and 3), Opera and Internet Explorer (versions 6 and 7) seem to be capable of using the Web Console. Should you encounter any problems with your particular browser, please report an issue for the Web Console in our issue tracking system (JIRA).

Beginning with Release 1.2.8 the Web Console is using JQuery to enhance the user experience. This should also help in keeping browser support on the broadest possible basis.

Extending the Web Console

Top

The Web Console can be extended by registering an OSGi service for the interface javax.servlet.Servlet with the service property felix.webconsole.label set to the label (last segment in the URL) of the page. The respective service is called a Web Console Plugin or a plugin for short.

To leverage the rendering of the common header and footer around the plugin's data area, the plugin must extend the abstract org.apache.felix.webconsole.AbstractWebConsolePlugin class. This is very simple but it creates a wire from the plugin bundle to the Web Console bundle, which may not be desired. One reason is that updating the web console may cause the plugin bundle to be refreshed, which does not make any sense from an application point of view). For this reason, we are currently investigating how to support plugins with header and footer rendering without requiring to extend the AbstractWebConsolePlugin class.

Such plugins, will be able to access information from the AbstractWebConsolePlugin which is now available to extensions of that class through method calls.

Further issues with respect to extensions:

• It is currently not yet resolved how to add resources in plugins.
• Many requirements exist to be able to customize some areas of look and feel of the console; most notably the logo and vendor links.

Issues

Top

Should you have any questions using the Web Console, please send a note to one of our Mailing Lists.

...