Hi, On Sun, Nov 4, 2018 at 9:45 PM Oliver Lietz <apa...@oliverlietz.de> wrote:
> > > ...wouldn't it make sense to exploit OSGi Capabilities instead of > > > building our own API and > > > implementation for capabilities?... The goal of the Capabilities module [1] is to provide a simple HTTP API that indicates what a Sling instance can do. I don't think the HTTP part of that is covered by OSGi capabilities, and [1] really just defines a JSON format for capabilities, a way to set up such endpoints with access control and a way to decide what's output (via CapabilitiesSource services). One can very much implement a CapabilitiesSource [2] that exposes relevant OSGi capabilities, would that work for you? Or do you mean that I should have used something from [3] instead of CapabilitiesSource? -Bertrand [1] https://github.com/apache/sling-org-apache-sling-capabilities [2] https://github.com/apache/sling-org-apache-sling-capabilities/blob/master/src/main/java/org/apache/sling/capabilities/CapabilitiesSource.java [3] https://osgi.org/specification/osgi.core/7.0.0/framework.resource.html
