You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Mark Nuttall (JIRA)" <ji...@apache.org> on 2011/01/21 16:15:43 UTC
[jira] Issue Comment Edited: (FELIX-2546) Only one service is
provisioned even when specifying for mulitple services
[ https://issues.apache.org/jira/browse/FELIX-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984762#action_12984762 ]
Mark Nuttall edited comment on FELIX-2546 at 1/21/11 10:14 AM:
---------------------------------------------------------------
Hello Guillaume,
Although there is currently a problem in using optional <reference> elements in blueprint, wouldn't it be better to fix that, rather than to have OBR continue to function incorrectly? It's surely not right for 'multiple' requirements to return a single capability.
Would you be willing to fix the defective behaviour in OBR if we were to implement an extended <reference> in Aries that one could test to see if it's bound before using it? In that way we could provision optional and multiple <reference-list> elements properly, which we cannot do at the moment. I'd very much rather do that than to have resolver.resolve() take a parameter whose meaning would be "work correctly".
Many thanks for your help in this.
Regards,
Mark
was (Author: mnuttall):
Hello Guillaume,
Although there is currently a problem in using optional <reference> elements in blueprint, wouldn't it be better to fix that, rather than to have OBR continue to function incorrectly? It's surely not right for 'multiple' requirements to return a single capability.
Would you be willing to fix the defective behaviour in OBR if we were to implement an extended <reference-list> in Aries that one could test to see if it's bound before using it? In that way we could provision optional and multiple <reference-list> elements properly, which we cannot do at the moment. I'd very much rather do that than to have resolver.resolve() take a parameter whose meaning would be "work correctly".
Many thanks for your help in this.
Regards,
Mark
> Only one service is provisioned even when specifying for mulitple services
> --------------------------------------------------------------------------
>
> Key: FELIX-2546
> URL: https://issues.apache.org/jira/browse/FELIX-2546
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR)
> Affects Versions: bundlerepository-1.6.4
> Environment: n/a
> Reporter: Emily Jiang
> Attachments: Felix OBR isMultiple support - timothyjward.txt
>
>
> Felix OBR is unable to return multiple services when specifying 'multiple' attribute with the value of 'true'. The test scenario is detailed below.
> I am trying to get all bundles registering the service of com.sample.HelloWorld and install them into the osgi framework . In my test environment, there are two bundles with different symbolic name offering the same service, com.sample.HelloWorld. However, only one bundle was pulled into runtime. The snippet of my repository is shown below.
> <require extend="false" filter="(&(service=service)(objectClass=com.sample.HelloWorld)(mandatory:<*service))" multiple="true" name="service" optional="false">Requires service with attributes {service=service, objectClass=com.sample.HelloWorld}</require>
> Regards
> Emily
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.