Hey Milen,
Yes, there attempts to use it and we are using it for example in Karaf under 
the hood. Feature descriptors which are using latest namespaces are backed by 
osgi resolver. Also eclipse-smarthome and openhab2 are using explicitly these 
to loosely couple provider/consumer features and deliver jaxrs stuff. 
Everything is built on top of Apache Karaf features which delegates actual 
resolution to osgi resolver implementation. In case of smarthome it is far from 
being perfect due to nature of inter dependencies between supplier/provider, 
however it shows at least some kind of separation and real world usage. 

Here are example links for you:
https://github.com/eclipse/smarthome/blob/master/features/karaf/esh-tp/src/main/feature/feature.xml
 
<https://github.com/eclipse/smarthome/blob/master/features/karaf/esh-tp/src/main/feature/feature.xml>
https://github.com/openhab/openhab-distro/blob/2.0.x/features/addons-esh/src/main/feature/feature.xml
 
<https://github.com/openhab/openhab-distro/blob/2.0.x/features/addons-esh/src/main/feature/feature.xml>

Kind regards,
Lukasz
--
Apache Karaf Committer & PMC
Twitter: @ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org

> Wiadomość napisana przez Milen Dyankov <milendyan...@gmail.com> w dniu 
> 15.03.2017, o godz. 11:38:
> 
> Hi all,
> 
> Is anyone aware of any attempt to use the requirements&capabilities, 
> repositories and resolver specs for anything other than provisioning OSGi 
> runtime? It seams to me the specs are generic enough to be used in other 
> scenarios. 
> 
> One example that comes to my mind is provisioning a telecommunication offer. 
> Say user purchase "plan A" which requires things like "text messaging", 
> "roaming", ... and then resolver finds services  with such capabilities which 
> on the other hand have their own requirements.   
> 
> The above is just an example I made up, it's not something I'm really 
> interested in. I'm rather looking for any example of usage of those concepts 
> outside the scope of their original purpose.
> 
> Best,
> Milen  
> 
> 
> -- 
> http://about.me/milen 
> <http://about.me/milen>_______________________________________________
> 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

Reply via email to