I\'m hoping that maybe someone has run into this problem before and can provide advice. I\'m writing an application on Hibernate 4 and Spring 3. Here\'s my dependency tree:<
Well, while pairing with a co-worker, we found a workaround for the issue we were seeing with JBoss and Hibernate 4. Turns out if we explicitly tell JBoss EAP our logging implementation (-D org.jboss.logging.provider=slf4j), it doesn’t do the scanning for the logging implementation and doesn’t have the NoSuchMethod exception that I was seeing. Thus, we don’t have to make any other changes other than setting one system property.