[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] Re: System and context class loaders
- From: "Steven E. Harris" <seh@xxxxxxxxx>
- Date: Thu, 24 May 2007 09:56:31 -0700
- Cancel-lock: sha1:qHhqzT2RyI0xp9j6YeL7wSqr4es=
- Delivered-to: firstname.lastname@example.org
- Organization: SEH Labs
- User-agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.13 (cygwin32)
"Steven E. Harris" <seh@xxxxxxxxx> writes:
> However, if I set the osgi.parentClassloader property to anything
> other than "boot" (or empty) or "ext", my
> hookconfigurators.properties files are no longer read in my
> framework extension bundles, or perhaps those files are read but the
> bundles themselves don't wind up on the class path.
I confirmed that the hookconfigurators.properties files are not
discovered in HookRegistry.mergeFileHookConfigurators(). The class
loader used there (via getClass().getClassLoader()) is the Equinox
startup class loader (with my hook configurator JARs on its path) if
osgi.parentClassloader is empty or "boot", but it's a different class,
but it's a different class loader if osgi.parentClassloader is "app"
Is this because the HookRegistry class can be loaded by the startup
class loader's parent, if the parent is non-null?
Steven E. Harris