felix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Deltour <rdelt...@gmail.com>
Subject Re: Rép : Bundle unsatisfied when using Declarative Services
Date Wed, 24 Aug 2011 13:52:33 GMT
Thanks for your prompt answer. I have set the property ds.loglevel to  
4, but actually don't see any log except:

DEBUG: Shutting down ComponentActorThread

when I refresh the SCR bundle.

Romain.


Le 24 août 11 à 15:43, David.Humeniuk@L-3Com.com a écrit :

> I know this can happen if there is a failure to activate the  
> component.  Do you have all the SCR logging turned on?
>
> David Humeniuk
>
>
> -----Original Message-----
> From: Romain Deltour [mailto:rdeltour@gmail.com]
> Sent: Wednesday, August 24, 2011 9:34 AM
> To: users-help@felix.apache.org
> Subject: Rép : Bundle unsatisfied when using Declarative Services
>
> Hi,
>
> It seems I'm facing a similar issue to Mohnish's below. I have an
> unsatisfied component while all its references are satisfied.
>
> Here's the SCR info:
>
> -> scr list
>    Id   State          Name
> [   8] [registered   ] converter-parser
> [  10] [registered   ] XSLT Step
> [   1] [unsatisfied  ] command-line
> [   2] [registered   ] calabash-xproc-engine
> [   9] [registered   ] Message Step
> [   6] [active       ] module-registry
> [   3] [active       ] expath-package-parser
> [   5] [registered   ] Dynamic Calabash Configuration Factory
> [   4] [active       ] module-uri-resolver
> [   0] [unsatisfied  ] org.daisy.pipeline.webservice
> [   7] [registered   ] script-registry
> -> scr info 1
> ID: 1
> Name: command-line
> Bundle: org.daisy.pipeline.cli (14)
> State: unsatisfied
> Default State: enabled
> Activation: immediate
> Configuration Policy: optional
> Activate Method: activate (declared in the descriptor)
> Deactivate Method: deactivate
> Modified Method: -
> Reference: script-registry
>     Satisfied: satisfied
>     Service Name: org.daisy.pipeline.script.ScriptRegistry
>     Multiple: single
>     Optional: mandatory
>     Policy: static
> Reference: module-registry
>     Satisfied: satisfied
>     Service Name: org.daisy.pipeline.modules.ModuleRegistry
>     Multiple: single
>     Optional: mandatory
>     Policy: static
> Reference: xproc-engine
>     Satisfied: satisfied
>     Service Name: org.daisy.common.xproc.XProcEngine
>     Multiple: single
>     Optional: mandatory
>     Policy: static
> Properties:
>     component.id = 1
>     component.name = command-line
>
> I'm using scr version 1.6.0, and cleaned the cache configured in the
> felix.cache.rootdir property to no avail. It works well when the
> project is run with Equinox (via Eclipse PDE).
>
> Any help would be much appreciated!
>
> Thanks,
> Romain.
>
>> De : Felix Meschberger <fmeschbe@gmail.com>
>> Date : 22 octobre 2009 07:09:58 HAEC
>> À : users@felix.apache.org
>> Objet : Rép : Bundle unsatisfied when using Declarative Services
>>
>>
>> Hi,
>>
>> Just a follow up to the list ...
>>
>> Mohnish and I have been trying to track this issue off list. After he
>> cleared his bundle cache and restarted the framework, the issue went
>> away.
>>
>> Its hard to tell, what was going on there, maybe an old bundle lying
>> around or such. For now the problem seems to have gone ..
>>
>> Regards
>> Felix
>>
>> mohn3310 schrieb:
>>> Hello,
>>>
>>> I've recently converted from using Activators to Declarative
>>> Services. I've
>>> run into an issue where all dependent services are satisfied, but  
>>> the
>>> overall state of the component is still unsatisfied. Any idea how
>>> it could
>>> get into this state?
>>>
>>> Here's the output of 'scr info':
>>>
>>> -> scr info 9
>>> ID: 9
>>> Name: MyBundle
>>> Bundle: com.myco.MyBundle (41)
>>> State: unsatisifed
>>> Default State: enabled
>>> Activation: immediate
>>> Services: com.myco.MyBundleService
>>> Service Type: service
>>> Reference: logService
>>>   Satisfied: satisfied
>>>   Service Name: org.osgi.service.log.LogService
>>>   Multiple: single
>>>   Optional: mandatory
>>>   Policy: static
>>> Reference: persistenceService
>>>   Satisfied: satisfied
>>>   Service Name: com.myco.persistence.PersistenceService
>>>   Multiple: single
>>>   Optional: mandatory
>>>   Policy: static
>>> Reference: httpService
>>>   Satisfied: satisfied
>>>   Service Name: org.osgi.service.http.HttpService
>>>   Multiple: single
>>>   Optional: mandatory
>>>   Policy: static
>>> Properties:
>>>   component.id = 9
>>>   component.name = MyBundle
>>>   service.pid = MyBundle
>>>
>>> And here's the scr-plugin generated serviceComponents.xml file:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <components xmlns:scr="http://www.osgi.org/xmlns/scr/v1.0.0">
>>>   <scr:component enabled="true" immediate="true" name="MyBundle">
>>>       <implementation class="com.myco.impl.MyBundleServiceImpl"/>
>>>       <service servicefactory="false">
>>>           <provide interface="com.myco.MyBundleService"/>
>>>       </service>
>>>       <property name="service.pid" value="MyBundle"/>
>>>       <reference name="logService"
>>> interface="org.osgi.service.log.LogService" cardinality="1..1"
>>> policy="static" bind="bindLogService" unbind="unbindLogService"/>
>>>       <reference name="persistenceService"
>>> interface="com.myco.persistence.PersistenceService"
>>> cardinality="1..1"
>>> policy="static" bind="bindPersistenceService"
>>> unbind="unbindPersistenceService"/>
>>>       <reference name="httpService"
>>> interface="org.osgi.service.http.HttpService" cardinality="1..1"
>>> policy="static" bind="bindHttpService" unbind="unbindHttpService"/>
>>>   </scr:component>
>>> </components>
>>>
>>> Thanks for your help.
>>>
>>> Mohnish
>>
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Mime
View raw message