[teiid-issues] [JBoss JIRA] Commented: (TEIID-672) Replace homegrown Logging with Log4J

Ramesh Reddy (JIRA) jira-events at lists.jboss.org
Wed Jun 17 15:55:56 EDT 2009


    [ https://jira.jboss.org/jira/browse/TEIID-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12472595#action_12472595 ] 

Ramesh Reddy commented on TEIID-672:
------------------------------------

One of the reason Teiid still depends upon its own logging façade framework (like commons logging) is so that it can dictate the file names and configuration. It is arguable that this can be completely replaced with some like commons-logging or slf4j. 

> Replace homegrown Logging with Log4J
> ------------------------------------
>
>                 Key: TEIID-672
>                 URL: https://jira.jboss.org/jira/browse/TEIID-672
>             Project: Teiid
>          Issue Type: Task
>          Components: Common
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>             Fix For: 6.2.0
>
>
> Teiid has Logging framework as well the implementation that supports the frame work, like Log Listeners, File appenders and Rolling File appenders, Platform loggers etc. Except for LogManager.java and its required constants, everything else can be replaced with Log4J implementation.
> Designer seems to be only dependent upon the "Logger" interface, so that will be kept. 
> A "log4j.properties" configured for "embedded" and "server" runtimes to configure the logging destinations.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       




More information about the teiid-issues mailing list