On 03/29/2016 02:43 PM, stak wrote:
So are you saying that activemq-all.jar is not a production grade jar to be
used as a client jar when they want to connect to an external activemq as a
client?. Is the purpose of that jar really only for a quick unit test of
sorts?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-all-jar-tight-coupling-with-log4j-tp4710022p4710030.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
There are plenty of folks that use it in production. The all jar
contains not only client code but broker code, message store code and
much more, hence the 'all' moniker, which is very much overkill if you
are using it just for client purposes. You need to choose the best tool
for the job and the all jar is not always it.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
