Chapter 10. The Client Classpath

HornetQ requires several jars on the Client Classpath depending on whether the client uses HornetQ Core API, JMS, and JNDI.

Warning

All the jars mentioned here can be found in the lib directory of the HornetQ 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 HornetQ versions. Mixing and matching different jar versions may cause subtle errors and failures to occur.

10.1. HornetQ Core Client

If you are using just a pure HornetQ Core client (i.e. no JMS) then you need hornetq-core-client.jar and netty.jar on your client classpath.

If the client runs inside a Java 5 virtual machine, use instead hornetq-core-client-java5.jar.

10.2. JMS Client

If you are using JMS on the client side, then you will also need to include hornetq-jms-client.jar and jboss-jms-api.jar.

If the client runs inside a Java 5 virtual machine, include instead hornetq-jms-client-java5.jar.

Note

jboss-jms-api.jar just contains Java EE API interface classes needed for the javax.jms.* classes. If you already have a jar with these interface classes on your classpath, you will not need it.

10.3. JMS Client with JNDI

If you are looking up JMS resources from the JNDI server co-located with the HornetQ standalone server, you wil also need the jar jnp-client.jar jar on your client classpath as well as any other jars mentioned previously.