[news.eclipse.technology.equinox] Re: how to check if DS is running?

["John E. Conlon" <jconlon@xxxxxxxxxx>]

Hi Ande,

Oops -  sorry I sent you the wrong link.  (A good bookmark organization 
more often beats memory and a quick google search;-)

What I really wanted to send you was a link to Ben Vitale's blog on how 
he troubleshot P2 Policy UI and Declarative  Services see:
http://eclipse-ruminations.blogspot.com/2009_06_01_archive.html

This one may also be of interest:
http://eclipse.dzone.com/articles/dependencies-and-services-osgi

Your right you can always create a service and see if it works, but that 
is (services don't start) is typically the reason for troubleshooting ds 
in the first place.

The best way is most often to bring up an OSGi console.  The two 
articles above are Eclipse centric so they focus on the Equinox console, 
but Felix and the other OSGi run times also have OSGi consoles that you 
can use to troubleshoot DS and other OSGi service related problems.

hope this helps,

John




Ande Dietisheim wrote:
> Hi John
>
> thanks for the links! Tom does indeed address the equinox version of DS 
> directly:
>
> http://publicsvn.bestsolution.at/repos/java/examples/EMF-Databinding/at.bestsolution.soccer.app/src/at/bestsolution/soccer/app/intro/Application.java 
>
>
> This might be acceptable in Tom's case (he has an RCP, that's running in 
> equinox anyhow). My usecase is related to ECF and theres no need to 
> restrict thing to be equinox only.
> Whats interesting is that the guys @felix think that there's not other 
> way but to check for the explicit bundles (equinox-version, 
> felix-version, etc.).
>
> A third opiniion suggests to use a dummy, DS declared service. If the 
> dummy service gets registered, I know that DS is running. This sounds 
> like the best option to me.
>
> http://www.mail-archive.com/users@xxxxxxxxxxxxxxxx/msg05205.html
>
> John E. Conlon wrote:
> > Ande,
> >
> > Take a look at the links in:
> > http://dev.eclipse.org/newslists/news.eclipse.technology.equinox/msg05597.html 
> >
> >
> > cheers,
> > John