I'm +1 on the CommonsLogLogChute in Engine. It probably also makes sense for ServetLogChute to be in Engine. I'm not too worried about compile time dependencies as our build scripts handles these automatically.
We should try to keep the list of dependencies up to date as that will help people choose which jars to include/exclude when deploying. WILL On 4/2/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
Hey folks, So, the only reason CommonsLogLogSystem ever went into VelocityTools was that that was the path of least resistance for me at the time. I wanted it to be released soon, and Velocity releases didn't happen soon. Now that we are up to speed, more or less, the reality is that CommonsLogLogChute (LogSystem is deprecated) doesn't really fit in Tools as well as it fits in Engine. That's where the other LogChutes for major logging systems are, and that's where it should be. This is just a heads up that it is coming in shortly. The real question i have here is ServletLogChute (formerly known as ServletLogSystem). Again, we have adaptors for LogKit, Log4j, JDK Logging, Commons Logging (soon), and System.err/out. Does it make sense for Engine to provide a wrapper for servletContext.log() too? Our LogManager essentially chooses the appropriate LogChute from those configured to be allowed based on the environment of Velocity and the order of the configured LogChutes. It seems to me that it would make sense to have sending log output to the servlet's log as a higher priority than sending it to System.err/out, assuming that a ServletContext instance is available in the application attributes. On the flip side, we're trying to remove Servlet API dependencies from Engine... I could go either way. I'm just curious to hear other people's thoughts here. If no one cares, chances are that i will leave ServletLogChute in Tools for now. p.s. if anyone is wondering about LogChuteCommonsLog (aka LogSystemCommonsLog), i increasingly feel that it is anathema and will never escape Tools, even if it manages to survive there. :) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
