I don't think so. Did you by chance read the articles I referenced? If I understand it correctly, Configurator is called once to configure an existing logger context. That's not what I'm looking for. Clogr manages potentially multiple logger contexts, and determines which one to return each time a logger is requested. This is in fact exactly what ContextSelector does, and why all Clogr should have to do would be to implement ContextSelector, except that the way to boostrap the initial ContextSelector was brittle and discouraged (and now prohibited by Java modules). The other impediment of course being that ContextSelector if I understand it correctly is being ripped out altogether. I fear I may be repeating myself. I encourage everyone to at least read https://stackoverflow.com/a/38317149/421049 and https://dzone.com/articles/creating-local-globals-with-csar so they can understand what's going on. |