Hi David, Ah, ok. Yes, that helps indeed. Thanks!
Cheers, =David > On Dec 17, 2019, at 19:55, David Bosschaert <david.bosscha...@gmail.com> > wrote: > > Hi David, > > This means that having an untyped map of configuration data is in most cases > not what you want. More convenient is to convert it to a typed api. Using the > OSGi converter to create an annotation instance is a very convenient way to > do this. Annotations are particularly useful since they allow you to specify > defaults too. > > The converter spec at > https://osgi.org/specification/osgi.enterprise/7.0.0/util.converter.html#util.converter-maps > > <https://osgi.org/specification/osgi.enterprise/7.0.0/util.converter.html#util.converter-maps> > just under table 707.5 has an example of this. > > The converter allows you to do this anywhere you like; Declarative Services > also has this functionality built-in. There it's called 'component property > types'. > > Hope this helps, > > David > > On Tue, 17 Dec 2019 at 06:56, David Leangen via osgi-dev > <osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>> wrote: > > Hi! > > I have a question about the Configurator spec. I am trying to update from the > old enRoute Configurer to the new R7 Configurator. > > > I am not sure what this means: > >> A convenient way to convert a configuration map to the desired data types is >> by using the Converter to convert it to an annotation instance or by using a >> Declarative Services component property type. > > > Can somebody enlighten me? > > > > I will surely have more questions later. :-) > > > Cheers, > =David > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <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
