I'm bringing up this thread to discuss on the logging backend and logging framework in C5.
Our current logging framework uses log4j as the logging backend and support a set of logging APIs (commons-logging, slf4j, java-logging, log4j logger). We currently don't support OSGI LogService. But we need to decide on whether do we need to support this as there were some decision made earlier not to support? This framework is serving well so far, but if we have to support other logging APIs then we will have to write them. *Alternatives* 1. Log4j2 [1] (logging backend only) The next generation of log4j. It is still at the beta stage in release. This looks promising as the numbers of this is way ahead of its predecessor [2]. 2. Pax logging [3] (complete framework) This framework uses a similar concept as ours. It uses log4j as the backend and support a whole set of logging APIs such as commons-logging API, log4J-logger API, jdk-logging, avalon-logger API, knopflerfish-log and tomcat-juli. It also has support for OSGI LogService API. So far we found that Pax logging has the support for all required logging APIs including the support for OSGI LogService. Other projects mostly have written their own way to handle different logging APIs like ours. Thoughts and ideas are welcome ! Thanks, Kishanthan. [1] http://logging.apache.org/log4j/2.x/ [2] http://www.javacodegeeks.com/2013/07/log4j-2-performance-close-to-insane.html [3] https://ops4j1.jira.com/wiki/display/paxlogging/Pax+Logging -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
