"David Wynter" <[EMAIL PROTECTED]> writes:
>I was fooled, because I made 2 changes at once. The change that actually
>fixed it was in TR.properties
>"log4j.file = WEB_INF/classes/log4j.properties" instead of "log4j.file =
>/WEB_INF/classes/log4j.properties"
Ah, ok. That explains a lot! Are you using different Servlet
containers on your Win2k and Win2k3 box?
I do know (there was a discussion about two years ago) about the
meaning of getRealPath("/") and getRealPath("") in various
containers. If you're brave, you can get
ftp://ftp.hometree.net/pub/webroottest/webroottest.war, deploy it to
your containers; access ..../webroottest/webroottest and send me the
result on your W2k and your W2k3 box.
Do you BTW use tomcat5?
Regards
Henning
>It seems that Win 2003 server is fussy where Win 2000 Server is not. i.e.
>the latter of these 2 actually works on Win 2000 Server and not on Win 20030
>Server.
>David
>-----Original Message-----
>From: David Wynter [mailto:[EMAIL PROTECTED]
>Sent: 25 May 2004 17:16
>To: Turbine Users List
>Subject: RE: FW: Win2003 Logging not working for T2.3?
>Hi,
>The only way I got it to work was to have both commons-logging.properties
>and log4j.properties on the classpath (by putting them into
>WEB-INF/classes/). I also made the changes to log4j.file path in
>TR.properties as Henning suggested.
>I am running T2.3 with your patches from last October.
>Thx.
>David
>-----Original Message-----
>From: Folkens, Brad [mailto:[EMAIL PROTECTED]
>Sent: 25 May 2004 13:34
>To: 'Turbine Users List'
>Subject: RE: FW: Win2003 Logging not working for T2.3?
>That commons-logging.properties file may need to be copied into the
>classpath too, depending on the commons-logging version you're using.
>Bradford A. Folkens
>[EMAIL PROTECTED]
>> -----Original Message-----
>> From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, May 25, 2004 6:50 AM
>> To: [EMAIL PROTECTED]
>> Subject: Re: FW: Win2003 Logging not working for T2.3?
>>
>> "David Wynter" <[EMAIL PROTECTED]> writes:
>>
>> >Here is the content of the Log4j.properties
>>
>> >-------------------------------------------------------------------->
>>
>>
>> >#
>> >-------------------------------------------------------------
>> ----------
>> >-
>> >#
>> ># Logging Configuration
>> >#
>> ># $Id: Log4j.properties,v 1.3 2003/06/20 00:10:22 henning Exp $ # #
>> >-------------------------------------------------------------
>> ----------
>> >-
>>
>> >applicationRoot = d:/Apps/tdk/webapps/transformer
>>
>> Remove this. applicationRoot gets set by the Turbine core
>> when the log4.properties are read in. Application root is
>> what it is. Root of the application. If you want to put your
>> logfiles in a different location, try using a different
>> variable name.
>>
>> >This file is in .../WEB-INF/classes so it is on the classpath
>>
>> I'd suggest that you move it to WEB-INF/conf
>>
>> >The TurbineResources.properties has the following line
>>
>> >log4j.file = /WEB-INF/classes/Log4j.properties
>> ^
>> Try removing the absolute reference. Some containers seem to
>> have problems with this.
>>
>> >and the WEB-INF/CONF has a commons-logginf.properties fiel with the
>> >following 2 line sin it
>>
>> >org.apache.commons.logging.LogFactory=org.apache.commons.logg
>> ing.impl.L
>> >og4JF
>> >actoryImpl
>> >org.apache.commons.logging.Log=org.apache.commons.logging.imp
>> l.Log4JLog
>> >ger
>>
>> Ugh. I don't even know whether this is loaded or used. As far
>> as I know (are you talking about 2.3 or 2.4-dev here?), at
>> least the 2.3 core has the logger hard coded to log4j.
>>
>> >Logging is the worse part of Turbine, cinfig is flaky as hell in my
>> >experience. I tried to work out how it worked and failed so cannot
>> >contribute patches unfortunately.
>>
>> Did you ever work with the 2.2 core? If you did, then you're
>> allowed to write about flakey logging. ;-)
>>
>> Regards
>> Henning
>>
>> --
>> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
>> [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
>>
>> RedHat Certified Engineer -- Jakarta Turbine Development --
>> hero for hire
>> Linux, Java, perl, Solaris -- Consulting, Training, Development
>>
>> "Fighting for one's political stand is an honourable action,
>> but re- fusing to acknowledge that there might be weaknesses
>> in one's position - in order to identify them so that they
>> can be remedied - is a large enough problem with the Open
>> Source movement that it deserves to be on this list of the
>> top five problems."
>> -- Michelle Levesque, "Fundamental Issues with
>> Open Source Software Development"
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honourable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
