It's very useful. But the bit about the "two-parameter getConfiguration
method using null (no location) as the second parameter" should maybe be
mentioned from the start, because it's not at all obvious and I remember
getting bitten by this myself a few years back.

> Hi,
>
> I wrote a blog post about configuring services a while ago.
>
> http://blog.vogella.com/2016/09/26/configuring-osgi-declarative-services/
>
> Maybe it helps to understand it better.
>
> Greez,
> Dirk
>
> Am 04.06.2017 14:02 schrieb "Mark Raynsford" <list+org.o...@io7m.com>:
>
>> On 2017-06-04T13:04:12 +0200
>> Felix Meschberger <fmesc...@gmail.com> wrote:
>>
>> > Hi Mark
>> >
>> > I assume your configurator is creating the configuraiton with:
>> >
>> > >        final Configuration config =
>> > >          this.configurations.getConfiguration(
>> > >            "com.io7m.callisto.stringtables.main.provider“)
>> >
>> > If this is the case, this new configuration is bound to the
>> configurator’s bundle, which IIUIC is the same bundle also containing
>> the
>> Example component.
>>
>> I see.
>>
>> > Thus the Example component gets the configuration being in the same
>> bundle, but the provider does not as it is in another bundle.
>> >
>> > You might want to try to use the two-parameter getConfiguration method
>> using null (no location) as the second parameter to make sure the
>> configuration is not bound at the time of creation — but later when it
>> is
>> first provided to the consumer
>> >
>>
>> Yes, this worked! Thanks.
>>
>> I have to admit, I'm not exactly sure what's happening here. The R6
>> compendium spec mentions that location binding is a security feature
>> (104.4.1), but it then uses terms like "management bundle" without
>> actually explaining what that is.
>>
>> M
>>
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev


_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to