+1 to gradudate Carsten
Am 06.11.2018 um 16:50 schrieb 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] https://github.com/apache/sling-org-apache-sling-feature/blob/master/apicontroller.md [2] https://github.com/apache/sling-whiteboard/tree/master/featuremodel/feature-extension-apiregions [3] https://github.com/apache/sling-whiteboard/tree/master/featuremodel/feature-apiregions
-- Carsten Ziegeler Adobe Research Switzerland [email protected]
