Author: marrs
Date: Wed Mar 4 10:57:41 2015
New Revision: 1663932
URL: http://svn.apache.org/r1663932
Log:
More layout fixes.
Modified:
felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/tutorials/leveraging-the-shell.mdtext
Modified:
felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/tutorials/leveraging-the-shell.mdtext
URL:
http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/tutorials/leveraging-the-shell.mdtext?rev=1663932&r1=1663931&r2=1663932&view=diff
==============================================================================
---
felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/tutorials/leveraging-the-shell.mdtext
(original)
+++
felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager-4/tutorials/leveraging-the-shell.mdtext
Wed Mar 4 10:57:41 2015
@@ -32,44 +32,37 @@ __List all dependency manager components
Sample output
-```
-[9] dm.demo
- [6] dm.demo.Probe(type=radiation) unregistered
- dm.demo.Sensor service required unavailable
- [7] dm.demo.Probe(type=humidity) registered
- [9] dm.demo.impl.Dashboard unregistered
- dm.demo.Probe (type=temperature) service required available
- dm.demo.Probe (type=radiation) service required unavailable
- dm.demo.Probe (type=humidity) service required available
- dm.demo.Probe (type=pressure) service required available
- [5] dm.demo.Probe(type=temperature) registered
- [8] dm.demo.Probe(type=pressure) registered
-```
-All components are listed including the dependencies and the availability of
these dependencies. The top level element is the bundle and below are the
components registered with that bundle's bundle context. The lowest level is
that of the component's dependencies.
-
-```
-[bundleid] bundle
- [component id] component interfaces (service properties)
- dependency <availability>
-```
-
-The following flags can be used to tailor the output.
+ [9] dm.demo
+ [6] dm.demo.Probe(type=radiation) unregistered
+ dm.demo.Sensor service required unavailable
+ [7] dm.demo.Probe(type=humidity) registered
+ [9] dm.demo.impl.Dashboard unregistered
+ dm.demo.Probe (type=temperature) service required available
+ dm.demo.Probe (type=radiation) service required unavailable
+ dm.demo.Probe (type=humidity) service required available
+ dm.demo.Probe (type=pressure) service required available
+ [5] dm.demo.Probe(type=temperature) registered
+ [8] dm.demo.Probe(type=pressure) registered
-```compact, cp``` shortens package names and dependencies and therefore gives
a more compressed output.
-
-```nodeps, nd``` omits the dependencies from the output.
+All components are listed including the dependencies and the availability of
these dependencies. The top level element is the bundle and below are the
components registered with that bundle's bundle context. The lowest level is
that of the component's dependencies.
-```notavail, na``` filters out all components that are registered wich results
in the output only containing those components that are in the unregistered
state due to one or more unsatisfied required dependencies. This is the command
option most used when using the dependency manager shell commands.
+ [bundleid] bundle
+ [component id] component interfaces (service properties)
+ dependency <availability>
+
+The following flags can be used to tailor the output:
+
+* ```compact, cp``` shortens package names and dependencies and therefore
gives a more compressed output.
+* ```nodeps, nd``` omits the dependencies from the output.
+* ```notavail, na``` filters out all components that are registered wich
results in the output only containing those components that are in the
unregistered state due to one or more unsatisfied required dependencies. This
is the command option most used when using the dependency manager shell
commands.
Sample output for ```dm na```:
-```
-[9] dm.demo
- [14] dm.demo.impl.Dashboard unregistered
- dm.demo.Probe (type=radiation) service required unavailable
- [11] dm.demo.Probe(type=radiation) unregistered
- dm.demo.Sensor service required unavailable
-```
+ [9] dm.demo
+ [14] dm.demo.impl.Dashboard unregistered
+ dm.demo.Probe (type=radiation) service required unavailable
+ [11] dm.demo.Probe(type=radiation) unregistered
+ dm.demo.Sensor service required unavailable
The flags can be used in conjunction with the other command options.
@@ -91,12 +84,9 @@ __Find out why components are not regist
Sample output
-```
-2 missing dependencies found.
------------------------------
-The following service(s) are missing:
- * dm.demo.Sensor is not found in the service registry
-```
+ 2 missing dependencies found.
+ -----------------------------
+ The following service(s) are missing:
+ * dm.demo.Sensor is not found in the service registry
-wtf gives the root cause for components not being registered and therefore
their services not being available. In a typical application components have
dependencies on services implemented by components that have dependencies on
services etcetera. This transitivity means that an entire chain of components
could be unregistered due to a (few) root dependencies not being satisified.
wtf is about discovering those dependencies.
-
\ No newline at end of file
+wtf gives the root cause for components not being registered and therefore
their services not being available. In a typical application components have
dependencies on services implemented by components that have dependencies on
services etcetera. This transitivity means that an entire chain of components
could be unregistered due to a (few) root dependencies not being satisified.
wtf is about discovering those dependencies.
\ No newline at end of file
