Debugging into ConfigurationAdmin, I see that when my code sets up the
PID that the component depends on, it reaches:
log( LogService.LOG_DEBUG, "No ConfigurationListeners to send {0}
event to.", new Object[]
{ asyncSender.getTypeName() } );
}
So SCR is somehow not listening for configuration admin events.
On Thu, Oct 27, 2016 at 4:09 PM, Benson Margulies <[email protected]> wrote:
> I have a few pax-exam tests which include Apache Felix SCR 2.0.6.
>
> I am finding them very fragile. I make very slight changes, and SCR stops
> activating some critical components.
>
> The log messages from SCR are not informative; heck, I can't even find
>
> org.slf4j.osgi-over-slf4j[org.apache.felix.scr.2.0.6] : Starting destruction
> process bundle: org.yaml.snakeyaml/59
>
> in the source code.
>
> I don't make any special arrangements about threads. I've tried @Inject and
> an explicit service tracker to wait for the component; it never shows up
> when things are broken. Has anyone else been here? My production code that
> does not use pax-exam (of course) works fine.
>
> --
> --
> ------------------
> 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.
