[jboss-jira] [JBoss JIRA] Commented: (JBLOGGING-58) Support setting the logging provider explicitly
[
https://issues.jboss.org/browse/JBLOGGING-58?page=com.atlassian.jira.plug...
]
David Lloyd commented on JBLOGGING-58:
--------------------------------------
The provider selection should be a strictly symbolic name set via system property only,
with choices of "log4j", "jdk", "jboss", and
"slf4j". An API is not feasible because the logging provider occurs during
class initialization before any user code has a chance to run. The system property should
be called "jboss.logging.provider".
Support setting the logging provider explicitly
-----------------------------------------------
Key: JBLOGGING-58
URL: https://issues.jboss.org/browse/JBLOGGING-58
Project: JBoss Logging
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 3.0.0.Beta4-jboss-logging
Reporter: Dan Allen
Assignee: David Lloyd
Priority: Minor
Fix For: 3.1.0.Beta1
Currently, JBoss Logging uses a classloading approach to look for a logging provider
based on a hardcoded order of precedence. While this is sufficient for the default case,
there should be a way to specify the logger explicitly, in the case that there is more
than one concrete logging implementation on the classpath.
The override should be part of the API, though a system property could also be supported.
The API would take precedence.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira