Hi, Using OSGi logging in that class [1] makes it impossible to activate debug logs dynamically, and debugging adapter-related code is no fun without that.
I have suggested a patch to use slf4j instead, in SLING-2016 - WDYT? I understand the adapter is relatively low-level code, but we're already using slf4 logging in the Sling engine, for example, so I think that should work for the adapter as well. -Bertrand [1] http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/adapter/src/main/java/org/apache/sling/adapter/internal/AdapterManagerImpl.java
