I think it is log4j which wants to look for config files on the thread
context loader.
Regards,
Antoine
On 1/29/2011 1:27 PM, Mitch Gitman wrote:
Here's the solution that finally worked for me, and that includes locating
the log4j class. This is all in my Ant task:
ClassPathXmlAppli
Here's the solution that finally worked for me, and that includes locating
the log4j class. This is all in my Ant task:
ClassPathXmlApplicationContext applicationContext = new
ClassPathXmlApplicationContext();
applicationContext.setClassLoader(this.getClass().getClassLoader());
Here's another old post that corroborates the one I linked to:
http://www.mail-archive.com/user@ant.apache.org/msg22871.html
This poster isolated the problem with the base class of
ClassPathXmlApplicationContext,
org.springframework.core.io.DefaultResourceLoader. And I notice that
DefaultResourceL
I have a Spring-based application that I'm exposing through an Ant task,
among other interfaces.
The moment where I run into trouble is when the application tries to use
Spring's ClassLoader-based code to load a Spring application context:
ApplicationContext applicationContext = new
ClassP
