I'm not sure which approach to follow, so I thought I'd ask out here. LogManager allows use of ClassLoader arguments. However, using a more abstracted interface like the ResourceLoader class in log4j-core is more extensible. In OSGi, you get the same public methods from ClassLoader in the Bundle interface. However, these are of course incompatible.
Now, we could either use an abstraction of ClassLoader, or we could have a sort of ClassLoader shim that delegates to a Bundle. Or, I could be completely missing the point of the ClassLoader parameters in LogManager. -- Matt Sicker <boa...@gmail.com>
