[
https://issues.jboss.org/browse/MODCLUSTER-602?page=com.atlassian.jira.pl...
]
Radoslav Husar commented on MODCLUSTER-602:
-------------------------------------------
You don't think the mod_cluster module should use what's
native to the container?
Well, the log messages do end up in what's native to
the container. The library jboss-logging which mod_cluster uses, first looks up the log
manager providers, if none found, defaults to JDK logging which in turn on Tomcat is
implemented/replaced by Tomcat JULI.
So it doesn't help that mod_cluster inside Tomcat uses
jboss-logging for it's few messages
It does help, since jboss-logging is the
facade that deals with different logging providers, optimizes for performance, etc.
IMO it's a dependency that we have to keep for a handful of
messages
Handful, specifically 46 messages (see
org.jboss.modcluster.ModClusterLogger).
messages that could be logged with the containers logging framework.
They do end up in JULI.
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.
This would mean creating another facade on top of a
facade we already have, delegating to either jboss-logging or something else. This would
be a rather significant piece of work for the small benefit which is "not having
jboss-logging.jar in tomcat/lib".
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)