'. '

ThreadContextClassLoader

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(New page: Java provides way to associate a special class loader with each of executing threads. This is handy, as often the executing class needs access to more than its own classes. However it ...)
Line 1: Line 1:
[[Java]] provides way to associate a special class loader with each of executing threads. This is handy, as often the executing class needs access to more than its own classes. However it is also acompanied with problems. Especially in a [[modular system]]s. When it is not easy to control thread management, it is hard to make sure the [[ThreadContextClassLoader]] is specified properly.
[[Java]] provides way to associate a special class loader with each of executing threads. This is handy, as often the executing class needs access to more than its own classes. However it is also acompanied with problems. Especially in a [[modular system]]s. When it is not easy to control thread management, it is hard to make sure the [[ThreadContextClassLoader]] is specified properly.
-
Things get even more complicated as each [[modular runtime environment]] may have different idea what [[ThreadContextClassLoader]] shall do. I know what I am talking about, I have spend last month trying to reimplement [[Netbinox]] [[OSGi]] container to provide [[ThreadContextClassLoader]] which is friendly to [[NetBeans]] modules as well as bundles comming from [[Equinox]] world.
+
Things get even more complicated as each [[NetBeans Runtime Container|modular runtime container]] may have different idea what [[ThreadContextClassLoader]] shall do. I know what I am talking about, I have spend last month trying to reimplement [[Netbinox]] [[OSGi]] container to provide [[ThreadContextClassLoader]] which is friendly to [[NetBeans]] modules as well as bundles comming from [[Equinox]] world.

Revision as of 16:52, 29 October 2010

Java provides way to associate a special class loader with each of executing threads. This is handy, as often the executing class needs access to more than its own classes. However it is also acompanied with problems. Especially in a modular systems. When it is not easy to control thread management, it is hard to make sure the ThreadContextClassLoader is specified properly.

Things get even more complicated as each modular runtime container may have different idea what ThreadContextClassLoader shall do. I know what I am talking about, I have spend last month trying to reimplement Netbinox OSGi container to provide ThreadContextClassLoader which is friendly to NetBeans modules as well as bundles comming from Equinox world.

Personal tools
buy