DE BENEDICTIS DAVIDE wrote:
<>Hummm lately that list should be heated, Wherever I go I see problems with classloaders and most of the time you think is an app error...
Yeah, that's what it was. My ant target looked something like:
<classpath>
<pathelement path="${classpath}"/>
<pathelement path="${tests.classes}"/>
<pathelement path="${application.dest.classes}"/>
</classpath>I changed it to:
<classpath>
<pathelement path="${application.dest.classes}"/>
<pathelement path="${classpath}"/>
<pathelement path="${tests.classes}"/>
</classpath>and it now looks for log4j.properties in .../WEB-INF/classes before looking through the various jars (I'm using JDK 1.4.2_03). Presumably all classloaders will search for resources similarly.
BTW, the offending Jar (at least the first one I found) was xdoclet-1.2.1. Why would they put a log4j.properties file in that jar? I guess that's a question for the xdoclet list.
Thanks for the nudge,
- Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
