On Wednesday 10 August 2016 19:46:05 Benson Margulies wrote: > On Wed, Aug 10, 2016 at 5:44 PM, David Jencks [...] > > out of curiosity, why do you need your own ConfigurationListener? > > Oh, it's the collision of two issues. > > First, I need to have the arrangement of '.cfg' file make sense to a > human being who is configuring a system, not just be a mirror of my > momentary set of modularity decisions into @Component classes. So I > can't use the DS connection to config-admin very well, since I need > multiple objects to read the same configuration. > > Second, purely in my tests, I was having trouble making sure that the > config of one of these items was present _before_ its @Activate was > called,
See my last mail in thread "Bundles needed to use DS/SCR" – pax-exam-cm ensures configurations are available before components get activated. O. > so I considered deferring the work until a > ConfigurationListener was called back. When I registered it on the > bundle at hand, it was never called. I probably registered it wrong. > I've found a simpler approach. > > > thanks > > david jencks [...] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
