I guess we have to disagree that not having a common interface is not a problem with regard to logging. I can put configuration files for com.pooper.scooper.Logger outside of the EAR and tell the sysadm to familiarize himself in the intricacies of configuring that package but it might not go over too well. I suppose it depends on which species you're working with:)
----- Original Message ----- From: "Andreas Mecky" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 14, 2003 8:26 AM Subject: Re: [JBoss-user] JBoss & Log4J The problem is not that there is no common logging interface (forget about the JDK1.4 logging). Nor is there a common API for configuration and something like that. This is not a problem. The problem is that these configuration files are logger definition files should not be packaged inside an ear. Because this is exactly what makes life a hell to go through as a sysadmin. I am developer and I have fought many battles with these weasels :) ----- Original Message ----- From: "Rod Macpherson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 14, 2003 4:56 PM Subject: Re: [JBoss-user] JBoss & Log4J The database driver analogy fails because your JDBC code has a standard API while logging does not. Putting the database driver in an EAR file (you may not have a WAR file at all) does seem like overkill in terms of isolation but it's not entirely without merit. The other issue is that an application may very well have it's own logging requirements and you want to be able to view those logs independent of the system logs. I would venture to say that most people centralize logging in a wrapper class and delegate to make it simple to switch it out, however, that is a design choice that cannot be enforced. Logging calls get weaved into everything and if somebody wants to tote a logging API with them (versus wrapping it with a layer of insulation) that is up to them. Your point of view is correct in theory but the specification says nothing about having to supply configurable logging in the server. ----- Original Message ----- From: "Jim Crossley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 14, 2003 6:59 AM Subject: Re: [JBoss-user] JBoss & Log4J Anders Engstr�m <[EMAIL PROTECTED]> writes: >> Remeber that the conf directory is jsut a part of the class path and the >> log4j config file in there is a standard log4j xml config file. I >> usually add my logging information to it. > Maybe I wasn't clear enough - but this is exactly the scenario we want > to avoid. The deployed application should have a self-contained logging > configuration. There should be no need to modify _server_configuration_ > files to enable/modify logging for a deployed application. I must respectfully disagree. The app server is precisely where you want logging configuration. IMHO, it is very poor form for deployable units to define their own logging parameters. It's akin to packaging their own JDBC drivers in WEB-INF/lib -- ugh!! Something like logging requires centralized control -- it's one of the compelling reasons for using an app server in the first place! What's stopping a poorly-configured app from filling up the disk with log output? The person responsible for disk usage is the sysadmin. He won't be happy having to hunt through his deployed web apps looking for a bad log4j config file. Just my $.02 -- Jim Crossley http://crossleys.org/~jim 404.409.9085 ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Bis zu 100 MB Speicher bei http://premiummail.yahoo.de ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
