Ok.... now beginning to think about an issue in my server development that I've been procrastinating.... hopefully this won't get too ugly...
My company has been using Log4J for a while now as our primary logging interface. In fact, we've built a nice subclass of the Log4J Logger class that not only adds a couple of new log levels (trace and verbose to be exact) to the typical five Log4J levels, but also ties in with our exception handling classes and resource bundles for internationalization purposes. The time has come to port some of these components that use our Log4J Logger subclass into the Phoenix-based server we are building. The server prototype I've built so far just uses the native LogKit logger in all the blocks I've deployed so far. So... here is my question(s): 1. I've picked up enough peripheral knowledge to know that it is possible to configure Phoenix to use the Log4J Logger class as the default logger, instead of the native LogKit logger class. Is there a decent set of documentation that tells me what I need to do make that happen (i.e. do I need a certain version of the framework jar(s), how to I configure Phoenix to use the log4j logger, etc.) 2. Is is possible to configure Phoenix to use a subclass of the Log4J logger class as its default logger, including the addition of custom log level classes? If so, how? If not, why not? 3. Is all of the Log4J XML configuration parameters supported in the environment.xml file? I think that's enough to get me started thinking how I'm going to do this... thanks... timothy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
