Alin Dreghiciu wrote:
OSGi framework by itself does not set any context class loader by
itself, so, I do not get what do you mean.
What class loader do you expect as a context class loader?
i think both spring framework and equinox provide a context class loader
that mimics the behavior of a jee/web container. i think equinox
provides the buddy system to achieve something similar while spring
framework looks at all started bundles.
ittay
On Tue, Jan 20, 2009 at 10:05 PM, Ittay Dror <[email protected]> wrote:
Hi,
I have a thirdparty code which uses the idiom of finding packages by
looking for a properties file in META-INF:
resources =
Thread.currentThread().getContextClassLoader().getResources(metaInfProperties);
This is done during handling of a request.
The problem is that the context class loader is BundleClassLoader, which
only searches the resources in the bundle it is associated with.
This is not the default class loader that is used. It is set by Jetty
before handling the request. This is because jetty is given it by
pax-web, which creates it in HttpServiceStarted.
My question is why is there a need to replace the default context class
loader (the one set by the osgi container)? Is there a way to override
this behavior?
Thank you,
Ittay
--
--
Ittay Dror <[email protected]>
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
--
--
Ittay
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
