[
https://jira.jboss.org/jira/browse/TEIID-361?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-361:
------------------------------------
LogManager will be made it into a just a shell class which facilitates the interaction
between the LogConfiguration and LogListener through its static methods. Nothing more.
Then each individual application (server, embedded) will inject the LogConfiguration and
LogListeners at the start up time according to their needs.
Platform logger lost its static nature in starting, so no more of pre-configured implicit
loggers associated auto magically and create confusion. Platform logger implements
queuing mechanism for the LogMessages, and that is the extent of its responsibilities.
It is no longer associated directly with LogManager, the configuration need to tie them
together. This paves way to replace Teiid's home grown log file appenders with
something like Log4J.
LogManager is tied with Current Conficuration and makes it hard to
use with Embedded
------------------------------------------------------------------------------------
Key: TEIID-361
URL:
https://jira.jboss.org/jira/browse/TEIID-361
Project: Teiid
Issue Type: Task
Components: Common
Affects Versions: 6.x
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.0.0
Original Estimate: 1 day
Remaining Estimate: 1 day
Remove the configuration of logging listeners and configuration out of the Log Manager,
and make them injectable. Once this is done Server and Embedded can use it how it fits
their needs.
--
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