0 Replies Latest reply: Mar 2, 2012 12:43 PM by Tomohisa igarashi RSS

jboss-logging version conflicts(2.0 vs 3.0): NoSuchMethodError on Logger#getMessageLogger()

Tomohisa igarashi Expert

First of all, I'm sorry to have some uncertain things, but I just would like to write it down for a reminder.

 

Current hibernate-entitymanager uses Logger#getMessageLogger() but the jboss-logging-spi-2.0 doesn't have this method, so we catch a error like this: http://pastebin.com/zjLmXynp

As you can see in the stacktrace, hibernate-entitymanager seems to be used in Riftsaw.

 

I have noticed the jnpserver is the one that uses the old jboss-logging-spi-2.0.

So if you use bpel-component and camel-jms binding together with having dependency on jnpserver in pom.xml, you will get the same error.

    <dependency>

       <groupId>org.jboss.naming</groupId>

       <artifactId>jnpserver</artifactId>

    </dependency>

 

One thing I couldn't make sure is that, once I remove above dependency from pom.xml, the error is gone automagically. I guess camel-jms change something around the JNDI lookup if it can't find the jnpserver.

 

And I also have noticed that camel-jms-binding quickstart no longer need to depends on jnpserver. It still works fine even if I remove that dependency. I found a interesting JIRA https://issues.jboss.org/browse/AS7-2132 and this may be related to some changes in AS7.1.