+1 for removing static logging.
-1 for java.util.logging. I like the freedom that commons logging
provides. In my case, I use log4j to email log entries that meet a
specific criteria while others are written to a rotating log. Their may
be way to do this using java.util.logging, I am pretty invested in
commons logging and log4j to change overnight.
Paul Spencer
Werner Punz wrote:
good point if you can hook commons.logging (I know this is somewhat
insane because commons is just a meta logger)
below it, I do not know the core java logging api good enough
but every dependency we can remove is a + from me.
Problem is if we cannot provide a path to hook commons logging into
it we get a huge clash with application and server vendors which
build upon that lib.
Mathias Brökelmann schrieb:
+1 for removing the static.
What is about java.util.logging? Can/Should we use it for 1.2?
IMO it is better to use java.util.logging. Apart from the unusable
default implementation for java.util.logging the reason not to use it
in myfaces 1.1 was the dependency to java 1.4. But jsf 1.2 will only
run with java 5 or higher. So that should not be the problem now. The
default implementation should also not be a problem. IMO it is out of
scope of myfaces. The container vendor is responsible to supply a
better solution as it is done for tomcat. And even if that is not the
case the user might plug its own implementation into
java.util.logging.
2007/2/27, Dennis Byrne <[EMAIL PROTECTED]>:
Alright. Here's my +1 binding. Let's put the nail in this coffin.
Dennis Byrne
