[ http://issues.apache.org/jira/browse/BEEHIVE-778?page=all ]
Eddie O'Neil updated BEEHIVE-778: --------------------------------- Fix Version: V1 (was: TBD) Description: Currently, the database control uses org.apache.log4j directly for logging. In order to allow for plugging in different loggers, the control should use commons-logging. For an example, take a look at NetUI's log infrastructure here: http://svn.apache.org/viewcvs.cgi/incubator/beehive/trunk/netui/src/util/org/apache/beehive/netui/util/logging/Logger.java?view=markup This exposes an org.apache.commons.logging.Log implementation that is used by the rest of NetUI. was: Currently, the database control uses org.apache.log4j directly for logging. In order to allow for plugging in different loggers, the control should use commons-logging. For an example, take a look at NetUI's log infrastructure here: http://svn.apache.org/viewcvs.cgi/incubator/beehive/trunk/netui/src/util/org/apache/beehive/netui/util/logging/Logger.java?view=markup This exposes an org.apache.commons.logging.Log implementation that is used by the rest of NetUI. Environment: Bringing this up to fix in V1. If anyone wants to take care of this one, feel free to take it off my list. > switch database control onto commons logging > -------------------------------------------- > > Key: BEEHIVE-778 > URL: http://issues.apache.org/jira/browse/BEEHIVE-778 > Project: Beehive > Type: Improvement > Components: System Controls > Versions: v1m1, V1Alpha, V1Beta > Reporter: Eddie O'Neil > Fix For: V1 > > Currently, the database control uses org.apache.log4j directly for logging. > In order to allow for plugging in different loggers, the control should use > commons-logging. > For an example, take a look at NetUI's log infrastructure here: > http://svn.apache.org/viewcvs.cgi/incubator/beehive/trunk/netui/src/util/org/apache/beehive/netui/util/logging/Logger.java?view=markup > This exposes an org.apache.commons.logging.Log implementation that is used by > the rest of NetUI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira