For Equinox, it depends on what version you are using.  The Luna release (Equinox framework version 3.10.x) is the first to use the same resolver implementation as felix and should provide the same level of error messages for uses constraint violations.  Prior to Luna the error messages would not very helpful for uses constraint violations.
 

Tom
 
 
----- Original message -----
From: "Lurie, Aron" <a.lu...@wustl.edu>
Sent by: osgi-dev-boun...@mail.osgi.org
To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
Cc:
Subject: Re: [osgi-dev] Resolving OSGi "Uses Constraint Violations" Using Anzo
Date: Tue, Aug 11, 2015 11:04 AM
 

Hi Richard,

 

Thanks for your comments, you make some good suggestions. One way to create visualizations for a failed resolve might be to have the resolver generate the relevant RDF, and load that into a server that resolved (and thus runs the visualization tool).

 

Can you point me to an example of what Equinox or Felix provides in terms of uses constraint violation information? I use Equinox primarily, and my experience was that only a small amount of high level information (the bundle that couldn't be resolved, and the package with the uses constraint) was provided regarding the cause of the violation. It didn't point out which uses constraint was violated.

 

Thanks,

Aron

 

From: osgi-dev-boun...@mail.osgi.org <osgi-dev-boun...@mail.osgi.org> on behalf of Richard S. Hall <he...@ungoverned.org>
Sent: Tuesday, August 11, 2015 9:30 AM
To: OSGi Developer Mail List
Subject: Re: [osgi-dev] Resolving OSGi "Uses Constraint Violations" Using Anzo
 
Hello,

That is interesting and tools and visualizations to help in this area are certainly needed. However, depending on your OSGi framework you can get a pretty precise description of a uses constraint violation. For example, both the Felix framework and Equinox use the same resolver which spits out a pretty detailed textual "graph" showing you how the uses constraint violation occurred. So, following the documented steps and learning SPARQL to get the same information is probably a little too much effort.

Still, it is interesting to be able to visualize this stuff. Perhaps you should look into instrumenting the Felix resolver so you can create your visualizations for a given failed resolve permutation, rather than having to use your "back off" approach.

-> richard

 
On 8/11/15 09:45 , Lurie, Aron wrote:

 

Hi All,

I've made a contribution to the literature on resolving OSGi uses constraint violations and I would like to bring it to your attention and open it up for discussion here. 
 

 

http://blog.cambridgesemantics.com/resolving-osgi-uses-constraint-violations-using-anzo

Resolving OSGi "Uses Constraint Violations" Using Anzo
Technical, ANZO, Advanced

Thanks,

Aron
 
 
 
 
_______________________________________________
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

Reply via email to