Quoting Konrad Billewicz <[EMAIL PROTECTED]>: > > I'm not sure why what you have wouldn't work? However, the double > backslashes > > are unnecesary (and could, possibly, be breaking things). They tie the > config > > file to a windows box. Just use single forward slashes. This will work on > > both Windows and UNIX systems. > > I read somewhere that they are necesary. But they are working when I place > full > path manually, so they are not a problem. >
Well, they are only necessary with respect to single backslashes escaping the next character in a string. So, you have to escape the escape character. Hence, if you were going to write this... C:\path\to\my\directory ..and you still wanted to use backslashes, you'd need to do.. C:\\path\\to\\my\\directory However, this is unnecessary. Just write it as... C:/path/to/my/directory Furthermore, if you wanted a path that worked for both Unix and Windows, then you could do.. /path/to/my/directory ..as long as the JVM was started from the C: drive. No matter what the reason, I'll always use single forward slashes in preference to 2 backslashes. > > > BTW, wasn't the point to set the REL_PATH propery in code, not in the > config > > file? > > I wish and I have to to place all config variables in one file (it's context > file in Tomcat/conf/Catalina/localhost). So in log4j.properties I can't have > any > configuration variables. That is the reason. > No big deal. So, have a servlet context listener read the context or JNDI param you defined in context.xml and set that as a system property. Then, perform configuration and you can reference your property. I do it all the time. What's preventing you from doing this? Jake > > Best regards, > Konrad Billewicz > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
