You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@aries.apache.org by David Bosschaert <da...@gmail.com> on 2015/10/10 11:54:36 UTC
Fwd: Aries Subsystems using Repository
Forwarding to user@aries...
---------- Forwarded message ----------
From: David Bosschaert <da...@gmail.com>
Date: 10 October 2015 at 10:53
Subject: Re: Aries Subsystems using Repository
To: users@felix.apache.org
Hi Paul,
Not sure why they would be different? The repository is used to find
any bundles that can provide capabilities which are needed. So if your
DS bundles provide capabilities either via Export-Package or
Provide-Capability that are required by the root bundles of the
subsystem, or their transitive deps, then they should be included.
I'm not sure when I'd have the time to add a ds example, but what
would help is if you could maybe post an example (maybe via a pull
request on https://github.com/coderthoughts/subsystem-examples) that
doesn't work... Maybe we can then pinpoint the issue quicker?
Best regards,
David
On 10 October 2015 at 00:13, Paul F Fraser <pa...@a2zliving.com> wrote:
> Hi,
>
> David Bosschaert's examples
> https://github.com/coderthoughts/subsystem-examples all include the
> dependent bundles in the esa file.
> Therefore not relying on picking them up from a repository.
> And there are no examples using declarative services bundles.
>
>
> Using Felix bundle repository, the problem I am having, which I have
> discussed in the Aries mail list, is that my system fails to resolve DS
> bundles from a repository but works OK with non DS bundles.
> I have tried to produce a simple sample to reproduce the problem but due to
> inexperience have been unable to do so.
>
> Is any one able to point me to a working feature subsystem example where the
> dependent bundles use DS and are not in the esa file?
>
> Perhaps David might be kind enough to add a simple example to his Github
> examples :)
>
> Regards
>
> Paul Fraser
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
Re: Aries Subsystems using Repository
Posted by David Jencks <da...@yahoo.com.INVALID>.
If you use bnd3 these Provide-Capability/Require-Capability headers should be generated for you from the DS info.
david jencks
> On Oct 10, 2015, at 8:55 AM, Paul F Fraser <pa...@a2zliving.com> wrote:
>
> On 10/10/2015 10:17 PM, John Ross wrote:
>> I'm not sure if this is part of the issue, but note that there is no
>> explicit support for DS in Aries Subsystems as there is for Blueprint.
>>
>> With Blueprint, service requirements and capabilities will be pulled
>> directly from the Blueprint XML files. The same is not true for DS.
>> When using DS, service requirements and capabilities must also be
>> expressed via the Require-Capability and Provide-Capability bundle
>> headers.
>>
> I think that's it..
>
> I am using bundles direct from bndtools release. No manual addition of Provide-Capability or Require-Capability.
>
> At least, I am not going mad,
>
> Thanks John & David,
>
> Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Aries Subsystems using Repository
Posted by David Jencks <da...@yahoo.com>.
If you use bnd3 these Provide-Capability/Require-Capability headers should be generated for you from the DS info.
david jencks
> On Oct 10, 2015, at 8:55 AM, Paul F Fraser <pa...@a2zliving.com> wrote:
>
> On 10/10/2015 10:17 PM, John Ross wrote:
>> I'm not sure if this is part of the issue, but note that there is no
>> explicit support for DS in Aries Subsystems as there is for Blueprint.
>>
>> With Blueprint, service requirements and capabilities will be pulled
>> directly from the Blueprint XML files. The same is not true for DS.
>> When using DS, service requirements and capabilities must also be
>> expressed via the Require-Capability and Provide-Capability bundle
>> headers.
>>
> I think that's it..
>
> I am using bundles direct from bndtools release. No manual addition of Provide-Capability or Require-Capability.
>
> At least, I am not going mad,
>
> Thanks John & David,
>
> Paul
Re: Aries Subsystems using Repository
Posted by Paul F Fraser <pa...@a2zliving.com>.
On 10/10/2015 10:17 PM, John Ross wrote:
> I'm not sure if this is part of the issue, but note that there is no
> explicit support for DS in Aries Subsystems as there is for Blueprint.
>
> With Blueprint, service requirements and capabilities will be pulled
> directly from the Blueprint XML files. The same is not true for DS.
> When using DS, service requirements and capabilities must also be
> expressed via the Require-Capability and Provide-Capability bundle
> headers.
>
I think that's it..
I am using bundles direct from bndtools release. No manual addition of Provide-Capability or
Require-Capability.
At least, I am not going mad,
Thanks John & David,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Aries Subsystems using Repository
Posted by Paul F Fraser <pa...@a2zliving.com>.
On 10/10/2015 10:17 PM, John Ross wrote:
> I'm not sure if this is part of the issue, but note that there is no
> explicit support for DS in Aries Subsystems as there is for Blueprint.
>
> With Blueprint, service requirements and capabilities will be pulled
> directly from the Blueprint XML files. The same is not true for DS.
> When using DS, service requirements and capabilities must also be
> expressed via the Require-Capability and Provide-Capability bundle
> headers.
>
I think that's it..
I am using bundles direct from bndtools release. No manual addition of Provide-Capability or
Require-Capability.
At least, I am not going mad,
Thanks John & David,
Paul
Re: Aries Subsystems using Repository
Posted by John Ross <jw...@gmail.com>.
I'm not sure if this is part of the issue, but note that there is no
explicit support for DS in Aries Subsystems as there is for Blueprint.
With Blueprint, service requirements and capabilities will be pulled
directly from the Blueprint XML files. The same is not true for DS.
When using DS, service requirements and capabilities must also be
expressed via the Require-Capability and Provide-Capability bundle
headers.
On Sat, Oct 10, 2015 at 4:54 AM, David Bosschaert
<da...@gmail.com> wrote:
> Forwarding to user@aries...
>
>
> ---------- Forwarded message ----------
> From: David Bosschaert <da...@gmail.com>
> Date: 10 October 2015 at 10:53
> Subject: Re: Aries Subsystems using Repository
> To: users@felix.apache.org
>
>
> Hi Paul,
>
> Not sure why they would be different? The repository is used to find
> any bundles that can provide capabilities which are needed. So if your
> DS bundles provide capabilities either via Export-Package or
> Provide-Capability that are required by the root bundles of the
> subsystem, or their transitive deps, then they should be included.
>
> I'm not sure when I'd have the time to add a ds example, but what
> would help is if you could maybe post an example (maybe via a pull
> request on https://github.com/coderthoughts/subsystem-examples) that
> doesn't work... Maybe we can then pinpoint the issue quicker?
>
> Best regards,
>
> David
>
> On 10 October 2015 at 00:13, Paul F Fraser <pa...@a2zliving.com> wrote:
>> Hi,
>>
>> David Bosschaert's examples
>> https://github.com/coderthoughts/subsystem-examples all include the
>> dependent bundles in the esa file.
>> Therefore not relying on picking them up from a repository.
>> And there are no examples using declarative services bundles.
>>
>>
>> Using Felix bundle repository, the problem I am having, which I have
>> discussed in the Aries mail list, is that my system fails to resolve DS
>> bundles from a repository but works OK with non DS bundles.
>> I have tried to produce a simple sample to reproduce the problem but due to
>> inexperience have been unable to do so.
>>
>> Is any one able to point me to a working feature subsystem example where the
>> dependent bundles use DS and are not in the esa file?
>>
>> Perhaps David might be kind enough to add a simple example to his Github
>> examples :)
>>
>> Regards
>>
>> Paul Fraser
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>