Thank you from the bottom of my heart. I have found the culprit, but it leads me to another question.
Initially instead of using scr:list I used services, which wouldn't show my "ActivatorComponent". So I went about to do an scr:info on each one of the referenced services and they all came up as either satisfied or active.
Once I did an scr:list, I saw that my "ActivatorComponent" was unsatisfied and then I did an scr:info on it and saw the culprit which is:
osgi> Component Description: com.castortech.iris.image.provider.IrisImageImpl
=======================================================================
Class: com.castortech.iris.image.provider.IrisImageImpl
Bundle: 215 (com.castortech.iris.image.provider:1.0.0.qualifier)
Enabled: true
Immediate: false
Services: [com.castortech.iris.image.IrisImage]
Scope: singleton
Config PID(s): [IrisImage_PID], Policy: require
Base Props: (0 entries)
Component Configuration Id: 2301
--------------------------------
State: ACTIVE
Service: 1141 [com.castortech.iris.image.IrisImage]
Used by bundle 141 (com.castortech.iris.irisdb.core:1.0.0.qualifier)
Config Props: (4 entries)
component.id<Long> = 2301
component.name<String> = com.castortech.iris.image.provider.IrisImageImpl
imagePlugin<String> = com.castortech.iris.models.ecore.ba.edit
service.pid<String> = IrisImage_PID
References: (total 1)
- imageProvider: com.castortech.iris.image.provider.internal.ImageProvider SATISFIED 1..1 static
target=(*) scope=bundle (1 binding):
* Bound to [654] from bundle 215 (com.castortech.iris.image.provider:1.0.0.qualifier)
It is in ACTIVE state with all references satisfied. Problem is that this was set with a required configuration, that Tim pointed as a possible cause. But how can it show as active in that case?