Although commons logging has some classloader issues when used in
multiple classloaders and it tends to show up in the top level
classloaders in some containers (like tomcat)...... IMHO, its a good
solution that can easily be bound to a number of providers.
I would not spend time on creating out own, there plenty of other
alternatives out there beside commons-logging.
Ian
On 4 May 2008, at 13:29, Vincent Siveton wrote:
Hi,
Shindig code uses java.util.logging which is a primary logging API
without outofbox best features like smtp (need third party).
So, WDYT to switch to Commons Logging API or create our own API? It
will be more easy to switch to log4j or logback or whatever.
Also, I think we need an howto log guide (see SHINDIG-224)
Cheers,
Vincent
