Hi Curt, I agree with you, and that's why long ago we developed our own logging library, which rolls log files, logs to DB and can be configured "per web application". Now we are looking to migrating to Log4J, even though we still have to check if it will be worthwhile for us. I had a look at the new logging classes that are being included now in the JDK1.4, and it seems the tendence is to centralise everything, which I don't like. I understand though, that for maintenance reasons it might look very attractive. In our case, log configuration files are always located in the same place "/WEB-INF" and follow the same name pattern "*.logger.conf". We then redirect all the log files to the same directory, which is outside the deployed application directory, and you can have all the log files in one place while you know where everything is configured. Easy to find information, easy to mantain and, as configuration changes are detected in runtime, pretty useful. D. PD: I would also add that IMHO, web app security in the J2EE spec is very poorly defined, as specifying mappings in static files and letting containers implement role-users mappings makes applications rigid and non-portable. But that's another story ;).
Curt Smith wrote: > > > Geoff Soutter wrote > >> >> >> I've hacked up an Orion Appender to allow you to log to the >> application.log file, via the Logger instance that Orion installs at >> java:comp/Logger. Here it is in all it's glory, use it however you wish. >> >> Cheers >> >> Geoff >> >> PS, did anyone figure out if it's possible to get orion to roll it's log >> files when they get too big? ;-) >> > How about Orion logs to a log4j output device instead of apps logging to > Orion's log > files? Or did I miss understand this functionality?? > > Personally I feel the new log4j 1.3 features that make it easier for > each application > to have it's xml config file in the .war / .ear so that apps can have > their own (separate) > log files from each other to be a very useful choice. > > My view of the problem of deploying and supporting a j2ee app is the few > features j2ee > put in the spec (a big zero) to allow debugging and logging of app, > feature, bean operations. > I feel we need to drill on the debugging problem until we have a > facility that supports > logging based on session ID, so that we can follow a particular user's > actions and > failures across a cluster and set of services. > > To me, moving to one log file for the universe is the wrong direction? > Any opinions? > > curt
