A value of null will cause the parent class loader to be set to:
Thread.currentThread().getContextClassLoader();
The context class loader for a given thread is the class loader that the
threads creator wants you to use (good for servlet containers),
so looks right to me. If its not set, it will use the parent thread's
class loader.
- Mark
John Wang wrote:
Hi guys:
Could it be in method:load in class CoreContainer:
libLoader = SolrResourceLoader.createClassLoader(f, null);
The parent ClassLoader is set to null, shouldn't it be the current
classloader? e.g."
libLoader =
SolrResourceLoader.createClassLoader(f,Thread.currentThread().getContextClassLoader(
));
Thanks
-John
On Sun, Jul 5, 2009 at 11:38 PM, John Wang <john.w...@gmail.com> wrote:
Hi Chris:
The problem is that (at least for me, not a expert spring'er) The
beans are being loaded (and when the class loading issue occurs) at
construction time of FileSystemXmlApplicationContex, the setClassLoader
method by the time can be called is too late.
-John
On Thu, Jul 2, 2009 at 2:26 PM, Chris Hostetter <hossman_luc...@fucit.org>wrote:
: I did try that. The problem is that you can't tell
: FileSystemXmlApplicationContext to load with a different ClassLoader.
why not?
it subclasses DefaultResourceLoader which has the setClassLoader method
Mark pointed out.
-Hoss
--
- Mark
http://www.lucidimagination.com
