I would say that where you place the logs is not as important as how that location gets configured for the webapp. Two things to AVOID are 1) requiring the app to be reconfigured whenever a new war is deployed and 2) hard coding the location of the logs and/or the log4j configuration.
You can usually get around these by setting system properties or setting variables in the JNDI environment provided by the web container. System properties are not as desirable since they're exposed to ALL webapps in the container. On Sat, 2011-02-05 at 13:05 +0530, Umesh Awasthi wrote: > Hi All, > > I am working on a webapplication and it is going to use looging in good way > for its import export process.so we need to store log files at some place so > that when ever some needs to consult logfiles can do that. > > One thing we can do is to create afolder in the webapps and place alll such > related files in this location but this approach seems to have one major > issue the moment we deploy a new war all previosu logs will be deleted and > we are lost. > > my question is in such case what is the best place to store your application > related log files? > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
