That sounds a lot like the DS ComponentFactory use case to me. You supply properties to the factory and it spits out a configured instance for you to use.
Just to confirm, I assume that the standard multiton pattern using factory configurations doesn't help you as the components are stateful and need to be created on demand? Regards, Tim Sent from my iPhone > On 18 Nov 2016, at 21:23, Scott Lewis <sle...@composent.com> wrote: > >> On 11/18/2016 11:45 AM, BJ Hargrave wrote: >> No. All component instances for the prototype scope service share the same >> component properties. But each instance represents a different service >> consumer. This is much the same as a bundle scope service where each >> component instance has the same component properties but represents a >> different consumer bundle. > > ok thanks. So for a use case that includes creating service instances via > PrototypeServiceFactory (or something else) and a desire to configure those > instances (ideally with ConfigurationAdmin/meta-type, etc) do you have any > suggestions on approach? > > Scott > > > _______________________________________________ > 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
