Hi, First of all... Legacy stuff needs to be fixed and remove this phenomenon... From Grady Booch and prior / recent, there should be ZERO TOLERANCE for circular dependencies amongst packages PERIOD; Second, NO ONE should be designing bundles with circular dependencies; This is 2009; It's bad enough no one can do a build (although I am working on changing the way we do builds, by simply creating the notion of a "source bundle"; I am working on a component to build "source bundles"... this is not the same as sigil, although sigil is moving toward the proper goal, but they didn't hit the mark... yet); Anyway, Equinox has a back door called "eclipse buddy policy" which you would set to "dependent" (presume you can google for that); I applaud Felix for sticking to their guns, although I'm a little behind the curve (about 8 months or so) and haven't been keeping up with the state of things; So, based on likely dated knowledge, hopefully still valid, Felix doesn't provide support for circular dependencies **amongst** bundles, but I anticipate being corrected on the matter; To paraphrase Grady Booch, it's called "separate of API from IMPL"; I am not pleased with the state of any/all OSGi frameworks to date in that they do not do a decent job of separating API from IMPL; The framework service mentality is there (minus versioning at the service level... only at the package and bundle levels), but the practices I've seen just don't take this seriously; If you properly separate API from IMPL, you are just about at 100% circumvention of circular dependencies... With however many grains of salt... "The framework is the build / the framework is the convention -- hopefully coming soon to an open source release near you"... Cheers...
________________________________ From: [email protected] on behalf of cato kato Sent: Fri 8/28/2009 2:30 PM To: [email protected] Subject: [osgi-dev] Circular Dependency Hi, I have a simple problem, but because i am newbei i cannot find the solution :) I have two (or more) bundles. Lets say A and B. Both A (db pool mech.) and B (snmp and alarm) depends each other. So this dependency causes circular references. I want to handle this situatian correctly. What would you suggest to handle this situation in osgi environment. Thank you. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
<<winmail.dat>>
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
