Hi all, I just happen to see below link. Actually i am comparing felix and equinox. (If one ca suggest me if there is good resource already doing it.). I wanted to know, Does this problem still exists in new version? http://ray.media.berkeley.edu/blog/?p=20
it says: * Equinox lets every reference to an unspecified class pass through to shared libraries by setting the <http://wiki.eclipse.org/Equinox_Boot_Delegation> org.osgi.framework.bootdelegation property to "*". * Felix passes no such references to shared libraries, but instead exports a set of non-java.* packages from the System Bundle via the org.osgi.framework.system.packages property. In Felix 1.4.* configurations, this is set indirectly by a JRE-keyed property like “jre-1.5″. As a result, any fairly substantial bundle which is developed and tested only on a default Equinox installation may fail on a default Felix installation, and vice-versa. Let’s say you develop for Equinox first. In that case, your code can casually refer to javax.sql and org.xml.sax classes without mentioning them in a MANIFEST.MF file. Move that bundle to Felix, and they’ll no longer be found: the Felix System Bundle is pitching them, but your bundle ain’t catching. On the other hand, if you develop for Felix first, you’ll probably include explicit OSGi-style imports of those packages - but then when you move to Equinox, there will be no exports to match. Ian Boston <http://blog.tfd.co.uk/2009/04/15/bundle-dependencies/> writes that bundle developers can protect themselves by using Import-Package ;resolution:=optional with abandon, but how many bundle developers routinely do so? (Once I knew what to look for, I quickly spotted several related bug reports against EclipseLink, for example.)
