[
https://issues.apache.org/jira/browse/JAMES-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000147#comment-13000147
]
Norman Maurer commented on JAMES-1149:
--------------------------------------
You refer to this:
/*
* (non-Javadoc)
* @see
org.apache.james.container.spring.provider.log.LogProviderManagementMBean#setLogLevel(java.lang.String,
java.lang.String)
*/
public void setLogLevel(String component, String loglevel) {
if (getSupportedLogLevels().contains(loglevel) == false) {
throw new IllegalArgumentException("Not supported loglevel given");
} else {
((Log4JLogger)logMap.get(component)).getLogger().setLevel(Level.toLevel(loglevel));
}
}
?
As you see it cast its logger to Log4JLogger todo this. So it should be
possible with slf4j too (when cast the Logger to the Log4J implementation). Or
I'm wrong ?
> Replace commons-logging with jcl-over-slf4j
> -------------------------------------------
>
> Key: JAMES-1149
> URL: https://issues.apache.org/jira/browse/JAMES-1149
> Project: JAMES Server
> Issue Type: Task
> Affects Versions: 3.0-M2
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 3.0-M3
>
> Attachments: slfj4-imap.patch, slfj4-mailbox.patch
>
>
> During my expirements with OSGI I noticed all the problems when using
> commons-logging which use some classloader magic. I thinkwe should use
> jcl-over-slf4j to replace it to simplify stuff in the future.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
