On Mon, Oct 31, 2016 at 2:12 PM, 'Christoph Läubrich' via OPS4J <[email protected]> wrote: > You should then activate the debug options of Felix SCR to see whats going > on.
Not only have I spend hours staring at the logging output of SCR, I've _debugged SCR_. Set breakpoints in it. Seen that, in particular, it seems to be never notified of the arrival of the ConfigurationAdmin service. Can you share the "working" vs the "not working" code? Unfortunately, no. It's part of a large, non-open-source, system. Essentially, I'll have to debug it in place to create a test case that I can share. What > Pax-Container do you use? Remote? Embedded? The default embedded Felix container with Felix 5.4.0. Have you tried to use > immediate="true" for your component to make sure it is not delayed? Yes. > > Am 31.10.2016 01:56, schrieb Benson Margulies: >> >> If I can make a small test case I will. >> >> Outline: >> >> As of the prior git commit, I have a working test. It uses Pax-exam, >> provisioning felix config admin and scr, current versions. It uses the >> config admin module to set up a PID. I have a component that requires that >> pid. The component is activated. All works. >> >> I made some changes that should only affect code after the call to the >> activate method. The tests stops working, because the component is never >> activated. If I debug inside of Felix SCR, I see that the SCR code that >> listens for ConfigurationAdmin so as to install listeners is never called. >> Yet CA is certainly in there; my pax-exam test can request injection of the >> ConfigurationAdmin service and receive it. >> >> It is possible that I perturbed the classpath, in order or in content. >> That's on my list of things to recheck. >> >> The larger integration tests of the larger system that includes these >> pieces all work, as well. >> >> > > -- > -- > ------------------ > OPS4J - http://www.ops4j.org - [email protected] > > --- You received this message because you are subscribed to a topic in the > Google Groups "OPS4J" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ops4j/P6vyapDiOpw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
