[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Conceptual problem with OSGi

It would be better to ask this question on the osgi-dev@xxxxxxxxxxxxx list since it is a general OSGi question and not tied to Equinox's implementation.

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the
OSGi Alliance

office: +1 386 848 1781
mobile: +1 386 848 3788

From: "Alexander Shutyaev" <shutyaev@xxxxxxxxx>
To: equinox-dev@xxxxxxxxxxx
Date: 2008/10/30 07:46 AM
Subject: [equinox-dev] Conceptual problem with OSGi

I have come upon a conceptual problem with OSGi.

First, I'll tell what I need. I need a factory that will create some instances. Each instance has it's own configuration and all instances provide a service.

I've read about the EMailFetcher example in the Configuration Admin Specification and it turned out to be just my case. So I was happy and thought that I should use ManagedServiceFactory and all the things associated with it.

Later, however I've read the Declarative Services Specification. And that is where it began. I can't feel the difference between the ManagedServiceFactory (from Configuration Admin) and ComponentFactory (from Declarative Services).

If anyone could tell me the difference between them (for example why can't I use ComponentFactory in the EMailFetcher example, or can I?), I would be very-very thankful.

Thanks in advance...
equinox-dev mailing list