You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2019/06/17 12:56:01 UTC

[jira] [Closed] (SLING-8478) Adding method to match Requirements and Capabilities

     [ https://issues.apache.org/jira/browse/SLING-8478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls closed SLING-8478.
-----------------------------

> Adding method to match Requirements and Capabilities
> ----------------------------------------------------
>
>                 Key: SLING-8478
>                 URL: https://issues.apache.org/jira/browse/SLING-8478
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model 1.0.4, Feature Model IO 1.0.4, Feature Model Analyser 1.0.4
>
>
> a feature can have requirements and capabilities, we use the OSGi interfaces for this. However, there is currently no easy way to match requirements and capabilities as these interfaces do not provide a method for it.
> For example, if you want to know whether a requirement is met by the available capabilities, that's not possible. While the OSGi specs provide a resolver that approach is way too heavy and not really suited for simple use cases. The resolver is used by the framework for bundle wiring.
> Therefore I propose we add a simple interface like
> MatchingRequirement extends Requirement {
>    boolean match(Capability cap);
> }
> and this allows to match requirements and capabilities. As we're using Apache Felix utils for our reqs/caps, this method is already available there, so we don't have to implement this ourselves. Its just making it available 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)