Note

This is an important note on the Messaging client jar. JBoss Messaging has an extensive tree of dependencies and bundling all right dependencies in one easy to use archive, so no wrong versions inadvertently get in the class path is, as experience shows, extremely convenient. However, this could cause problems if a different version of a dependency is required by the user's client code.

If, for example, the log4j.jar bundled with the release causes problems for being too old, one could just simply build the client-side class path so a newer version of log4j.jar precedes jboss-messaging-client.jar in that class path. This approach may work, but is not guaranteed to work, because we did not run the full test suite with any other log4j.jar version except the one we bundle with the release. Soon we will providing an ant task that creates a slimmed down client jar without the extra dependencies bundled.

A list of required dependencies for a specific release can be found in the build-thirdpary.xml file that is part of the companion source bundle that ships with each release. It can also be looked up online in http://fisheye.jboss.org.