> > This is defined in Section 135.4 of the OSGi compendium spec release.
That is exactly what I was looking for. Thank you very much! I remembered that I had seen it somewhere, but I searched it in the OSGi core spec where the Export-Service header is described. It would probably a good idea to link the chapter of Comendium spec from the OSGi core specification where Export-Service is explained. I propose to append this information to the Wiki site <http://wiki.osgi.org/wiki/Export-Service> as well. This sounds a lot like http://jpm4j.org - you should probably talk to Peter > Kriens! I know about it, but I did not see any option (or documentation) on the website, how to search based on capabilities as it is in the MANIFEST header. Anyway, I will ask him if that is possible. On Fri, Mar 4, 2016 at 11:11 AM, Timothy Ward <tim.w...@paremus.com> wrote: > Hi, > > > On 4 Mar 2016, at 10:03, Balázs Zsoldos <balazs.zsol...@everit.biz> wrote: > > Hi, > > as much as I know, Export-Service MANIFEST header is deprecated. I would > like to ask you if there is an alternative like osgi.service namespace with > Provide-Capability? > > > This is defined in Section 135.4 of the OSGi compendium spec release. > > > Use case: > > We have many components. The components have references. I would like to > have a screen where I can list the artefacts that can offer services with > the interface that the component needs. > > > The osgi.service namespace from chapter 135 will definitely handle that. > > > Second question: > > I have implemented a simple webapp that: > > - Downloads the search index of maven-central > - Downloads the MANIFEST file of every JAR that has > Bundle-SymbolicName in the search index > - Indexes the MANIFEST in the way that Provide-Capability headers are > processed, too > - Offers a simple screen where Import-Package or Require-Capability > clauses can be written as search expressions > > Is there anyone else, who would be happy to use such a website? If yes, I > will take some time to make it user-friendly and make it as a public > website. Well, the second part should take a while as the source is a bit > ugly at the moment :). > > > This sounds a lot like http://jpm4j.org - you should probably talk to > Peter Kriens! > > > Kind regards, > *Balázs **Zsoldos* > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
