I guess I was confusing in my statements. What I meant (or meant to mean) is that the issue might only be fixed by completely isolating the app from the JBoss class-path (or class loader), which we failed to do (warning that we still receive proves that). That is, parent class loader class-path is still visible from our application, which makes slf4j complain about multiple bindings. However, in our case we have minimized the slf4j errors to the following set
2011-05-13 18:46:42,072 ERROR [STDERR] (RMI TCP Connection(4)-127.0.0.1) SLF4J: Class path contains multiple SLF4J bindings. 2011-05-13 18:46:42,073 ERROR [STDERR] (RMI TCP Connection(4)-127.0.0.1) SLF4J: Found binding in [vfszip:/<Path-to-lib-folder-inside-our-app-ear-file>/lib/slf4j-log4j12-1.6.1.jar/org/slf4j/impl/StaticLoggerBinder.class] 2011-05-13 18:46:42,073 ERROR [STDERR] (RMI TCP Connection(4)-127.0.0.1) SLF4J: Found binding in [vfszip:/<JBoss5.1Home>/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class] 2011-05-13 18:46:42,073 ERROR [STDERR] (RMI TCP Connection(4)-127.0.0.1) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
and luckily it does work for us. In JBoss 7 they are going to change the class loading model and class loading configuration options, making it possible to overcome this issue (at least that's what I've heard somewhere, need a proof link). We're using JBoss 5.1 and the following code for META-INF/jboss-app.xml file of our application's ear file
<jboss-app> <loader-repository> com.company:loader=MyAppName.ear <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </jboss-app>
I don't know whether things have changed for JBoss 6 or are different for war files, so isolation config you're using might turn out to be correct as well. I wish I could help you more. If you get lucky solving this issue, please let me know :) Regards, Roman -- View this message in context: http://xwiki.475771.n2.nabble.com/XWiki-war-JBoss-AS6-MySQL-tp6309076p636900... Sent from the XWiki- Users mailing list archive at Nabble.com.