Details
Description
When executing the "osgi:list" in the Karaf console, the Spring status stays empty. After the first invocation of "osgi:list" in the Karaf shell, the listener gets registered, but the Spring status stays empty until the next bundle state change (ie states changes in the past are lost).
A more reliable solution to this problem would be to register the listeners in a bundle activator in the Karaf Shell OSGi bundle, so that all events are listened from the early start of the server.
This problem was already reported in FELIX-1717 but the problem is still present in Karaf 2.2.4.
Attachments
Issue Links
- duplicates
-
KARAF-1114 osgi shell blueprint bundle shouldn't use lazy default-activation
- Closed