Prior to JBoss 5, the jboss-all-client.jar was pretty much all you needed. However, the JBoss 5 Getting Started Guide states the following:
The client/jbossall-client.jar library that used to bundle the majority of jboss client libraries, is now referencing them instead through the Class-Path manifest entry. This allows swapping included libraries (e.g. jboss-javaee.jar) without having to re-package jbossall-client.jar. On the other hand, it requires that you have jbossall-client.jar together with the other client/*.jar libraries, so they can be found.
In order to access JBoss Messaging from a remote client, you need the following jars in the client’s CLASSPATH:
- $JBOSS_HOME/client/jnp-client.jar
- $JBOSS_HOME/client/jboss-javaee.jar
- $JBOSS_HOME/client/jboss-messaging.jar
- $JBOSS_HOME/client/jboss-remoting.jar
- $JBOSS_HOME/client/jboss-serialization.jar
- $JBOSS_HOME/client/javassist.jar
- $JBOSS_HOME/client/jboss-aop-client.jar
- $JBOSS_HOME/client/trove.jar
- $JBOSS_HOME/client/log4j.jar
- $JBOSS_HOME/client/jboss-logging-spi.jar
- $JBOSS_HOME/client/jboss-logging-log4j.jar
- $JBOSS_HOME/client/jboss-common-core.jar
- $JBOSS_HOME/client/jboss-mdr.jar
- $JBOSS_HOME/client/concurrent.jar
Nice! I needed this!!! Get it at the top of the search engines so it isn’t so hard to find next time.
It would be good to know how you found these JAR files. You fed me for a day, but I’ll be hungry again tomorrow. Please teach me how to fish.