Please give the exact version of JBM being used. Thanks.
Are you sure that the JAR files in your client's classpath are those from the client directory of the server?
Not quite helpful info.
But I got a similar error sometime back. I re arranged the jar files here and there and it got resolved magically. Just to make you feel better - you are not alone in this whole jar conflicts thing. I can vividly recall the countless nights resolving the correct jar files, just because some other version of the jar is lying somewhere.
I actually found out the problem, I was using the wrong jar version.
but then another problem arose: how do i recover with maven this file, given that it has dots in the directory name:
If I do:
<dependency> <groupId>org.jboss.client</groupId> <artifactId>jbossall-client</artifactId> <version>4.0.5.GA</version> <scope>compile</scope> </dependency>
then maven tries for
How do I do that?