[
https://issues.apache.org/jira/browse/ARIES-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920217#action_12920217
]
Timothy Ward commented on ARIES-450:
------------------------------------
I'd probably characterise it as a bug in the modelling code, in that it fails
to add package version information to service requirements and capabilities,
but essentially yes it is a bug in our OBR resolution system.
Felix OBR itself is not at fault.
> Service based provisioning returns services that can never be used
> ------------------------------------------------------------------
>
> Key: ARIES-450
> URL: https://issues.apache.org/jira/browse/ARIES-450
> Project: Aries
> Issue Type: Bug
> Components: Application
> Affects Versions: 0.3
> Reporter: Timothy Ward
> Fix For: 0.3
>
>
> When performing service based provisioning, the OBR metadata does not provide
> any information about the version of the interface either required or exposed
> as a service.
> For example,
> * I have a bundle A that uses the org.apache.aries.Foo service, and imports
> org.apache.aries;version="[1.0.0,2.0.0)"
> * I have a bundle B that provides the org.apache.aries.Foo service and
> imports org.apache.aries;version="[2.0.0,2.1.0)"
> When bundle A is provisioned, the current implementation will return bundle B
> as a valid implementation of the Foo service, even though there is no way
> that A can ever use it because the class spaces have no overlap!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
