If you are using the Equinox implementation of DS try adding the system
property
equinox.ds.print=true
You get all manner of handy output. -consolelog is also useful in this. If
you run Equinox with -console then you can use commands like "ls" and "conf" to
investigate what's happening in DS land.
Jeff
On 2010-05-20, at 8:59 AM, Peter Kriens wrote:
> :-) Look in the OSGi log ... There are extensive logs of anything that goes
> wrong with DS. It is actually one of the attractive aspects of DS that you
> can just throw an exception when you do not like something, being sure that
> it gets logged by DS.
>
> Kind regards,
>
> Peter Kriens
>
>
> On 20 mei 2010, at 12:59, Eugen Reiswich wrote:
>
>> Hi,
>>
>> I am using now declarative services for a while and I really like the idea
>> of avoiding all that boiler plate ServiceTracker code. But what really
>> frustrates me is that I don't get any feedback (e.g. exceptions) when I
>> misspell my bind and unbind service methods or when I accidentally use the
>> same service component id for several components. In this case the service
>> components either do not start or do not behave as expected. At the same
>> time as developer I don't get any feedback what might be wrong. Is there
>> any "verbose" mode for OSGi declarative services or could this be an eclipse
>> preference problem? Any hint would be appreciated!
>>
>> Regards,
>> Eugen
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
