Generic JMS Client with EAP/ActiveMQ: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= =Overview= Also see: {{Internal|WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Generic_JMS_Client_with_HornetQ|Generic JMS Client with HornetQ}} =Classpath=...") |
|||
| Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[WildFly_ActiveMQ-Based_Messaging_Subsystem_Concepts|WildFly ActiveMQ-Based Messaging Subsystem Concepts]] | |||
=Overview= | =Overview= | ||
Revision as of 21:04, 7 February 2017
Internal
Overview
Also see:
Classpath
The classes required by the remoting and ActiveMQ client-side logic are available in $JBOSS_HOME/bin/client/jboss-client.jar so an EAP7/ActiveMQ client typically includes that JAR on its classpath.