I have some more information. While I still don't know where my log
message are going, I turned on the gogo remote shell. According to
scr:info, my component is alive.
However, I can't obtain a service reference to the service it exports
with a plain old ServiceTracker or call to my bundle context. I'd be
grateful for any diagnostic advice.
scr:info com.basistech.ws.worker.core.config.WorkerConfigurationImpl
*** Bundle: rosapi-worker-core (56)
Component Description:
Name: com.basistech.ws.worker.core.config.WorkerConfigurationImpl
Implementation Class:
com.basistech.ws.worker.core.config.WorkerConfigurationImpl
Default State: enabled
Activation: immediate
Configuration Policy: require
Activate Method: activate
Deactivate Method: deactivate
Modified Method: -
Configuration Pid:
[com.basistech.ws.worker.core.config.WorkerConfigurationImpl]
Services:
com.basistech.ws.worker.core.config.WorkerConfiguration
Service Scope: singleton
Reference: ConfigurationAdmin
Interface Name: org.osgi.service.cm.ConfigurationAdmin
Cardinality: 1..1
Policy: static
Policy option: reluctant
Reference Scope: bundle
Component Description Properties:
(No Component Configurations)
On Wed, Aug 10, 2016 at 10:32 AM, Benson Margulies <[email protected]> wrote:
> For unit testing purposes, I'm setting up a minimal container that has DS/SCR
> .
>
> I included:
>
> <groupId>org.apache.felix</groupId>
> <artifactId>org.apache.felix.scr</artifactId>
> <version>2.0.6</version>
>
> I set the framework ds.loglevel property to debug, and I see no sign of life.
>
> I'm using standard OSGi DS annotations.
>
> Can anyone tell me what I'm missing?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
