In this chapter we explain which jars you need on the Java classpath of a JBoss Messaging client application. This depends on various factors including whether you're using just core, JMS, JNDI or Netty. We explain which jars are needed in each case.
All the jars mentioned here can be found in the lib directory of the JBoss Messaging distribution. Be sure you only use the jars from the correct version of the release, you must not mix and match versions of jars from different JBoss Messaging versions.
If you're using just a pure JBoss Messaging core client (i.e. no JMS) then you need jbm-core-client.jar on your client classpath.
If you're using a Netty transport then you will also netty netty.jar and jbm-transports.jar.
If you're using JMS on the client side, then you will need jbm-core-client.jar, jbm-jms-client.jar and jbm-jms-api.jar. Note that jbm-jms-api.jar just contains Java EE API interface classes needed for the javax.jms.* classes, so if you already have a jar with these interface classes on your classpath you won't need it.
If you're using a Netty transport then you will also netty netty.jar and jbm-transports.jar.