In OSGi, a bundle classloader has access only to packages which the bundle has constraints on (using Import-Package, Require-Bundle) and packages it has locally in the bundle or any attached fragment bundles. The only classes a bundle classloader gets for "free" are the classes in the java.* namespace. In Java the only classloader which can define java.* classes is the boot classloader. What is required by the spec is that the Framework must give access to the java.* packages from the VM to the bundle classloaders. How a Framework does this is implementation specific. The OSGi specification does not specify that the parent classloader of a bundle classloader must be the boot classloader or any other type of classloader. This is a detail left up to the implementers.
HTH.
Tom
From: Alan Cabrera <[EMAIL PROTECTED]>
To: OSGi Mail List Developer <[email protected]>
Date: 11/05/2007 12:25 AM
Subject: [osgi-dev] Parent class loader
Maybe I'm being a bit dense but it's not clear to me where the parent
class loader comes from. Is this implementation specific?
Regards,
Alan
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
