On Fri, Aug 28, 2015 at 2:06 PM, BJ Hargrave <hargr...@us.ibm.com> wrote:
> DS does not make configurations. It just uses them. > > Peter has something in enRoute which makes configurations from a resource > in a bundle: > https://github.com/osgi/osgi.enroute.bundles/tree/master/osgi.enroute.configurer.simple.provider > After speaking with Tom Watson, I think we realized, like you said, it's pretty much what Peter is doing in this enroute impl. Thanks - Ray > > -- > > BJ Hargrave > Senior Technical Staff Member, IBM // office: +1 386 848 1781 > OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 > hargr...@us.ibm.com > > > > ----- Original message ----- > From: Raymond Auge <raymond.a...@liferay.com> > Sent by: osgi-dev-boun...@mail.osgi.org > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> > Cc: > Subject: [osgi-dev] creating default instances from service factories > Date: Fri, Aug 28, 2015 1:56 PM > > I'm trying to solve a problem for a friend! [tic] > > He has a factory metatype definition > > e.g. > // still using bnd annotations > @Meta.OCD( > factory = true, > id = "the.pid" > ) > > He would like 2 distinct configuration instances having specific > properties set, to be instantiated from this definition "by default" at the > start of the framework (of course once all deps are started and so on...) > > However, I do not like the notion of pragmatically creating the > configurations using the config admin API. > > Is there a more elegant way to do this, preferably using DS? > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > (@OSGiAlliance) > _______________________________________________ > 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 > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
