Entries in my server-side code are currently moving from the SLF4J 1.7.2 API through the slf4j-log4j12 binding via the JBoss 6 log4j logmanager to JBoss-logging.
I eliminate the dependency on log4j. Client side, this means switching to login. On the server side, I would like to pull out the slf4j-log4j12 binding, but this seems to be causing problems. JBoss 6 binds its own slf4j run-down interface and bindings, but they seem to be around in slf4j 1.5.5.
What is my best option from the following alternatives?
- I can continue server-side logging through the slf4j-log4j12 binding in jboss-logging. This seems best, but I was hoping to completely abandon the slf4j-log4j12 binding as part of getting rid of log4j. Plus, doesn't that eliminate the many benefits of using the newer version of SLF4J?
- Updating the slf4j API, slf4j-jboss-logmanager and / or jboss-logging in JBoss 6 so that I can have log instructions directly from the slf4j 1.7.2 interface in jboss-logging. Is it possible? If so, how do I find new versions of these components?
- Switching to server-side logback, which completely changes beyond JBoss logging and probably means that I need to manage a separate log file.
source share