WildFly ActiveMQ-Based Messaging Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
{{Internal|WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Generic_JMS_Client_with_HornetQ|Generic JMS Client with HornetQ}} | {{Internal|WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Generic_JMS_Client_with_HornetQ|Generic JMS Client with HornetQ}} | ||
==Classpath== | |||
The classes required by the remoting and ActiveMQ client-side logic are available in <tt>$JBOSS_HOME/bin/client/jboss-client.jar</tt> so an EAP7/ActiveMQ client typically includes that JAR on its classpath. | |||
Revision as of 21:02, 7 February 2017
Internal
Overview
Applies to EAP 7.* and newer.
Generic JMS Client with ActiveMQ
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.