This is an automated email from the ASF dual-hosted git repository. bdelacretaz pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-capabilities.git
commit 5efb7a3e72508d870325c5f96861efff99421107 Author: Bertrand Delacretaz <[email protected]> AuthorDate: Thu Jun 21 14:37:08 2018 +0200 Expand README --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index b84cb65..71df24e 100644 --- a/README.md +++ b/README.md @@ -12,6 +12,12 @@ by aggregating the output of all active `CapabilitiesSource` services. This can be easily expanded to multiple sets of Capabilities if needed later on, by changing the code to use service properties to group or tag the `CapabilitiesSource` services. +These capabilities are _not_ the same as OSGi capabilities: they can be application-related, indicate +the availability of external services, etc. + +CapabilitiesSource services +---------------------------- + The tests provide simple `CapabilitiesSource` examples, that API is as follows: @ProviderType @@ -29,6 +35,9 @@ The tests provide simple `CapabilitiesSource` examples, that API is as follows: Map<String, Object> getCapabilities() throws Exception; } +CapabilitiesServlet output +-------------------------- + The `CapabilitiesServlet` produces output as in the example below, where two `CapabilitiesSource` services are available:
