[
https://jira.jboss.org/jira/browse/TEIID-672?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-672.
--------------------------------
Resolution: Done
Modified the AdminAPI in regards to LogConfiguration, and mapped the configuration back to
Log4J system underneath. Note that the changes made during the runtime are not persistent
across restarts yet. For that user needs to modify the "log4j.properties" file
directly on the installation folder.
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