On Sat, 26 Mar 2005 17:23:43 -0500, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Remy wrote:
My plan for JULI is to:
What is JULI? I know JCL, UGLI, Log4J, j.u.logging ... hmmm ... is JULI an acronym for j.u.l-integration?
JULI is a java.util.logging implementation. It currently lives here: http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/juli/
I think the API, java.util.logging, got many things right: - the API functionality itself seems good enough to me - it has a design making it easy to extend once you figure out the API (no docs), since you simply have to replace the main LogManager - it is extremely robust in a container environment (one-per-VM singleton design for the LogManager, and the core classes are hard to replace: this means classloading problems are almost impossible)
What happens when multiple independent webapps use j.u.logging? Can each webapp have its own personal logging configuration file? And if so, is logging correctly cleaned up when the webapp is undeployed?
We'll see how well this works soon, as it is used to provide logging defaults in the new Tomcat build (the previous defaults were using java.util.logging as well, but with the default implementations, and consequently didn't do anything useful).
I�ll just point out there are two quite independent logging concepts here: logging of internal container details, and logging by webapp code.
I�m quite sure you can use j.u.logging for Tomcat�s internal logging. Have you also looked into the issues relating to what happens when a webapp uses j.u.logging API to log messages (or when some library that app depends upon does so)?
Is there any pace for this in the logging project, or should I seek another home ?
If not in Logging, perhaps in Jakarta Commons? It appears that we have several folks trying to move JCL to the next level, and both you and Richard Sitze ahould have considerable common ground in terms of needs.
I do consider commons, but commons does this funny things to your package names, and it's a bit annoying ;) Also, I am a bit confused about the logging project scope. Does it want to host logging related projects or not ?
It seems to me that apache-logging would be a better home for this project than commons.
Note, however, that commons projects are *not required* to use org.apache.commons as a package prefix as far as I know.
Regards,
Simon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
