On 3/11/10 9:29, Simon J Archer wrote:
Jeff is right. A DS component factory is used to programmatically
manufacture multiple DS components from the same component XML. Of
course each manufactured DS component can interact with
ConfigurationAdmin as defined by the DS spec and described in the OSGi
and Equinox book (http://equinoxosgi.org <http://equinoxosgi.org/>).
Just in case you missed the link right below in the quoted message... ;-)
From: Jeff McAffer <[email protected]>
To: OSGi Developer Mail List <[email protected]>
Date: 03/11/2010 08:26 AM
Subject: Re: [osgi-dev] ConfigAdmin and DS Component Factory
Sent by: [email protected]
------------------------------------------------------------------------
The OSGi and Equinox book (http://equinoxosgi.org
<http://equinoxosgi.org/>) has pretty detailed coverage and examples
of ConfigAdmin and ComponentFactories individually but at as Neil
says, they are not particularly linked.
Jeff
On 2010-03-11, at 7:38 AM, Neil Bartlett wrote:
> Phil,
>
> ConfigAdmin and DS Component Factories do not work together. You are
> required to programmatically call newInstance() yourself. However it
> should be possible to build a bridge from a ComponentFactory to a
> ManagedServiceFactory.
>
> ManagedServiceFactory is not deprecated.
>
> Regards
> Neil
>
> On Thu, Mar 11, 2010 at 12:30 PM, Philipp Kursawe
> <[email protected]> wrote:
>> Hello,
>>
>> someone out there that can explain me how the ConfigAdmin and DS
>> Component Factories work together?
>>
>> I was under the impression that each factory configuration created
>> will invoke the newInstance method of the DS component factory?
>>
>> Or do I have to create the instances myself programmatically?
>> What properties have to be set in the factory configuration to provoke
>> a creation of a new instance with that factory? Do I need to set the
>> service.factoryPid to the id of the factory?
>>
>> There seem to be no tutorials out there when or how to use the DS
>> component factory. Only for the deprecated (?) ManagedServiceFactory.
>>
>> Thanks,
>> Phil
>> _______________________________________________
>> OSGi Developer Mail List
>> [email protected]
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
