[
https://issues.apache.org/jira/browse/ARIES-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Teodor Todorov updated ARIES-987:
---------------------------------
Summary: Spi-fly does not take into account, that an OSGi Framework may not
support multiple cardinality on a Requirement. (was: Spi-fly does not take
into account, that an OSGi Framework may not support multiple cardinality.)
> Spi-fly does not take into account, that an OSGi Framework may not support
> multiple cardinality on a Requirement.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-987
> URL: https://issues.apache.org/jira/browse/ARIES-987
> Project: Aries
> Issue Type: Bug
> Reporter: Teodor Todorov
>
> The piece of code, that does not consider, whether the multiple cardinality
> support is available in the hosting OSGi Framework, is in the method "private
> static ClassLoader findContextClassloader(Bundle consumerBundle, String
> className, String methodName, Class<?> clsArg)"
> from class org.apache.aries.spifly.Util. This method makes the intersection
> of the allowedBundles (the providers, matching the filters of the consumer)
> and bundles (all providers), but does not take into account the set of
> provider bundles, which are wired to the client bundle - this information is
> available through the BundleWiring of the client bundle.
> I may provide a patch, which resolves this, on request.
> The OSGi Test Case for Service Loader does take into account, that multiple
> cardinality might NOT be supported in the hosting OSGi Framework.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
