The Parser service of the Core Library maintains a common set of commands so that bundles in the OSGi framework can retrieve these commands and redirect them to miscellaneous clients.
Overview
The Parser Service has two usage aspects:
It allows you to extend the content of the command inventory with new pluggable commands. Pluggable commands can be implemented by any bundle wishing to export some of its functionality or internal information to console users (for example, the Core Bundle provides a number of commands for controlling bundles and listing information, the HTTP Bundle lists the aliases registered in the HTTP Service, etc.)
A pluggable commands set is responsible for the execution of the commands it records in the Parser Service. In addition, it should organize its commands in a separate group and may support shortcuts.
To make the Parser Service recognize a pluggable commands entry, register it as a Pluggable Commands service in the OSGi framework.
It allows you to obtain its currently stored commands and map their execution to client applications (Client) that use a specified communication output – such as local output, Telnet, etc.
When the end user issues a command (client input), the command receiver redirects it to the Parser Service (received command).
The Parser Service calls the Pluggable Commands service responsible for the command, which executes it according to the client input.
The Parser Service sends the result from the execution to the client via the specified communication stream.
For more information check the Developer Guide – Console Commands.
Registering Bundle
This service is registered by Core Commands Bundle.
System Properties
The System Properties of the Parser Service are provided in the Setup Guide.
