1

I am developing a Jersey RESTful service using the Spring framework integration with Hibernate. I get a NoSuchMethodException on a org.jboss.logging.logger.debugf call. As I noticed, the class is indeed loaded from the bean-validator.jar included alongside the jersey-spring3 library, eventhough I have specifically referenced the jboss logging artifact.

Has anyone encountered this issue? And if so, how should I solve it?

Update

I have found a workaround, but it is far from being a solution. In order for the required classes to have the same signature, I have downgraded the hibernate-entitymanager to version 4.2.8.Final. However, this leads the way to other compatibility issues.

Update 2

In the end, I have chosen to implement the REST service functionality using the Spring Framework instead of using the aforementioned integration.

Dragos Dumitrescu
  • 101
  • 1
  • 10

1 Answers1

0

Check out the answers in the following post, your issue might be similar:

Error "java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger"

Community
  • 1
  • 1
codedabbler
  • 1,231
  • 7
  • 13
  • I checked it out, but it is not the same issue. The problem is that another version of the logger class is being loaded from the bean-validator.jar – Dragos Dumitrescu Jun 17 '15 at 18:40