Package io.mats3.test.broker

package io.mats3.test.broker

Tool for creating a MQ Broker to easily create a MatsFactory backed by an in-vm MQ Broker, employed by several of the other Mats testing tools - by default uses Apache ActiveMQ, but may be directed to use Apache Artemis instead, or to use an external ActiveMQ or Artemis broker.

Related Packages

Package	Description
io.mats3.test	Contains a set of helpful tools for testing: MatsTestBrokerInterface to get DLQ'ed messages, MatsTestHelp for creation of relevant ids, MatsTestLatch for a simple tool to synchronize between the test method and the async Mats endpoints, and TestH2DataSource which is a small wrapper around H2 to create a database with a test table - mainly used by the API Tests to verify SQL transactions.
io.mats3.test.abstractunit	Common code for the modules 'mats-test-junit' and 'mats-test-jupiter' - These abstract classes should not be used directly, but rather utilized through the mentioned implementations.
io.mats3.test.junit	Mats3 testing tools for JUnit 4.
io.mats3.test.jupiter	Mats3 testing tools for Jupiter (JUnit 5).

Class	Description
MatsTestBroker	A special utility class utilized in tests and Mats test infrastructure providing a ConnectionFactory for the test (Jms)MatsFactory - and if relevant also fires up an embedded ("in-VM") ActiveMQ (default) or Artemis message broker.
MatsTestBroker.ActiveMq	Feature flags for the method MatsTestBroker.newActiveMqBroker(ActiveMq...) - which you probably shouldn't do unless you are experimenting with the "mats-examples".
MatsTestBroker.MatsTestBroker_ActiveMq	Either creates an in-vm ActiveMQ, or an ActiveMQ ConnectionFactory to an external URL, based on system properties.
MatsTestBroker.MatsTestBroker_Artemis	Creates a connection to an Artemis broker.
MatsTestBroker.MatsTestBroker_InVmActiveMq	Creates an in-vm ActiveMQ no matter what the properties says.