On Fri, 13 Jun 2008 23:19:22 +0200, simon wrote: > The second part of the "jar hell" problem is dependencies which *are* > exported as part of a bundle's public API. > > For example, a bundle exports a class with this API: > public boolean isInRange( > org.apache.lang.math.DoubleRange range, double val); > > Now doesn't loading that bundle in an OSGi app limit the entire app to > having just one common version of lang, just like a non-OSGi app would be?
Bundles and their exported classes can be versioned, with ranges and all; *without* having to mutilate the package names. At least that is my understanding, based on reading about the peer class loader stuff. -h --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
