Hi, We have also tried to go that path, however this thing seems to be orphaned. It cannot be built with the released version of the subsystem implementation, however we are currently trying to fix this for our own little implementation.
Unfortunately it is rather difficult to find out whether a file is a subsystem artifact or not (both the .esa extension and the subsystem manifest are optional). We have made the installer feel responsible for all .esa files, which is fine for our test purposes. Also the logic when to start a subsystem (especially after an update is not clean there). Best regards Stephan From: Cristiano Gavião [mailto:[email protected]] Sent: Sonntag, 18. August 2013 17:48 To: [email protected] Subject: Re: [Aries Subsystem] initial provisioning with subsystems ? Well, I could find the solution... :) aries subsystem provides the bundle org.apache.aries.subsystem.install that provides an implementation of org.apache.felix.fileinstall.ArtifactInstaller. So I just needed to setup fileinstall properly. regards, Cristiano 2013/8/18 Cristiano Gavião <[email protected]<mailto:[email protected]>> Hello, I've been playing with Aries Subsystem for some time. In all my experiments I install the .esa artifacts using console commands that delegate to the subsystem service. Now I would like to experiment with a deliverable product that embeds some .esa files. So, how would be the best strategy to deal with such case? thanks for any tip. Cristiano -- "Tudo vale a pena se a alma não é pequena..."
