Hi Maarten, I figured it out finally. I was using Jetty embedded in Google Web Toolkit's development jar. Apparently Jetty uses slf4j itself, and prevents loading of slf4j classes from wars deployed within it - which causes the NoClassDef. You can override this behavior in a jetty-web.xml file. Doing that resolved the problem; although I also figured out that I just needed one binding.
Thanks! j -- View this message in context: http://slf4j.42922.n3.nabble.com/NoClassDef-on-LoggerFactory-tp4025414p4025416.html Sent from the slf4j - user mailing list archive at Nabble.com. _______________________________________________ slf4j-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/slf4j-user
