rang s wrote:
Thanks David for the reply.
1.) You mentioned that to avoid the JUL-to-SLF4J artificat of SLF4J, a no-op stub is added. How do I specify the underneath implementaion. For example- if I intend to use log4j, do I just need to package the log4j.jar and the config file in my jar file ?
If you want your application to have separate logging, you only need to include your log4j.xml, log4j.properties, or logging.properties file and that's it. Then your application's logging will be configured according to that file. The logging is always treated the same regardless of whether you use slf4j, JUL, log4j, or commons-logging; this means you could use a log4j.xml and use the JUL API if you wanted to, and it'd work correctly.
If you want your application to use container logging, just leave out any logging config file.
Either way, any logging JARs you include in your deployment should be automatically ignored by the container unless you specifically override it using jboss-deployment-structure.xml, which you normally should not do.
rang s wrote:
2.) Also. as per https://docs.jboss.org/author/display/AS7/Implicit+module+dependencies+for+deployments , org.jboss.logging.jul-to-slf4j-stub is a implicit module. This does not seem to be the case. I had to explicitly had a dependency to avoid ClassNotFound Errors in 7.1.2.FINAL.
OK, that sounds like a bug to me. Could you please log an issue at https://issues.jboss.org/browse/AS7? Thanks.