SIgh. I can't repro the problem that's interesting to you, and the more CXF-ish problem needs to be chased at CXF.
On Wed, Jul 6, 2016 at 12:29 PM, Benson Margulies <ben...@basistech.com> wrote: > If I can repro it, I'll endeavor to produce. > > > On Wed, Jul 6, 2016 at 12:25 PM, David Jencks <david.a.jen...@gmail.com> > wrote: >> I’m wondering what the DS implementation bundle is getting it’s Config Admin >> packages from in each case. >> >> thanks >> david jencks >> >>> On Jul 6, 2016, at 9:20 AM, Benson Margulies <ben...@basistech.com> wrote: >>> >>> I can dump a bunch of wiring. But I'd have to repro the problem. >>> which, after being quite reproducible for some time, has gone into >>> hiding to be replaced by a different problem. Just what bundle's >>> wiring are you interested in? >>> >>> >>> On Wed, Jul 6, 2016 at 12:18 PM, David Jencks <david.a.jen...@gmail.com> >>> wrote: >>>> There has been another report of a similar problem that I haven’t been >>>> able to reproduce (outside karaf). Does Karaf provide any way of looking >>>> at the bundle wiring? I’d like to see how the DS bundle is wired in the >>>> working and non working cases. I’m wondering if in the non working case >>>> DS gets wired correctly to config admin. >>>> >>>> thanks >>>> david jencks >>>> >>>>> On Jul 6, 2016, at 9:10 AM, Benson Margulies <ben...@basistech.com> wrote: >>>>> >>>>> com.basistech.worker.service.cfg exists. >>>>> >>>>> And when I stopped and started karaf, the component got itself activated. >>>>> >>>>> >>>>> >>>>> On Wed, Jul 6, 2016 at 12:01 PM, David Jencks <david.a.jen...@gmail.com> >>>>> wrote: >>>>>> You have configuration policy require and there is no component >>>>>> configuration shown, so the configuration is missing. >>>>>> >>>>>> If at least one matching configuration were available to DS you’d see >>>>>> one component configuration for each configuration, and then you could >>>>>> tell if the references were satisfied or not from the references section >>>>>> of the component configuration. >>>>>> >>>>>> thanks >>>>>> david jencks >>>>>> >>>>>>> On Jul 6, 2016, at 8:52 AM, Benson Margulies <ben...@basistech.com> >>>>>>> wrote: >>>>>>> >>>>>>> Folks, I have a service that isn't starting, and I cannot see why. Any >>>>>>> clues? >>>>>>> >>>>>>> >>>>>>> karaf@root>scr:details com.basistech.ws.worker.service.WorkerService >>>>>>> Component Details >>>>>>> Name : com.basistech.ws.worker.service.WorkerService >>>>>>> State : UNSATISFIED >>>>>>> Properties : >>>>>>> service=worker >>>>>>> References >>>>>>> >>>>>>> ----- >>>>>>> >>>>>>> karaf@root>scr:info com.basistech.ws.worker.service.WorkerService >>>>>>> *** Bundle: com.basistech.ws.rosapi-worker-service (144) >>>>>>> Component Description: >>>>>>> Name: com.basistech.ws.worker.service.WorkerService >>>>>>> Default State: enabled >>>>>>> Activation: immediate >>>>>>> Configuration Policy: require >>>>>>> Activate Method: activate >>>>>>> Deactivate Method: deactivate >>>>>>> Modified Method: - >>>>>>> Configuration Pid: [com.basistech.worker.service] >>>>>>> Services: >>>>>>> com.basistech.ws.common.WebServiceAvailable >>>>>>> Service Scope: singleton >>>>>>> Reference: CxfTransport >>>>>>> Interface Name: org.apache.cxf.transport.http.DestinationRegistry >>>>>>> Cardinality: 1..1 >>>>>>> Policy: static >>>>>>> Policy option: reluctant >>>>>>> Reference Scope: bundle >>>>>>> Reference: Metrics >>>>>>> Interface Name: com.basistech.ws.common.metrics.MetricsRegistryService >>>>>>> Cardinality: 1..1 >>>>>>> Policy: static >>>>>>> Policy option: reluctant >>>>>>> Reference Scope: bundle >>>>>>> Reference: Worker >>>>>>> Interface Name: com.basistech.ws.worker.api.WorkerInterface >>>>>>> Cardinality: 1..1 >>>>>>> Policy: static >>>>>>> Policy option: reluctant >>>>>>> Reference Scope: bundle >>>>>>> Properties: >>>>>>> service = worker >>>>>> >>>> >>
