Yeah, Dennis, you're right. Sorry, I hadn't quite thought it through (long day yesterday). You probably would have to run exploded if you wanted to write the html file under your webapp, although I wouldn't recommend forcing anyone to deploy exploded. Perhaps you could write to your web server's content directory (if you have a web server)?
I'm with Yoav, I think that it's really up to the server administrator to decide. I think if you're supporting different customers, then they (usually) already have certain policies about where log files go - forcing log files to be accessible via the web might well conflict with these policies (including file permissions). Ken -----Original Message----- From: Doubleday, Dennis [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 6:07 PM To: 'Log4J Users List' Subject: RE: Making HTML log file available through web app No, different servers for different customers. Yes, OK, I suppose I can have a different log4j.xml for each app server and a server-specific Ant deployment target. What should the relative file location be, though, if I deploy an EAR file to the server and there is no exploded context-relative directory to write the logs to? Will I have to deploy exploded in order for that to work? Is that server-dependent? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
