Hi all, Slingstart provisioning is a nice way to provision and launch applications - I've even used it for non-sling based ones :)
One thing that would be nice is to add subsystem support. Especially application/composite subsystems would be quite useful to support as they provide a layer of isolation. So I started looking into what would need to be done for subsystem support... The provisioning model needs to be enhanced so that subsystems can be specified there. I have started an initial prototype that enhances the feature in the model with a type so that this can be recorded: https://issues.apache.org/jira/browse/SLING-5148 Then the slingstart-maven-plugin must be enhanced to process these subsystems from the model. Instead of individual bundles, it creates an .esa file from the artifacts and places the .esa file in the generated launchpad archive. I've added a prototype for this here: https://issues.apache.org/jira/browse/SLING-5149 Finally the runtime side needs to be enhanced to pick up the .esa file from the launchpad archive and install it using the Subsystem service, for this an OSGi subsystems runtime must be available in the sling runtime. I haven't added JIRAs for this yet, as I need to look into the details of this a little more... What do people think? If we agree to go ahead with this I will finish off the patches, provide unit tests and add the additional JIRAs for the runtime side... Cheers, David
