On Thu, Sep 29, 2016 at 2:34 AM, David Jencks <[email protected]> wrote: > Neither this nor restarting the framework should cause problems. > > Can you come up with a self contained demonstration of this (no components) > behavior? I vaguely recall someone having a similar problem that I couldn’t > reproduce.
David, First, a Maven bug caused me to use version 6.0.0 instead of version 6.0.1-SNAPSHOT, which led to wiring errors, which led to services not starting. Then, I discovered that if you really use the osgi-over-slf4j connector properly, SCR produces messages at more than one logging level, and I didn't have my logging back end configured correctly. Working backwards, fixing the logging revealed the rest, and now all is well. thanks, benson > > thanks > david jencks > >> On Sep 28, 2016, at 8:50 AM, Benson Margulies <[email protected]> wrote: >> >> On Wed, Sep 28, 2016 at 11:43 AM, David Jencks >> <[email protected] <mailto:[email protected]>> >> wrote: >>> It should work in any order. >> >> OK, then I've got some other problem on my hands. Does the last of >> these three messages indicate a problem? >> >> 177 [FelixStartLevel] INFO org.apache.felix.scr.2.0.6 - Starting >> with globalExtender setting: false >> 181 [FelixStartLevel] INFO org.apache.felix.scr.2.0.6 - Version = 2.0.6 >> 242 [CM Configuration Updater (ManagedService Update: >> pid=[org.apache.felix.scr.ScrService])] ERROR >> org.apache.felix.scr.2.0.6 - Cannot create MetaType providing >> ManagedService; not providing Metatype information but just accepting >> configuration >> >> >> >> >>> >>> david jencks >>> >>>> On Sep 28, 2016, at 8:28 AM, Benson Margulies <[email protected]> wrote: >>>> >>>> I'm trying to retrofit SCR/DS into a very dumb application that loads >>>> some bundles and starts the framework. Everything is at the same start >>>> level, and no @Components are ever activated. >>>> >>>> I have logging working; I see >>>> >>>> 191 [FelixStartLevel] INFO org.apache.felix.scr.2.0.6 - Starting >>>> with globalExtender setting: false >>>> 195 [FelixStartLevel] INFO org.apache.felix.scr.2.0.6 - Version = 2.0.6 >>>> >>>> In a more sophisticated cousin of this, I carefully start SCR and DS >>>> at one start level, and only after they are started do I get involved >>>> in starting the rest. I wonder: is this in fact a requirement, or >>>> should I look for some other explanation of why the dumber app is not >>>> activating anything. >>>> >>>> If I start up a container to a shell command line everything works >>>> fine, so I can't get any diagnostic traction that way. >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> <mailto:[email protected]> >> For additional commands, e-mail: [email protected] >> <mailto:[email protected]> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
