Change Notes item #452829, was opened at 2001-08-18 22:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=381174&aid=452829&group_id=22866 Category: None Group: v3.0 (Rabbit Hole) Status: Open Priority: 5 Submitted By: David Jencks (d_jencks) Assigned to: Nobody/Anonymous (nobody) Summary: log4j logging in pool and connector Initial Comment: I finished converting the pool and connector modules to log4j logging, and reformatted the code to guidelines. My strategy for dealing with the "PrintWriter for logging" issue in the connector api is: All jboss supplied classes actually use log4j for logging. If they have a setLogWriter method, the value is ignored. If jboss is setting up an object with an api-required setLogWriter method, it is called with a logging.log4j.CategoryWriter, writing to a category based on the class of the configured object. The only place this applies at the moment is ConnectionFactoryLoader. ConnectionManager also has a setLogWriter method, but each ConnectionManager has its own ConnectionManagerFactory, so if someone provides a different ConnectionManager they can provide a specific ConnectionManagerFactory that appropriately configures logging. david jencks ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=381174&aid=452829&group_id=22866 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
