On 1/11/06, Manfred Geiler <[EMAIL PROTECTED]> wrote: > 2006/1/10, Korhonen, Kalle <[EMAIL PROTECTED]>: > > If one really wants to combine java logging to log4jLogs, I'd think you > > should be able to fairly easily write a java log handler using log4j > > logger (don't know how the performance of such a beast would be > > though...). > > And here we go: configurate logging in a central (!) logger.properties > file that sits in the JRE lib dir. Aaaargh. Think of multiple > container or application instances on one machine. > A log4j.xml file in my container, that I can change during runtime > (like in JBoss) - that's what really rocks!
A good J2EE 1.4 container should support configuring java.util.logging per app. Any that do not support this are missing an important feature. You're completely correct that commons-logging should be used for MyFaces as long as the JDK 1.3 requirement stands - but moving forward, java.util.logging is the standard, and that's what MyFaces should use, even if log4j has technical advantages. -- Adam > > Well, although I think that log4j is the best logging solution, IMO we > must not force it upon MyFaces end users. > > So, I still think that commons-logging is the best tradeoff available. > > +1 for commons-logging as the one-and-only logging dependency for all > MyFaces packages. > > Manfred >
