Console commands

When the Aggregator bundle is activated, it registers a CommandProvider that responds to commands entered in the OSGi console beginning with the token aggregator. The CommandProvider supports the following commands:

Note: The Aggregator supports the use of the felix gogo command processor if it is available. When using this command processor, the syntax for invoking Aggregator commands is slightly different, using a colon instead of a space between the service identifier (aggregator) and the command token. For example, the command to list the active servlets would be aggregator:list instead of aggregator list.

Command	Description
aggregator help	Displays a list of Aggregator commands and their function
aggregator list	Lists the names of the currently active servlets. In order for a servlet to be a member of this list, it must have been started.
aggregator reloadconfig <servlet>	Reloads the server-side AMD config for the specified servlet.
aggregator validatedeps <servlet> [clean]	Validates the module dependency graph by by scanning module last modified dates looking for new/removed/modified modules and updates the dependency graph as needed.  If the clean parameter is specified, then the dependency graph is built from scratch and all the modules will be opened and parsed to determine each module's dependencies.
aggregator getdeps <servlet> <module> [<feature list>]	Lists the expanded set of dependencies for the specified module on the specified servlet.  If a feature list is specified, then the feature list will be used in resolving module dependency chains involving modules using the has! loader plugin.  Features are specified as a space separated list of feature names.  If the feature name is preceded by a !, then the feature value is false, otherwise, the value is true.
aggregator clearcache <servlet>	Clears the Aggregator cache for the specified servlet.
aggregator dumpcache <servlet> <regexp>	Dumps details about the Aggregator cache for the specified servlet.  If a regular expression is specified, then only cache entries matching the regular expression will be displayed.
<code">aggregator getoptions <servlet>	Lists the currently defined Aggregator options and their values.
aggregator setoption <servlet> <propname> <propvalue>	Sets the specified option to the specifaied value.  The new value is persisted to aggregator.properties in the home directory of the user that launched the server, and so will persist across server restarts.
aggregator getconfig <servlet>	Displays the string representation of the evaluated server-side config
aggregator processrequesturl <servlet> <query-args>	Processes the request with the specified query args as if the request had been issued via HTTP to the servlet. The query args are specified without the leading '?'. The reply from this command is the HTTP status of the response. This command is provided in order to facilitate the generation of a cache-primer bundle by build automation, avoiding the need to stand up an HTTP client in order to process the requests. This command was introduced in version 1.3
aggregator createcachebundle <servlet> <bundle-symbolic-name> <bundle-filename>	Creates a [cache-primer bundle](Caching#the-cache-primer-bundle) with the specified symbolic name at the specified file location. The bundle will contain the contents of the Aggregator cache at the time that the command is issued. This command was introduced in version 1.3

_Note: some implementations of the OSGi servlet bridge delay activation of servlet bundles until after the first HTTP request directed to the servlet is received. If the aggregator does not seem to be responding to console commands, try sending a request to an aggregator servlet to activate the bundle. Alternatively, you can use the start console command to activate the aggregator._