sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Bosschaert <>
Subject Re: [Feature Model] Initial API Regions implementation
Date Wed, 07 Nov 2018 08:32:49 GMT
Hi all,

If nobody objects I'd like to create two new Sling Git Repositories for
sling-org-apache-sling-feature-extension-apiregions for the extension
handlers and
sling-org-apache-sling-feature-apiregions for the runtime framework
extension bundle.

Are there any sling-specific instructions on how to create these repos?

Best regards


On Tue, 6 Nov 2018 at 15:50, David Bosschaert <>

> Hi all,
> Over the past little while I have worked on an implementation for a
> runtime enforcement component for API Regions for Sling Features [1].
> The implementation is based on 2 components.
> a. Merge/PostProcessor handlers that work on the 'api-regions' section in
> the feature files. These components know how to merge api-regions sections
> into a target feature and the PostProcessor handlers generate a number of
> properties files that drive the runtime enforcement implementation of this.
> For details see [2].
> b. The runtime component which is implemented as an OSGi Framework
> extension bundle. Registers a ResolverHookFactory service with the
> framework which is consulted by the OSGi resolver. The hook can prevent
> certain resolutions from happening and is driven by the properties files
> generated by the process in a. to enforce the regions as defined in the
> feature files. For details see [3].
> Currently these two new components [2][3] are in the sling-whiteboard, but
> it would be great to graduate them out of there into their own Sling
> repositories. Does the sling community think that this would be the right
> thing to do?
> Many thanks,
> David
> [1]
> [2]
> [3]

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message