On Jun 29, 2011, at 1:51 PM, Mark Struberg wrote: > Sorry for the delay, follow up further... > >> By default, the resolver only scans classes in >> org.apache.logging.log4j packages and subpackages. > > But that still does perform much worse than a simple set of properties files > which can get picked up directly via ClassLoader#getResources, isn't? How do > you perform this class scan? >
Maybe, but IMO the ease of adding new components is worth it. On my 2 1/2 year old Macbook Pro I added the API and Core classes to Tomcat's lib directory and the scan took about .15 seconds. Of course, then it processes the XML configuration to actually instantiate the Appenders, Layouts, Filters and LoggerConfig objects. And it is only going to do this each time a reconfiguration occurs. The source code for this component is org.apache.logging.log4j.core.config.plugins.ResolverUtil and org.apache.logging.log4j.core.config.plugins.PluginManager. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
