[
https://issues.jboss.org/browse/MODCLUSTER-602?page=com.atlassian.jira.pl...
]
Coty Sutherland reopened MODCLUSTER-602:
----------------------------------------
You don't think the mod_cluster module should use what's native to the container?
Tomcat doesn't log via jboss-logging, it uses JULI. So it doesn't help that
mod_cluster _inside_ Tomcat uses jboss-logging for it's few messages; IMO it's a
dependency that we have to keep for a handful of messages that could be logged with the
containers logging framework.
Using jboss-logging in EAP and Wildfly is fine, but JULI is Tomcat's native logging
framework so it'd be nice if we could use that to log rather than jboss-logging.
Remove jboss-logging from mod_cluster code that runs on Tomcat
--------------------------------------------------------------
Key: MODCLUSTER-602
URL:
https://issues.jboss.org/browse/MODCLUSTER-602
Project: mod_cluster
Issue Type: Bug
Components: Core & Container Integration (Java)
Reporter: Coty Sutherland
Assignee: Radoslav Husar
I'm trying to get rid of all of the JBoss dependencies that I can from Tomcat in JWS
and found that jboss-logging is used by mod_cluster. Is it possible to remove
jboss-logging from the mod_cluster code that runs on Tomcat and use JULI or some other
framework?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)