> Same should happen for Log, assuming we get the commons-logging > to support JMX and add a wrapper for JDK1.4 ( for log4j > we should just use their mbean ). I assume we all agree on > moving to commons-logging as API, and keeping the old Logging > interface only for backward compat.
I just reviewed the tomcat 5.0 proposal, and I didn't notice anything about logging changing in 5.0 Just so I understand this, the current use of <Logger .../> element "will/should/encouraged to" disappear in 5.0 and instead modules will directly call the commons-logging interface? So if I want to log a particular context/webapp or Host or Engine, I will have to figure out what "domain" it logged to and get the underlying logging system (log4j, JDK1.4, logkit) to filter out the webapp/Host/Engine I am interested in? Cheers, -bob -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
