Relative paths in MMBase log4j implementation

[Pierre van Rooden]

If you specify a relative path in the log4j.xml file as the path to the 
logfile for MMBase, the current implementation pick this up as a path 
relative to the current working directory of the java process (whichs 
eems to be '/' in our case).

Our administrators figured that it would be more interesting if the path 
is relative to some path determined by or configured in the appserver 
where you are running the application from.
This would allow you to make one webapp, then run that webapp under 
different appserver instances, and have different log files for each 
instance.

i.e. the webapp is under:
/usr/webapps/my_webapp
teh servers run duenr:
/usr/tomcat/server1
/usr/tomcat/server2
etc...
if bioths ervers run 'my_webapp' (i.e. by symlinking and configuration 
in server .xml, the logs for this webapp should then appear under

/usr/tomcat/server1/logs
/usr/tomcat/server2/logs
and so on.
Right now, specifying a relative path doesn't work properly.
Does anyone have an idea how best to implement this?
--
Pierre van Rooden
Mediapark, C 107 tel. +31 (0)35 6772815
"Never summon anything bigger than your head."