Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Debugging Declarative Services resolution
Debugging Declarative Services resolution [message #991630] Wed, 19 December 2012 17:17 Go to next message
Johan Van Noten is currently offline Johan Van Noten
Messages: 18
Registered: July 2009
Junior Member
A customer of ours created an app with about 60 bundles containing about 100 component XMLs.
A mixture of:
* static 1..1 bindings
* dynamic 0..n bindings
* required configuration management
* some immediate, others not

There seem to be issues with the component resolution process, so some debugging is required.
We feel it is very difficult to keep track of the resolution chain.
Component resolution can easily go 4 levels deep trying to concretize delayed components, etc.

What are we already using?
* equinox.ds.debug=true and equinox.ds.print=true
* Felix Webconsole (component part)
* debugging through PDE in the Equinox ds code Smile

Are there any good tools to get a view on the resolution process?
Any proven debug strategies / best practices for debugging the resolution process?

FYI: Equinox 3.8.1

Thanks,
Johan
Re: Debugging Declarative Services resolution [message #991905 is a reply to message #991630] Thu, 20 December 2012 08:04 Go to previous messageGo to next message
BJ Hargrave is currently offline BJ Hargrave
Messages: 54
Registered: July 2009
Member
One other thing that might help is Xray. It understands DS components and can provide a visual overview.
Re: Debugging Declarative Services resolution [message #991984 is a reply to message #991905] Thu, 20 December 2012 10:45 Go to previous message
Johan Van Noten is currently offline Johan Van Noten
Messages: 18
Registered: July 2009
Junior Member
Good suggestion.
It certainly helps for determining the current state.
For bigger amounts of bundles/services (as indicated above) it is quite difficult to keep track. Highlighting the connectors could maybe help.

The kind of issues that we were researching were rather on the resolution part of DS (it got stuck while resolving components). This is not linked to the spec, but rather to the implementation (i.c. Equinox). We should have realised that therefore this question cannot be tackeled generically.

Thanks for your answer. I immediately added X-ray to my toolset.

Previous Topic:Declarative Services re-use implementation class
Next Topic:Launch RCP App without plugins folder
Goto Forum:
  


Current Time: Sun Apr 20 03:11:12 EDT 2014

Powered by FUDForum. Page generated in 0.01575 seconds