Stephan, I think that you could use the MiME type when you are creating the .esa file.
The Zip api let you set this kind of header information in the generated artifact. regards, Cristiano 2013/8/20 Siano, Stephan <[email protected]> > Hi John,**** > > ** ** > > How do I get the MIME type from the > org.apache.felix.fileinstall.ArtifactInstaller interface? Furthermore I am > not sure whether this really belongs to Aries-Subsystems as (at least our > implementation) has only references to felix-fileinstall and the osgi > enterprise spec (but not to the aries implementation). **** > > ** ** > > I can post it here or contribute it, but I am not sure whether this is > interesting enough for it (and the implementation of the canHandle method > is far from perfect.**** > > ** ** > > Best regards**** > > Stephan**** > > ** ** > > *From:* John W Ross [mailto:[email protected]] > *Sent:* Montag, 19. August 2013 14:55 > *To:* [email protected] > *Subject:* RE: [Aries Subsystem] initial provisioning with subsystems ?*** > * > > ** ** > > The following subsystems related projects in SVN are currently not > maintained and might be deleted in the future (particularly > subsystem-scope-* as this is obsolete functionality). > > subsystem-example > subsystem-executor > subsystem-install > subsystem-scope-* > > If subsystem-install is providing value, please feel free to offer any > contributions that have made it so. > > With regard to identifying subsystem files, note that there is also a > reserved MIME type: application/vnd.osgi.subsystem. > > John > > > > > > RE: [Aries Subsystem] initial provisioning with subsystems ? > > > > 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] <[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]> > > 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..." **** > -- "Tudo vale a pena se a alma não é pequena..."
