Keep in mind that which library JARs you need depends on which lines of the source code get executed I your specific application. Chris's approach is the safe one, because it includes everything you might possibly need without being as bug as the uber-JAR and it's future-proofed as dependencies change in later versions. Denis's approach of picking a subset requires you to know exactly why ActiveMQ needs each dependency and whether you're doing the things that need it, and to maintain that knowledge as new versions are released.
Tim On Jun 17, 2016 12:39 PM, "titou10" <titou10.tito...@gmail.com> wrote: > For JMSToolBox, ( > https://sourceforge.net/projects/jmstoolbox/?source=directory), I bundle > those jars and it works: > > - activemq-client-5.13.3.jar > - geronimo-j2ee-management_1.1_spec-1.0.1.jar > - hawtbuf-1.11.jar > > Denis > > Le 2016-06-17 à 09:43, danny a écrit : > >> Hi, >> >> Which set of jar are needed for a java JMS client application, to connect >> to my ActiveMQ server >> >> I have activemq-client-5.13.3.jar, on my class path. but Its not >> enough, i >> get class not found exceptions. >> >> >> up till now I have made do using activemq-all-5.13.3.jar, >> >> however now the size of the jar is causing problems, >> and the fixed logging, included in the activemq-all-5.13.3.jar has bee >> come >> an issue. >> >> >> I looked at this >> http://activemq.apache.org/maven/5.8.0/activemq-client/dependencies.html >> but it was not enough >> >> >> >> Thanks. >> >> >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/jars-needed-for-a-jms-client-application-tp4713101.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > >
